Overview
This page relates to the ConnectWise integration. It contains the data mappings for contacts and contact-related information like phone numbers and email addresses. It also contains any logic and sync rules that apply.
For more information on the integration between Emersion and ConnectWise, see this article.
Contacts Data Mapping
| ConnectWise | Emersion | Rules | |
|---|---|---|---|
| id | - | id | |
| company | - | account | |
| site | - | site | |
| first name | first name | ||
| last name | last name | ||
| gender | gender | ||
| birth day | date of birth | ||
| is Inactive | status | In ConnectWise, this field is labelled Status, and can be either Active or Inactive. | |
| address | primary address | In ConnectWise, this is displayed as Personal Address on the Profile tab. | |
| Address | Address | ||
| address line 1 | <-> | address line 1 | |
| address line 2 | <-> | address line 2 | When copying addresses from ConnectWise to Emersion, the address display type will be Unstructured, which is a very simple type. Emersion addresses using one of the more complex types will be converted to the Unstructured format for the purpose of comparing and exporting data. |
| city | <-> | suburb | |
| state | <-> | state | For Australian addresses, the state value has to match a standard abbreviation, e.g. 'VIC', 'NSW' etc. |
| zip | <-> | postcode | |
| country | <-> | country | These values received from ConnectWise are matched using a lookup table based on the ISO 3166 standard. Values that fail lookup will be discarded. |
| communication items | <-> | phone numbers | Communication Items in ConnectWise are matched to phone numbers and email addresses in Emersion using the 'communication type' as a key. The mapping between ConnectWise types and Emersion types is defined in the Communication Types mapping screen. If a type is not mapped, then the communication item will be excluded from the sync data. For phone numbers, only digits and the '+' character are allowed. All other characters are removed. |
| Communication Item | phone number | ||
| communication type = phone | |||
| type | - | type | |
| value | <-> | number | For phone numbers, only digits and the '+' character are allowed. All other characters are removed. |
| extension | <-> | extension | |
| isPrimary | <-> | isPrimary | |
| Communication Item | phone number | ||
| communication type = fax | |||
| type | - | type | |
| value | <-> | number | For phone numbers, only digits and the '+' character are allowed. All other characters are removed. |
| extension | <-> | extension | |
| isPrimary | <-> | isPrimary | |
| Communication Items | <-> | email address | Communication Items in ConnectWise are matched to phone numbers and email addresses in Emersion using the 'communication type' as a key. The mapping between ConnectWise types and Emersion types is defined in the Communication Types mapping screen. If a type is not mapped, then the communication item will be excluded from the sync data. |
| Communication Item | email address | ||
| communication type = email | |||
| type | - | type | |
| value | <-> | address | |
| isPrimary | <-> | isPrimary |