Your CRM lists one billing address. Your invoice tool lists another. A staff member edits both, but tomorrow an integration copies the old address back. Choosing a “main customer system” does not solve the problem until someone defines who can change that field.
Assign authority by field and business action. The system that owns account relationships may differ from the one that owns invoice addresses. Your team needs a rule for disagreement, including who can approve a correction and where the correction starts.
Map the field, the editor, and the receiving tools
Consider a hypothetical service company using a CRM, accounting software, and a booking tool. It wants each system to keep its useful role. The operations manager fills this map with the people who maintain the records.
| Field | Authoritative system | Permitted editor | Conflict rule |
|---|---|---|---|
| Customer account ID | CRM | Account administrator | Match by stable ID; hold ambiguous records for review. |
| Billing address | Accounting software | Billing team after customer confirmation | CRM displays the accepted address; it does not overwrite it from an older contact record. |
| Relationship owner | CRM | Sales manager | Booking tool receives the owner; changes start in CRM. |
| Appointment contact | Booking tool | Scheduling team for that booking | Keep the appointment-specific contact separate from the account owner. |
| Marketing preference | Designated preference store | Customer or authorized support process | Preserve the preference and its source; do not infer permission from an address update. |
This example describes an operational design, not a legal determination about consent. Your business should have the relevant privacy owner review its rules before implementing them.
Use a conflict to test the map
In the example, the customer changes its billing address through the billing team on Tuesday. A Wednesday CRM import contains Monday's address. Under the agreed map, the import cannot replace the accounting address. The integration records the conflict and routes it to billing if the customer details still require clarification.
“Newest value wins” would fail here if the Wednesday import has a new import timestamp but an old customer value. Define what each timestamp means. A sync time shows when a system received a record; it may say nothing about when a person confirmed the field.
Test a second conflict: a booking contact uses a personal email while the company account uses a finance inbox. Both may be correct for different purposes. Merging them into one contact field would destroy information. Give the fields separate names and uses instead of asking which email wins.
Make unresolved records visible
Decide where staff can see held records. A hidden error log can leave an invoice blocked for days. The billing team needs the customer ID, competing values, origin, and reason for the hold. It also needs a way to accept a correction without making the same edit in three tools.
Record the source of a manual override and how long it applies. If a manager authorizes an exception for one invoice, that exception should not silently redefine the customer's permanent address. Scope matters as much as system ownership.
Before connecting live records, run the map against a small set of invented conflicts. Include a missing ID, an old value arriving late, and a legitimate appointment-specific difference. Ask the receiving team to resolve each case using the instructions alone. Revise any rule that requires the original designer to explain it.
Define what an empty value means
Add a rule for blank fields before configuring synchronization. A missing address in an import could mean the source never collected it, or a staff member could have deliberately removed an incorrect value. Those cases deserve different handling. In the hypothetical map, the billing team should decide when a blank can clear an accepted address and what evidence supports that action. Have the integration hold ambiguous deletions instead of interpreting every empty field as a command to erase useful customer information.
Our guide to one system versus connected tools covers the broader stack decision. A field map handles the disagreements that remain when you keep several systems. For help implementing those rules, see custom software development.

