Sales needs a company name for a conversation. Finance needs the legal name for an invoice. Both can be correct. Syncing them into the same field means one may overwrite the other.

I would start with what each value means, who maintains it, and when the other system should accept a change.

01. Which system owns the value?

Assign ownership field by field, based on how the business uses the data. A system can own billing details without owning every field on the company record.

Suppose sales works in HubSpot and finance maintains customer records in an ERP. Sales uses a trading name. Finance records the registered legal name. Before syncing either, check whether they belong in the same field.

If they serve different purposes, keep them separate. If they represent the same value, agree which system maintains it and which direction updates should travel. Record those rules alongside the mapping.

02. What happens when the values disagree?

Now suppose both systems hold a billing address. Finance verifies an address in the ERP while sales enters a different one in HubSpot.

Decide how the integration should handle that conflict before update order decides which value survives.

  • Accept the owning system's value. If someone corrects the address elsewhere, they still need a way to get that correction back to the owner.
  • Accept the latest change. This needs comparable timestamps for changes to the field and an agreement that the newer value should win.
  • Hold the update for review. Someone must decide which value to keep. Agree what each system should show while they wait.

Define what an empty value means, too. A field left blank because nobody supplied the information is different from an instruction to clear it. Deleting a record is another case. Give each one an explicit rule.

03. Who resolves exceptions?

Before adding a review step, agree who will do the work and how they will correct the record.

For the billing-address example, finance could review the conflict, see both values, and make the correction in the system responsible for that field. The integration would then apply the agreed sync rule.

Decide where exceptions appear, how soon they need attention, and what happens to updates while a review is pending. Define how the record returns to normal synchronization afterward.

Sending a notification only covers the first step.

Put the rules in the mapping

Here is a filled-in example for that sales and finance setup. The field labels and rules are illustrative. Use the actual properties and decisions agreed for your systems.

Illustrative field ownership mapping
Value and ownerDestinationUpdate rule
Trading name, maintained by sales in HubSpotERP trading-name fieldCopy to the separate trading-name field. Do not replace the legal name.
Legal name, maintained by finance in the ERPHubSpot legal-name propertyAccept ERP changes. Route corrections from sales to finance.
Billing address, maintained by finance in the ERPHubSpot billing-address propertiesKeep the ERP address while finance reviews conflicting values. Resume with the approved ERP value.
Missing billing address in an ordinary ERP updateExisting HubSpot billing addressLeave the existing address unchanged. Treat an explicit request to clear it as a separate case for review.

A checklist before the build

For each field, write down enough for someone outside the planning conversation to understand what should happen.

  1. What does the value mean to each team?
  2. Which system is responsible for maintaining it?
  3. Which direction should changes travel?
  4. What happens when both systems change it?
  5. How should missing values, requests to clear a field, and deleted records be handled?
  6. Who reviews exceptions, and where do they make corrections?
  7. How will you test conflicts and check the results?

I would bring a few conflicting example records into that conversation. Work through what should happen to each one, including who has to act when the integration cannot resolve it.

If an example needs separate fields or a person to review it, put that in the mapping before the sync starts applying the same rule to every record.

Choosing a connector, automation platform, or custom integration Before you retry that request.