Choose the source of truth
For each shared entity, such as a customer, item or order, decide which system owns it and which systems receive copies. Define stable identifiers and field mappings. Two applications independently updating the same field can create conflicts that a connector alone cannot resolve.
Inspect the actual interface
Collect API documentation, authentication requirements, rate limits and sandbox access through an approved channel. Check pagination, event delivery and version changes. Confirm whether the workflow needs immediate updates or whether a scheduled batch is sufficient.
Design for partial failure
Describe what happens when one system accepts a change and the next is unavailable. Use traceable requests, safe retry rules and a way to identify duplicates. Plan a reconciliation report so operations teams can locate missing or inconsistent records.
Test migration separately from synchronization
A historical import and a continuing sync have different risks. Test mappings on a representative sample, compare record counts and totals, and plan a cutover with rollback criteria. Assign an owner to resolve exceptions after launch.
Bring this to your project brief.
- Systems, entity owners and field mappings
- API constraints and anonymized payloads
- Reconciliation, migration and rollback requirements
Use general descriptions or anonymized examples. Do not put credentials, personal records or confidential documents into the brief.
Prepare your project brief