Enter once, then enter again, then again
A new customer signs. Someone adds them to the CRM. Then someone creates them in Xero so they can be invoiced. Then someone sets them up in the job management tool so the team can book work. Same name, same address, same contact, typed three times by two different people.
Then the customer moves office. The CRM gets updated. Xero does not. The engineer turns up at the old address, and the invoice goes there too.
Nobody thinks of this as a big problem, because each entry only takes a few minutes. But it happens for every customer, every order and every change, all year.
The real reason the systems do not talk
It is tempting to blame the software. Usually each tool is fine. The cause is that they were chosen at different times, by different people, to solve different problems, and nobody was asked to decide how they fit together.
Without that decision, there is no answer to a simple question: which system is right? If the CRM and the accounts package disagree about a phone number, who wins? Until someone answers that per field, connecting them just copies confusion faster.
Off-the-shelf connectors in Zapier or Make can help, but they often get set up as one-way copies with no plan for updates, deletions or conflicts, and then quietly stop when a field changes name.
What the retyping is really costing
- Staff time spent on entry that adds nothing, repeated for every record.
- Typos that differ between systems, so reports never quite agree.
- Customers contacted at old addresses or with the wrong details.
- Invoices delayed because the customer was not yet set up in accounts.
- A general distrust of the data, so people keep their own side lists.
The side lists are the tell. Once staff stop trusting the systems, they start keeping private notes, and now you have a fourth copy.
How we connect your systems properly
| Data | Typical owner | Flows to |
|---|---|---|
| Customer and contacts | CRM (HubSpot, Salesforce, Pipedrive) | Accounts, job system |
| Invoices and payments | Xero or QuickBooks | CRM for visibility |
| Jobs and schedules | Job management tool | Accounts for billing |
| Products and prices | Stock or ecommerce system | Quotes and invoices |
That table is only an example. The first thing we do is agree yours, field by field.
- Map every place a piece of data is entered today, and who enters it.
- Agree the source of truth for each field with you, and write it down.
- Build an integration layer that listens for changes through each system's API or webhooks and pushes them to the others.
- Match records reliably, using IDs rather than names, so 'J Smith Ltd' and 'John Smith Limited' do not become two customers.
- Validate before writing: missing VAT numbers, invalid postcodes or duplicate emails go to an exception queue for a person to resolve.
- Log every sync, so when something looks wrong you can see exactly what moved and when.
For simple cases we use Zapier, Make or n8n and document the setup. Where volumes are higher or the logic is more involved, we write a small service that we can test and monitor.
One entry, one set of details
Your team types a customer in once, in the system that owns it, and the rest follow. Changes flow the same way. When a record cannot be synced cleanly, it lands in a short queue with the reason, rather than silently failing.
The monthly job of reconciling the CRM against the accounts package goes away, because they are no longer independent copies.
It also changes how you add software in future. When the next tool arrives, the question is no longer 'who will type things into it?' but 'which fields does it own, and which does it receive?'. That is a short conversation and a small extension to the integration layer, rather than another person's afternoon each week.
Signs you are paying for double entry
- New customers are set up by hand in more than one system.
- Your CRM and accounts package disagree on basic details.
- Someone keeps a spreadsheet to track what has been entered where.
- An existing Zapier or Make automation broke and nobody noticed for a while.
- Staff ask 'which system is right?' more than once a week.