Integration Scoping Worksheet: Map Systems Before Connecting
The questions we work through before connecting a CRM, ERP, portal, or accounting system, laid out as a worksheet you can fill in with your own team: which systems, what data moves, which direction, how often, and what happens when it fails.
Why scope an integration on paper first
Most integration problems are decided before anyone writes code: two systems that disagree about who owns a customer record, a field that means different things on each side, or a sync that silently stops and nobody notices for a month. Working through these questions first makes the build smaller, cheaper to change, and easier to trust.
Fill in this worksheet with the people who use each system day to day. Where you don't know an answer, write "unknown". Those gaps are exactly what scoping is for.
1. The systems
For each system involved, note:
| System | What it's used for | Who administers it | Can it share data automatically (an API or export)? | Who owns the contract with the vendor? |
|---|---|---|---|---|
Include the informal systems too: shared spreadsheets, inboxes, and forms. They're often where data goes missing.
2. The records that move
List each kind of record that needs to move between systems: customers, contacts, orders, invoices, products, appointments, tickets.
For each one, answer:
- Which system is the source of truth? When two systems disagree, which one wins?
- Which direction does it move? One way, or both ways?
- What triggers the move? A new record, a change, a status update, or a schedule?
- How fast does it need to arrive? Within seconds, within the hour, or overnight?
3. The fields
For each record type, list the fields that must move, and check:
- Does each field mean the same thing in both systems? ("Status" and "stage" rarely line up exactly.)
- Do the formats match? Dates, phone numbers, currency, and product codes are the usual problems.
- Are there required fields on one side that are often blank on the other?
- Are there duplicate records today that would be multiplied by syncing?
4. Sensitive data
- Which fields hold sensitive data (payment, health, financial, personal)?
- Does any of it need to move at all, or can the integration avoid touching it?
- Who should be able to see it in each system?
- Are there compliance requirements that apply?
The safest sensitive data is the data an integration never handles. Payment details, for example, can usually stay with the payment processor entirely.
5. When things go wrong
- What happens if one system is down when a record needs to move?
- Who is told when a sync fails, and how?
- Can a failed record be retried without creating a duplicate?
- Is there a log showing what moved, when, and why?
An integration nobody is alerted about when it breaks will eventually break silently.
6. People and process
- Which manual steps does the integration replace, and who does them today?
- What changes in each person's daily work once it's live?
- Who signs off that the integration works, and against what checks?
Reading your worksheet
Count the "unknown" answers. A handful is normal. If most of section 2 is unknown, the first piece of work is deciding which system owns each record, not building anything. If section 5 is mostly unknown, plan for monitoring and alerts from the start rather than as an afterthought.
Next steps
Our system integrations work starts from these same questions, and How We Scope and Price explains how the answers shape the size of a project. If you'd like a second pair of eyes on your worksheet, book a strategy call.
Your Bottleneck Has a Fix.
Tell us what's slowing you down. On a strategy call we'll map the fix and what it takes — no pitch deck, no fluff, just engineering.
Book a Strategy Call