Bi-Directional Syncing allows Microsoft Dynamics CRMi users to send and receive updated data records between Acoustic Campaign and Microsoft Dynamics CRM. Use bi-directional syncing for new or existing Acoustic Campaign fields mapped to Microsoft Dynamics CRM.

Read through the following points before you proceed with bi-directional syncing:

• Leads and Contacts do not have to have the same mappings. For example, you can map specific fields on a Lead but not map those same fields for the Contact.
• When you change a record in Microsoft Dynamics or Acoustic Campaign, all mapped fields are moved to another system. Therefore, the data in a field can be overwritten, regardless of which system is considered the system of record, even if the change was not a mapped field.

Note: To minimize risks, take care when mapping fields from Acoustic Campaign to Microsoft Dynamics CRM. Back up your data in all systems before you start the bi-directional sync.

• Synchronization issues can occur when processing records between the two systems. For example, although processing takes 10 minutes, scheduled updates might take longer due to larger data jobs. Also, updates to a field in both systems might coincide.

Before you configure bi-directional synchronization to update records, you need to understand if you must sync a new or existing field. The field you want to use for bi-directional syncing must exist in your Acoustic Campaign database. Also, the corresponding field in Microsoft Dynamics CRM to which you want to map the Acoustic Campaign field must live in the CRM database.

Complete the backup of your data in the following systems before you start the bi-directional sync.

1. Scribe: Export your existing Scribe maps.
2. Acoustic Campaign: Export your Acoustic Campaign data to a CSV.
3. Microsoft Dynamics CRM: Back up your data according to Microsoft Dynamics specifications. See your CRM Administrator for details.

Note: Account fields are not bi-directional. Account fields are only synced from CRM to Acoustic Campaign.