How to Audit Your CRM Integrations for Data Gaps and Sync Failures
TL;DR: Audit CRM integrations by tracing the same records and activities from source to destination. Check identity, field mappings, event-specific sync rules, permissions, relationships, and reporting definitions separately. Preserve evidence of each gap, assign a fix owner, and verify the corrected destination record before declaring the integration healthy.
What should the audit prove?
The audit should show that the intended information reaches the correct record with the expected meaning. A connected account or successful job does not establish that every field, activity, or relationship is correct. Define the expected result before inspecting the logs.
| Check | Evidence to preserve | Pass condition |
|---|---|---|
| Identity | Source and destination record IDs | The intended person and company match |
| Fields | Source value, mapping and destination value | The configured transformation is correct |
| Activities | Original event and related CRM activity | The right event reaches the right record |
| Relationships | Person, company and opportunity links | Required associations are present |
| Attribution | Opportunity dates and attribution rule | Reported credit matches the defined rule |
| Recovery | Failure, correction and repeated check | The underlying issue is resolved |
Choose records that expose different failure paths
Use a review set that represents your actual workflow, including existing and new contacts, incomplete records, recently changed fields, and records connected to opportunities. Include unsuccessful or skipped operations. Do not prescribe a universal sample size: coverage of your material paths matters more than copying an arbitrary count.
Start with record identity. HubSpot sync matches contacts by email and companies by domain; matching does not merge existing CRM duplicates. For Salesforce sync, also inspect whether the workspace writes people as leads or contacts and whether the event permits record creation.
Inspect mappings and sync rules independently
Mappings determine the values and write behavior; sync rules determine when an event writes. Review HubSpot field mappings or Salesforce field mappings in both directions. Fill-if-empty intentionally preserves a populated destination, while overwrite behavior may replace it.
A mapping change can start background reprocessing, so a temporarily unchanged record is not automatically a failed sync. Preserve the change time and check again after the relevant processing has completed. If the value still differs, review field type, required values, and the connected account’s access.
Trace separate enrollment and activity sync rules for automatic sends, manual sends, replies, tasks, and logged call outcomes. Sync if already exists can skip a record that has no match; an enabled integration does not mean creation is permitted for every event.
Verify actual activities and relationships
Compare the original event with the destination activity and its related person. Email tasks sync after completion, while phone-call and action-item tasks can sync when ready. A missing unfinished email task can therefore reflect the configured product behavior rather than data loss.
For Business call sync, review the logged outcome, sync rule, Phone call mapping, and CRM connection. Recordings and transcripts depend on availability, processing, and permissions. A call activity without an attachment is a different issue from a missing call record.
Check contact-company and opportunity relationships separately from field values. HubSpot associations refresh on a daily schedule distinct from its approximately fifteen-minute record checks, and large changes can take longer. A populated contact does not establish that every association needed by a filter has arrived.
Find every writer before changing a field
Inventory the routes that can change the destination. Unify Play sync actions run according to the Play independently of automatic sync rules, using the workspace connection and saved mappings with bidirectional sync enabled. Do not diagnose the event rules alone when the change came from a Play.
Include CSV imports in the investigation because mapped upload values can update existing records. Keep the original file and upload result when reviewing an unexpected change. Establish which process owns the field before enabling another overwrite route.
Treat ownership changes carefully. Engagement policies depend on the configured CRM ownership field; changing or removing its mapping can disable enforcement. Review the policy impact with the administrator responsible for account access before saving a repair.
Reconcile attribution, then close the issue
For the Business Pipeline generated dashboard, check the opportunity’s original CRM creation date, linked people or company, and qualifying activity. Direct attribution takes precedence, and each opportunity contributes once. Missing amounts use the workspace average of populated amounts, so inspect amount quality before presenting a value discrepancy as a sync failure.
- Record the failing stage, affected IDs, expected result and observed result
- Assign an owner for the mapping, permissions or workflow correction
- Retest the affected record and another relevant path after the change
- Close the issue only after the destination and reporting view agree with the intended behavior
Repeat targeted checks after material schema, permission, routing, or integration changes. Consolidating tools can simplify administration, but it does not remove the need to verify writes. To evaluate a connected outbound workflow against this audit, try Unify.
Frequently asked questions
Does a green connection status prove the integration is healthy?
No. Verify records, values, activities, relationships, and reporting behavior separately.
Does every missing activity mean a sync failed?
No. Check whether the event is eligible and its sync rule enabled. Unfinished email tasks, for example, are not yet synced as CRM tasks.
Will matching records remove existing CRM duplicates?
No. Unify matches records for writes but does not merge existing HubSpot or Salesforce duplicates.
Why might a populated field remain unchanged?
Fill-if-empty behavior can intentionally preserve it. Also check the read or write direction, field access, and background processing.
Should an audit use a fixed number of records?
Choose coverage based on the material workflows and risks. Include exceptions, not only successful records.
When is a repair complete?
When the affected destination records and relevant reporting behavior match the expected result after retesting.
Glossary
- Sync rule: The event-specific decision to write data
- Field mapping: The relationship and behavior between source and destination fields
- Association: A relationship between CRM records
- Orphaned record: A record missing a relationship required by the workflow
- Reconciliation: Comparison of intended and actual records or outcomes

