PUBLIC RESOURCE · INTEGRATION CHECKLIST
Seven things to check before connecting business systems.
Most integrations are easy to draw as two boxes and an arrow. The work that makes them dependable happens in the details.
General guidance, not a client case, security audit or complete technical design.
Ownership
Agree the source of truth for each record and field. Decide who owns changes and who can resolve disagreements between systems. A shared record does not mean both systems should overwrite every field.
Identity
Check how users, companies and records match. Prefer stable identifiers, define how existing records are linked and decide how to handle missing matches or duplicates before the first sync.
Mapping
List fields, statuses and workflows that differ. Document required values, transformations, time zones and what happens when one platform has no equivalent for a value in the other.
Permissions
Define what information must not cross boundaries. Confirm permission to access and process the data, use appropriately limited credentials and keep customer and internal information separated.
Failures
Plan for retries, conflicts, duplicates and loops. Decide which failures can be retried safely and which need a person. A repeated event should not create repeated actions or endless updates.
Visibility
Agree monitoring, alerts and human exception handling. Identify who sees a failure, how they find the affected record and what action they should take. A successful request alone does not prove the data is correct.
Recovery
Test normal operation and failure cases before rollout. Plan rollback, reconciliation, documentation and handover so the team can recover from an interrupted sync or an unexpected platform change.
Ready to look at your systems?
If you've got two platforms your team is manually keeping aligned, or a process that's become a workaround, I can help assess what it would take to improve it.