You fix a customer's phone number in HubSpot. Later, the old number comes back. Sales blames the integration. Finance says its records are correct. The integration is doing exactly what someone told it to do. Unfortunately, nobody remembers who that was.
Before you turn on a sync, decide where each important value should be maintained and which system is allowed to change it. That decision gives you something concrete to configure and test.
Start with a field ownership sheet
A company can use HubSpot for sales while keeping billing details in an accounting platform. Calling either application the source of truth for everything leaves a lot unexplained.
Write down the fields your team actually needs across both systems. For each one, name the place where staff should make corrections, the intended direction of updates, and the person responsible when the values disagree.
Here is an illustrative starting point for a business that manages sales in HubSpot and billing elsewhere. These are business decisions to validate, not a promise that every connector supports every mapping.
| Field | Maintained in | Intended behavior |
|---|---|---|
| Sales qualification status | HubSpot | Keep sales decisions in HubSpot unless another team needs a copy. |
| Billing address | Accounting platform | Show the approved billing address in HubSpot where supported. |
| Customer account ID | Accounting platform | Store a reference in HubSpot without letting sales invent a new ID. |
| Sales contact phone | HubSpot | Send verified corrections to the connected app where supported. |
The sheet should also explain what happens when a field is blank. Does blank mean unknown, intentionally cleared, or waiting for review? Those are three different instructions wearing the same empty cell.
Check what the connector can actually support
Start with the app's native data sync options. HubSpot's field mapping documentation explains that custom mappings require Data Hub Starter, Professional, or Enterprise. Field types and app restrictions can limit which mappings work and which directions they support.
Compare the available settings with your ownership sheet. If a required direction is unavailable, leave that field out until you have a supported approach. A connection that moves fewer fields correctly is useful. A connection that moves everything unpredictably creates a second job.
For owner fields, check the people as well as the properties. HubSpot documents that record owners must exist as users in both applications for owner sync to work. Do not assume that matching display names means the assignment is ready.
Separate sync direction from conflict handling
HubSpot data sync offers one-way and two-way configurations for supported apps and objects. The default application in the conflict settings determines which side takes precedence when resolving discrepancies. It does not override the chosen sync direction. HubSpot also states that an empty field in the default app does not change the value in the other app. See the data sync setup guide.
That default is a setting to understand, not a substitute for your field-by-field business decisions. Confirm that the complete configuration protects the values you care about. Avoid describing a field as accounting-owned while allowing sales edits to flow back into it.
For every important mapping, write a plain-language test: when this value changes here, this is the value we expect there. If the team cannot agree on the expected result, pause that mapping. Code will not settle the argument.
Match records before comparing their values
A correct field mapping still causes trouble if it updates the wrong record.
HubSpot's record matching guidance treats matching separately from field mappings and filters. Default identifiers include contact email, company name or domain, and product SKU or name. Available matching options vary by app and object.
Review records that could be confused with each other: two offices using one company name, a shared inbox used by several people, or products whose names changed while their SKUs stayed the same. Agree on what each record represents before deciding how to pair it.
If you choose a shared external identifier, check that both sides contain the same identifier. A HubSpot record ID and an accounting customer ID are not interchangeable just because both contain digits.
Test the awkward records
Use a small, representative set of records in an appropriate test environment or a carefully controlled pilot. Save the starting values and compare the result with your expected outcome.
- Conflicting values: Enter different values on both sides and confirm the intended result.
- Missing data: Check a blank source value, a blank destination value, and a missing required field.
- Later corrections: Change a value after the initial sync to verify ongoing updates.
- Unmatched records: Confirm whether a record should be created, excluded, or reviewed.
- Unexpected ownership: Test a record whose assigned user does not exist in the other application.
HubSpot has a test sync feature, but its scope is specific: a new object sync with an app being connected for the first time, in one direction from that app to HubSpot. Do not assume it is available for an existing two-way integration.
Also check your pilot filters. HubSpot documents that sync filters restrict which records initially enter the sync. Records already synced continue updating according to their mappings. A record leaving a filter is therefore not a reliable way to stop its updates.
Give ongoing corrections an owner
After launch, name a person who reviews sync failures and a person who can approve mapping changes. They may be the same person. They should not be a mysterious former employee whose name appears only in an old setup note.
Keep the ownership sheet beside the integration documentation. Update it when teams change their process, add fields, or introduce another application that writes to the same records.
If the native connector cannot support a necessary rule, define that gap before commissioning custom work. Our HubSpot integration cost breakdown explains the choices involved. Start with the built-in connection, then add only the work your process requires.
Make your next sync predictable
Choose one object, document its important fields, and test the changes your team makes every day. You should be able to explain where to fix a value and why that correction will stay fixed.
No Bounds Digital helps teams plan and configure HubSpot integrations around those decisions. Schedule a call to review your sync requirements and the places where your data needs a clear owner.
