CRM integration change checklist: before and after you touch a sync

Use this list whenever someone connects a new app, edits mappings or changes properties in your CRM. It is written around HubSpot data sync, and the same steps apply to other CRMs.

Updated 2026-10-17 · Venture Lab 10

Before the change

• Snapshot the current mappings as JSON or CSV, dated.
• List the reports, workflows and lists that read the mapped properties.
• Check the sync direction. HubSpot data sync offers two-way, only to HubSpot, or only to the other app.
• Check the conflict setting. HubSpot says the default app overwrites the other when values differ. If that app has no value, nothing is changed.
• Note required fields. HubSpot marks them with an asterisk in the mappings table.

During the change

• Use a test sync where you can. HubSpot documents a test sync for a new object sync from a newly connected app. It runs one-way into HubSpot and previews the results.
• Remember that filters only scope the first sync. HubSpot notes that records which have synced keep syncing based on the mappings.
• Map names and owners correctly. First Name and Last Name must both be on. Owners are matched by email and must exist as users in both apps.
• Know what custom mappings need. HubSpot documents that they require a paid Data Hub subscription.

After the change

• Take a new snapshot and diff it against the old one. Review every removed and changed mapping.
• Spot-check a few records on both sides.
• Watch the reports you listed for a few days.
• Store both snapshots with a note of who changed what and why.

The free CRM mapping diff does the diff step in your browser. It needs no CRM login and makes no connection; you paste the two snapshots.

Venture Lab 10 is independent. Other product and service names are used only to describe compatibility or for comparison, and are trademarks of their owners.

← All guides