1. Internal KB
  2. Integration Library

DATA SYNC | Microsoft Dynamics + HubSpot Integration

Below are some specifics on how the Data Sync connector works for Microsoft Dynamics along with any notable limitations.

Deduplication;
  • During the initial sync, HubSpot will compare both databases. When a match is detected, existing records will be updated. 
  • Contacts: Data sync matches records by comparing the contacts’ email addresses. Only one Contact with an Email Address will sync, the sync will sync the first Contact with a unique Email Address recognised via the API call. 
  • Companies: HubSpot will match an Account record with a HubSpot Company record based on the Company Name field.
Field Mapping & Association limitations;
  • Lookup field types cannot sync between the two systems due to API variables in the return of lookup values to HubSpot.

Possible Solution: If the use case is to simply sync the Lookup value to HubSpot, you can recommend passing the MS Lookup Value into a Single String Value field and pass to HubSpot that way.

  • If a record has multiple company associations, only the primary company will be synced.
  • Data sync can automatically associate invoices to contacts. Invoices must be manually associated to company records in HubSpot.
    • Note* I would strongly advise independent testing in your test portal to identify any specific limits for your current field mappings. If you do not see a field as available then that likely means the field cannot be mapped. 
    • Additional Information on Field Mappings within Data Sync here.
Setting Limits in the Sync eg. Sync MQLs HubSpot > Dynamics 
  • The Limit which records sync section only limits which records initially sync between HubSpot and the third-party app. Once records sync, they will continue to sync data back and forth based on the property mapping set up. 
  • The same applies to Dynamics originating records, you can apply Filters for Dynamics > HubSpot for the initial sync, once the records meet this criteria, they will continue to sync based on One Way/Two Way rules established. 
  • A typical example of applying Limits may be as follows: 
    • All records that originate in HubSpot should sync to Dynamics when Marketing have qualified eg. Lead Status = MQL. The record will continue to sync, when Sales close that lead, Marketing can assess ROI/Attribution and understand how that lead progressed through the funnel directly in HubSpot reporting 
    • Only records that originate in Dynamics should pass to HubSpot for upsell/cross-sell or additional nurture, therefore you consider setting a custom Lead Status property to eg. 'Lead' and use this as the Filter
 
Non-Marketing + Marketing Contacts
  • You can decide to set a flat rule that all contacts syncing from Dynamics are set to non-marketing initially, you can then use Workflows based on custom enrolment to update specific Contacts as 'Marketing' when hitting a criteria (screenshot below)
 
Screenshot 2023-09-17 at 6.18.00 pm.png
 
HubSpot Embed for Dynamics
Guide to setup here.
 
Author: Lucy Seed
Date Updated: 2/10/2023