Your CRM contains a new customer address, but your job management system still shows the old one. Both systems are connected, so which record should win? Without clear rules, an integration can move conflicting information around rather than resolve it.
Agree ownership for each type of information
There does not have to be one system that controls every field. Your accounting software might own invoice references, while the CRM owns sales contacts. A job system might hold the service location. Define ownership field by field where responsibilities differ.
A customer’s registered address, billing address and job address may all be valid and different. Treating them as one field can create errors even when the integration works exactly as configured.
Match the correct customer first
Use stable identifiers where possible. Names can change and two customers can share the same name. An email address may be shared by several staff or replaced when someone leaves.
A connection should retain the relationship between the customer IDs used by each system. Ambiguous matches should go to review rather than silently merging records.
Decide what happens when both records change
Automatically accepting the most recent edit can be unsuitable. A later change may be incomplete or come from a system that does not own that information. Agree which changes can be accepted automatically and which need a person to decide.
For example, a customer may request a billing address change through a portal while office staff update a service location. Those changes should be handled separately rather than allowing one to overwrite the other.
Make exceptions visible
Staff need to see which updates failed, which records are waiting for review and when information last moved successfully. An exception list should show enough detail to resolve the issue and identify the responsible person.
Keep a useful change history recording the source, previous value and accepted result. Retrying a failed update should not create a second customer record or repeatedly overwrite a corrected field.
Test the awkward cases
Include duplicate customers, missing identifiers, simultaneous edits, deleted contacts and temporary connection failures in testing. Agree what happens to older records before the integration starts sharing new changes.
Bring examples from your own systems
Digital Solutions can help map how records should move between applications. Start with a few real conflicts, using anonymised examples where appropriate, and explain the outcome your team expects.
Explore business software integration and software audit trails.