The symptom
We double-enter the same info in three systems
The short answer
Re-keying happens because no one has ever decided which system is allowed to be right. Your CRM thinks it owns the customer. Your accounting package thinks it owns the customer. Your scheduling tool has its own copy with a slightly different phone number. With three claimants and no ruling, the only reconciliation mechanism left is a person typing the same thing three times and quietly resolving the differences in their head.
The fix is a decision before it is a technology. For each kind of record — customer, job, invoice, contact — name exactly one system as the master. Everything else receives a copy and is not allowed to originate one. Once that ruling exists, the integration is mechanical: the master pushes changes outward, the others accept them, and conflicts have an obvious winner. Without the ruling, integration makes things worse, because now the disagreement propagates automatically.
Do the mapping on paper before anyone connects anything. It usually takes ninety minutes with the two or three people who actually use the systems, and it routinely finds a field that three departments each believe they own, which is the real problem hiding under the symptom.
How businesses end up here without doing anything wrong
Every system was a good decision on its own day. The CRM was bought to stop losing leads. The accounting package came from the bookkeeper. The scheduling tool was adopted by operations because the CRM could not do routes. None of these purchases was a mistake, and none of them was made with the others in view.
The re-keying then becomes invisible because it is bundled into other jobs. Nobody says they spend four hours a week copying data; they say setting up a new customer takes about twenty minutes. Multiply that by new customers per week across three people and you have a real number that has never once appeared in a management meeting.
Why the integration is the easy half
Most business software published in the last decade has an API, and the common pairs — CRM to accounting, scheduling to CRM — are well-trodden. Connecting them is genuinely not the hard part, and off-the-shelf flow tools handle a surprising amount of it.
The hard part is what happens when the two copies disagree, which they will within a week. A serious build answers that up front: which field wins, what happens to a record deleted on one side, what happens when a sync fails at 2am, and who sees the failure. A weekend integration answers none of those and fails silently, which is how businesses end up trusting neither system and going back to typing.
Before and after — yours to use, nothing to buy
Before and after: the system-of-record map
Fill this in for your own business before you talk to anyone about integration. The exercise is the artifact. Each row names a record type, what happens today, and what the target looks like once one system is declared the master.
| Step | Today | After |
|---|---|---|
| New customer | Typed into the CRM by sales, into accounting by the bookkeeper, and into scheduling by the coordinator. Three spellings of the same company. | Created once in the CRM. Accounting and scheduling receive it automatically and cannot create their own. |
| Contact details | Updated wherever the customer happened to mention the change. The other two copies stay wrong forever. | Edited only in the master. Downstream copies update on change, and the other systems make the field read-only. |
| Job or project | Created in scheduling, then re-created in the CRM so sales can see it, then referenced by a different number in accounting. | One job identifier, generated by the master, carried into both other systems as a reference field. |
| Invoice | Assembled by hand from the job record, then keyed into accounting. Line items are retyped from the estimate. | Drafted in accounting from the completed job record, with line items carried over. A person reviews and sends. |
| When two copies disagree | Whoever notices fixes the one in front of them. The disagreement survives in the other two. | The master wins, by written rule. Conflicts are logged, not silently resolved. |
| When a sync fails | Not applicable — there is no sync, which is why nothing ever fails visibly. | The failure raises an alert with the record attached and retries. Silence is treated as a fault, not as success. |
The last two rows are what separate a build from a weekend project, and they are the rows most vendor demonstrations skip. Ask about them specifically. To put a number on the cost of doing nothing: four people re-keying three and a half hours a week each, at a fully loaded $36 an hour with 70 percent of it rules-based, is 9.8 hours a week and 470 hours a year — an illustrative $16,934 of annual capacity, against an illustrative $11,000 build, giving a payback of about 7.8 months. Those figures are output from Soxoa's public estimate_automation_roi tool on those inputs, and are illustrative rather than a quote.
Terminology bridge
What consultants call this
The moment you search for help with this, you will meet these words. They all describe parts of the same decision.
The one system allowed to hold the authoritative version of a given record. The decision underneath everything else.
The formal discipline of keeping that authoritative version consistent. Enterprise-sized name, small-business-sized problem.
Whether both systems can change the record or only one can. One-way is dramatically safer and usually enough.
Integration platform as a service — the category containing the off-the-shelf connector tools.
Running the same sync twice does not create two customers. Ask any builder how they guarantee it.
If someone proposes a two-way sync before you have named a master, they have skipped the only decision that matters.
Common questions
Fair questions
Can we just use an off-the-shelf connector?
Often yes, and you should try that first. Off-the-shelf connectors handle common pairs well when the mapping is simple and the failure cost is low. They struggle when records have to be matched rather than copied, when three systems are involved instead of two, and when someone has to be told that last night's sync failed.
What if two systems genuinely both need to be editable?
That happens, and it is a real design decision rather than a mistake. The answer is field-level ownership: the CRM owns contact details, accounting owns payment terms, and each system makes the other's fields read-only. It is more work to specify and much less work to live with.
How long does an integration like this take?
It depends almost entirely on how many record types you are willing to leave alone. One record type, one direction, with a real error path, is a small piece of work. All records in both directions is a project, and usually not the one worth doing first.
Sources
Where this comes from
- CRM API: deals
HubSpot developer documentation
Example of a CRM exposing pipeline stage and last-activity date as readable fields — the raw material for a stale-deal alert.
- Accounting API: Invoice
Intuit QuickBooks Online developer documentation
Shows the fields an invoice actually needs, and that invoices can be created from another system rather than keyed in.
- Overview of cloud flows
Microsoft Power Automate documentation
Reference for what an off-the-shelf flow tool can and cannot do on its own.
- Employer Costs for Employee Compensation
U.S. Bureau of Labor Statistics
Published series on benefits and payroll costs as a share of total compensation — use it to turn a wage into a fully loaded rate.
- Annual Business Survey
U.S. Census Bureau
Free public data on business technology use and characteristics, if you want a baseline outside vendor marketing.
Last reviewed: September 1, 2026 · every source link checked on that date
Where to go next
Three useful next reads
Honest ranges for build, licence and maintenance costs, with the recurring costs included.
Read it →See the evidenceAccounting assessment exampleA worked assessment of close intake and exception review, with the assumptions and limitations stated openly.
Read it →What it costsAutomation ROI calculatorRun your own headcount, hours and rate through the interactive version of the arithmetic above.
Read it →Free · No strings
Get the system-of-record map drawn for your business
Share your company, website, and email. We research your operations, show the sources and assumptions, and send a private assessment link when it is ready — no call required to read it.
Other things owners tell us