Data unification & migration
One record per customer, across every region and platform.
Duplicates, regional splits and ghost accounts make every number arguable. We consolidate to one record per customer, rehearse every change at full volume and keep the evidence to reverse it.
A merge you can take back
Every merge keeps a copy of both records first, so it can be reversed. Try it.
| North America record | Europe record | |
|---|---|---|
| Account name | Kestrel Textiles | Kestrel Textiles Ltd |
| Storefront ID | NA-30417 | EU-11802 |
| Owner | Priya Raman | Lukas Brandt |
| Renewal date | Mar 1, 2027 | Apr 15, 2027 |
| Billing contact | ap@kestrel.example | blank |
| Merged record | Rule that decided it | |
|---|---|---|
| Account name | Kestrel Textiles Ltd | Legal name from the signed contract |
| Storefront ID | NA-30417 and EU-11802 | Both kept, one per region |
| Owner | Priya Raman, Lukas Brandt | Regional owners kept side by side |
| Renewal date | Apr 15, 2027 | Taken from the latest signed term |
| Billing contact | ap@kestrel.example | Never replaced by a blank |
Example records with invented values.
Do these sound familiar?
What we deliver
- Identity resolutionMatching rules across CRM, commerce and warehouse IDs, with tie-break rules and a named system of record.
- Merge programsWaves rehearsed in a full sandbox, a premortem before execution, and a pre-image and rollback file for every record.
- Data lineageEvery record tagged to the platform that wrote it, ready for a re-platform cutover.
- Regional data modelsNorth America and Europe routing, currency and ownership that agree across every system.
- Cleanup with evidenceCriteria tested on real accounts first, backups before any delete and verification by record ID afterward.
- Storage & archivingAn archive strategy that frees space without losing history.
This practice in our case studies
- One record per customer, across two regions and three platformsCustomers existed twice, once per region. Each now has one record, with both regions’ storefront IDs, owners and terms side by side.
Questions before we start
How do you keep a migration reversible?
Every record a change touches is captured before the change, every wave ships with a rollback file, and the full run is rehearsed at production volume in a sandbox first.
Can you merge records that integrations depend on?
Yes, once the integrations are mapped. We check what each connected system does with a merged record before the first merge runs, and hold its callouts during the wave.
What do you test first?
The criteria. Every rule that decides what gets merged or deleted is run against real accounts and reviewed before it touches production.
Integrations and guides
- Salesforce and commercetoolsA move to commercetools without splitting customers in two: the same account IDs on the new platform, orders from both platforms counted once, and the old platform retired in planned steps.
Related practices
- Salesforce architecture & engineeringApex, Flow and Lightning simplified and secured, and documented so your own team can run the org.
- Systems integrationSalesforce connected to your commerce, warehouse, contract, billing and support systems, with one owner for every field and an alert when a sync goes quiet.
- Revenue & contract operationsThe deal, the signed contract and the bill kept in agreement, from the first quote to the renewal.
- AI agents & readinessIdentity, definitions and permissions fixed before any AI agent reads your records, with cost and accuracy measured.
Talk to us about your systems.
Tell us which systems are involved and what is going wrong. We reply within one business day, and new engagements begin in January 2027.
hello@feldtgroup.com