Match the same customer.
Agree a durable customer key and how duplicates are resolved. A matching display name alone may not identify the same account.
Interlock03 / Integrations & data
Integrations & data
A connection needs
more than a connector.
Decide what moves, which system owns it and what happens when it cannot be accepted. That is the difference between a link and a reliable business handoff.
Source recordCRM
CRM
Approved order
Customer, sales owner, order reference and agreed net value.
Validated handoff
Destination recordERP
ERP
Order preparation
Matched customer identity, valid fields and a traceable source reference.
Try a small mapping exercise
Three columns.
One clear contract.
Choose the target field for each source column. Check the mapping to see the exact corrections needed.
Name the source of truth.
Sales may own opportunity details; Finance may own credit status. Write down which system and role can change each field.
Give failed records somewhere to go.
Track missing references, invalid values and rejected updates with a responsible owner and a safe retry rule.
Check what arrived.
Compare counts, values and sample records. Agree who signs off the result before increasing the live scope.
Put the next step in focus
Start with one
source-to-destination flow.
Bring the two systems, the business event and the fields you expect to move. API access, product limits and licences are validated during scoping.