The Contacts template is used to import new or update existing contacts in Vega.
A new contact record will be created for every row in the upload file where there is no existing contact in Vega with an exact match on any of the following -
- first name, last name and email address
- first name, last name and mobile phone
- first name, last name and address
- Scoperid/Org ID
Please note: If the Scoperid matches an existing record it will match on that alone. Please be careful when you use Scoperid.
If there is a matching contact in Vega then the imported data will update the existing contact.
Please note- the import tool does not check for duplicate records within the import file itself. If there are multiple records with the same details in one upload file it will create a new contact record for each. It is therefore important that any duplicates are resolved before uploading.
A system created attribute will be added to every contact created or updated by the Import, identifying the import name and date. The name assigned to each Import should be unique so that you have visibility of which import created the contact record.
* Denotes a required field
|Template Field Name||Field Type (Length)||Description|
This is a unique identifier for the contact record. For data migration, this will typically be the unique identifier for the Contact from your legacy system, not Vega. This data will be populated into the Org ID field on the Contact.
Note: If the Scoperid matches an existing record it will match on that alone. Please be careful when you use Scoperid.
|AccountName||nvarchar(50)||This is the Name of the Account (usually first and last name or Organisation name)|
|Title||nvarchar(50)||Valid values are Dr, Master, Miss, Mr, Mrs, Ms or leave blank where a title is not known.|
|First Name||nvarchar(150)||The first name of the primary contact for this Contact. This can be left blank where unknown.|
|Middle Name||nvarchar(50)||The middle name of the primary contact for this Contact. This can be left blank where unknown.|
|Last Name||nvarchar(150)||The last name of the primary contact for this Contact. This can be left blank where unknown.|
|Suffix||nvarchar(50)||The suffix of the primary contact for this Contact record where required else leave blank.|
|Organisation||nvarchar(150)||The name of the organisation for the Contact record where the Contact represents an organisation or is an organisation else leave blank.|
|Job Title||nvarchar(100)||The primary contact's job title where applicable or leave blank.|
|Salutation||nvarchar(100)||The salutation that you wish to use when addressing communications to this contact. If not supplied it will default to the Contact's first name where this is populated.|
|[The contact's primary address can be imported here as part of the contact record or, where there are multiple addresses for a contact, addresses can be imported using address import template where you can specify the address type. Any of these fields can be left blank if not required.]|
|Address 1||nvarchar(150)||The first line of the contact's primary address.
The data import only inserts a new address if the address 1 field is present and it doesn't match what's already recorded.
Otherwise, if address 1 is not filled, it updates the existing address with any fields that are filled e.g. city, postcode etc.
|Address 2||nvarchar(150)||The second line of the contact's primary address|
|Address 3||nvarchar(150)||not used|
|Suburb||nvarchar(150)||The suburb of the contacts primary address|
|City||nvarchar(150)||The city of the contact's primary address|
|State Name||nvarchar(150)||The state of the contact's primary address where applicable|
|Country||nvarchar(150)||The country of the contact's primary address|
|Post Code||nvarchar(20)||The Postcode of the contact's primary address|
|[The contact's primary communication details, including 2 email addresses, mobile, main and work phone numbers, can be imported here as part of the contact record or, where there are additional communication options for a contact, these can be imported using telecoms import template where you can specify the telecoms type. Any of these fields can be left blank where not required. None of these fields are validated and therefore they may be loaded in whatever format you prefer.]|
|Email Address||nvarchar(50)||The Contact's 1st email address|
|Email 2||nvarchar(50)||The contact's 2nd email address|
|Mobile Phone||nvarchar(60)||The contact's mobile phone number|
|Main Phone||nvarchar(60)||The contact's main phone number|
|Work Phone||nvarchar(60)||The contact's work phone number|
|[The Join Date, Active Flag and Ok to Contact fields MUST be populated but any of the other fields can be left blank where the default values are as required]|
|Join Date*||date||The date the contact joined. If entered it must be formatted as DD-MMM-YYYY, for example, 17-Jan-2016.|
|Active Flag*||bit||TRUE or FALSE. Where the contact is Active this must be set to TRUE. Where the contact is not active this must be set to FALSE, and the Inactive Date and Entity Status Reason should be populated where they are different from the default values.|
|OK to Contact*||bit||TRUE or FALSE. Indicates whether the contact is ok to contact. If the contact is not OK to Contact this must be set to FALSE, the Mail Status Reason will default to ‘No (Their Choice)’ if not supplied.|
|Membership||nvarchar(150)||Indicate whether the contact is a member and the membership model which applies to them.|
|Alert Note||nvarchar(500)||Any alert notes you want highlighted when you bring up this contact in Vega.|
|[Two attributes can be imported for the Contact as part of the Contacts import. If you require more than 2 attributes, effective dates or an attribute value to be captured then the Attributes import should be used. Any of these fields can be left blank where not required. If the attribute type or Attribute does not exist it will be created by the import. Ensure that the Names have been correctly entered where your attributes have already been configured.]|
|Attribute Type 1||nvarchar(100)||The Attribute Type for the 1st Attribute.|
|Attribute 1||nvarchar(250)||The 1st Attribute to be added for the contact.|
|Attribute Type 2||nvarchar(100)||The 2nd Attribute Type for the Attribute.|
|Attribute 2||nvarchar(250)||The 2nd Attribute to be added for the contact.|
|[The following details can be left blank if the defaults are as required. Where the Contact record is not active, both the Inactive Date and Entity Status Reason should be populated.]|
|Match Entity ID||nvarchar(50)||Is mapped to SUPPID in the user interface which can be a sequential number from an old system or a separate sequential ID for a client.|
|DPID||int||The Delivery Point Identifier for the Primary Address if known.|
|Entity Status Reason||nvarchar(50)||This must be a valid Entity Status reason where entered. If not entered it will default to Active where the Active Flag is set to TRUE and Inactive where the Active Flag is set to FALSE. If the Contact is inactive and you want to display a different reason this should be set.|
|Mail Status Reason||nvarchar(50)||This must be a valid Mail Status reason where entered. It will default to OK to Contact where OK to Contact is set to TRUE. If OK to Contact is set to FALSE it will default to No (Their Choice), it should be entered where any other reason is required for the contact.|
|Inactive Date||datetime||The date the Contact was made inactive. This must be in date format dd-mmm-yyyyy, for example, 22-NOV-1996.|
|Deceased Date||datetime||Where the Contact is deceased this is the date they were updated to 'deceased' status. This must be in date format dd-mmm-yyyyy, for example, 22-NOV-2016.|
|Birth Date||date||The date of birth of the contact where it is known. This must be in date format dd-mmm-yyyyy, for example, 22-NOV-1996.|
|Campaign||nvarchar(50)||The name of the Campaign that the contact was acquired through. This can be set to a default value, for example, Initial Data Migration where there is no equivalent in your legacy system.|
|Gender||nvarchar(1)||Must be either 'M','F' or 'U'.|