Choosing Stable Identifiers Between Business Systems
Integrations need a dependable way to recognise the same item on both sides. A display name may change or be shared by several records, making it a poor matching rule.

Document the identifier relationship
Identify the source key, destination key and any mapping table needed between them. Decide how new mappings are approved and how missing or duplicate identifiers are handled. Preserve the original values so a transformation can be investigated later.
Practical checklist
- Avoid matching solely on display names.
- Check uniqueness.
- Record mappings explicitly.
- Route ambiguous matches for review.
How to review the result
Test renamed items and repeated names. The integration should continue to identify the intended record or stop with a clear exception, rather than guessing.