Recommended Mapping Examples

The initial configuration already includes useful field associations. Start from these defaults and customize only what is actually required by the business process.
Contact example
Exchange
vtenext
Last name
Last name
First name
First name
Primary e-mail
E-mail
Business phone
Phone
Mobile phone
Mobile
Home phone
Home phone
Business fax
Fax
Department
Department
Job title
Title
Birthday
Date of birth
Business address
Primary shipping address
Other address
Other address
The Primary e-mail field must remain mapped to a valid vtenext e-mail field.
Organization example
Exchange
vtenext
Company name
Organization name
Primary e-mail
E-mail
Business phone
Phone
Description
Description
Business address
Billing address
Other address
Shipping address
Organization name is a structural association and should not be treated like a normal free mapping row.
When to add a custom field
Add a mapping only when the value is actually used, the vtenext field type is compatible, the information must be visible in Exchange and it is clear which system is the authoritative source for the value.
Avoid excessive mappings
Synchronizing many unused fields makes troubleshooting harder. A smaller, clear mapping based on real business needs is usually preferable.