A staff member copies a customer address from an email into a CRM, then into an order system, then into a delivery sheet. It looks like a typing problem. Often it is also an ownership problem: each system needs the value, but no one has defined which record is authoritative or how changes travel.
Follow one field across the workflow
Choose a repeated field and record where it first enters, who can edit it, where it is copied, how errors are corrected and which output depends on it. Check whether the apparent duplicates are truly the same thing. A billing address, service location and delivery point may look similar while serving different purposes.
If two systems both allow edits, define precedence and reconciliation. If one is authoritative, document how downstream systems refresh and how conflicts surface. An integration can copy data quickly while spreading an incorrect value more efficiently.
Automate only after the rule is clear
Before building a sync, settle identity matching, field meaning, allowed edits, timing, failure handling and the owner of exceptions. Test a normal update, a conflicting update and a rejected record. Decide how the team will know the sync ran and where someone resolves a mismatch.
A practical inspection
- Select one repeated field and trace its origin.
- Confirm whether repeated values represent the same business meaning.
- Name the authoritative record and permitted editors.
- Define conflict, refresh and failure rules.
- Test a normal change and an exception before automation.