A customer changes their phone number with your delivery team, unsubscribes from your emails, and pays an invoice late. Each of those facts lands in a different system. A month later, sales calls the old number, marketing emails someone who unsubscribed, and nobody knows the account is overdue.
The fix isn’t one giant system. It’s deciding which system owns which data.
Decide the owner of each kind of data
A typical small business setup:
| Data | Source of truth | Syncs to |
|---|---|---|
| Contact details (name, email, phone) | CRM (service business) or store (online store) | Email platform, inbox, accounting |
| Marketing consent and unsubscribes | Email platform (email), WhatsApp tool (WhatsApp), recorded back to CRM | All tools that send marketing |
| Orders, products, stock | Store | CRM (summary), accounting |
| Deals, pipeline, sales activity | CRM | Reporting |
| Invoices, payments, VAT | Accounting | CRM (status) |
| Conversations | Shared inbox / CRM | CRM timeline |
Your answers may differ. What matters is that each row has one owner.
Rules that keep it true
- Edit in the owner, not the copy. If the store owns addresses, changing one in the CRM gets overwritten or causes conflict.
- Sync one way where possible. Two-way syncs are where conflicts and loops happen. Use them only where truly needed, and know which side wins.
- One matching key. Email and phone in
+971format, consistently. Without a reliable key, syncs create duplicates. See CRM data hygiene. - Opt-outs everywhere, fast. An unsubscribe or WhatsApp STOP must reach every tool that sends marketing.
- Monitor the syncs. Native integrations and automations fail silently. Alert on errors. See error handling in n8n.
- Write it down in the data ownership map, and update it when tools change.
Common traps
- Spreadsheets as hidden sources of truth that never sync back. See outgrown spreadsheets.
- Two tools both “owning” contacts with a two-way sync fighting each other
- Consent stored only in the email platform, so the WhatsApp tool doesn’t know someone opted out
- Accounting customer names that don’t match CRM company names, making payment status impossible to link
Why it matters for compliance
The UAE’s data protection law gives people rights to correct their data and to object to direct marketing. With a clear source of truth, a correction or opt-out is made once and flows everywhere, instead of being missed in one tool.
Frequently asked questions
Shouldn’t we just use one all-in-one platform?
Suites (for example Zoho or HubSpot with add-ons) reduce the number of syncs. You still need to decide which module owns what.
How often should syncs run?
Contact and consent changes: as close to real time as practical. Order summaries and invoice status: hourly or daily is often enough.
What if two systems both need to edit the same field?
Pick a winner (usually the most recent edit from the owner system) and document it. Avoid where you can.
If you’d like your customer data mapped and your syncs set up properly, that’s part of our tech stack service.
Free download · Excel template
Data ownership map
Map each kind of customer data to its source-of-truth system, where it syncs to, in which direction, how often and with which matching key.
Download itNo sign-up. Opens in Excel, Google Sheets or Numbers.
Rather have it done?
This is the kind of work our tech stack service covers. Tell us where you are today and we’ll reply with a plan and a fixed price.
Let’s talk