Audit company overlap before a CRM migration
Review duplicate companies across both exports while every source ID is still intact.
Two company masters need to become one migration plan, and your team has to decide which records should stay separate.
Create a Free workspace and upload company records with a unique source reference. Review local duplicates first, use paid depth when registry checks are needed, and take the output back to your migration process. Contact us separately to scope an assisted Merge Safety Sprint.
Keep each source record traceable
The fictional CSV shows the column layout. Read the instructions, replace every example row and preserve identifiers as text.
Two pages carry what this one only points at: where assurance stands, and every figure with the population it was measured over.
trust and security →every figure, with its population →On this page
Data migration leads, MDM owners and RevOps teams combining company records after an acquisition.
Buying breadth as the product: we hold a fraction of an incumbent’s records and are not building a global company graph. Entity Bind resolves companies and organisations only. It does not resolve people, vessels, bank-account ownership, sanctions exposure, emissions or geolocation, and its results may not be used for eligibility decisions about individuals, including employment, credit and tenancy.
How it actually goes wrong
What causes it, what it costs when nobody notices, and the part of it a resolver can reach.
An acquisition brings overlapping accounts, supplier records and naming conventions into the same migration. The same company may have a different ID in each system. A group may also have several legal subsidiaries behind one website. A join on the name or domain can confuse the two problems.
Keep a copy of each source export before changing it. Review proposed groupings with the registration jurisdiction, identifier and evidence beside each row. Your migration team decides and applies changes in the target system; Entity Bind returns a reviewable file and writes nothing to your CRM, ERP or MDM.
If that reads like your week, create your Free workspace and upload a company CSV to see which rows match and which need review. Contact us separately if you want a guided first file.
Start freeWhat we do about it
Each of these runs today. Where one needs a column you might not have, or fails in a particular way, the sentence says so.
- 01
Keep both systems' IDs
Build source_ref from the system and its original ID, such as crm-a:0001 and crm-b:0001. Keep the original fields too. Use that unique reference as the key column so your team can join results back to either export. - 02
Review legal identity before survivorship
Check which rows describe the same legal company before deciding which billing address or account owner should survive. A parent and subsidiary may stay separate even when the group domain agrees. - 03
Route uncertain records to a steward
Retain unresolved rows with their causes and any missing field that could settle the identity. A migration deadline does not turn a similarity score into company evidence.
Which of these is your export?
One export usually sits in three of these at once. Your rate is set by the columns still standing once the names have been stripped back to a comparable form.
Company name, issuing jurisdiction and registration number
Preserve leading zeros and jurisdiction prefixes. Supplied identifier agreement or conflict can settle comparisons before deeper work. Confirm the identifiers are correctly attached to the source rows.
No published rateThis shape has not been measured on a published fixture, so the behaviour above carries no rate.
Company name with domain, address or postcode
Keep each signal in its own column. Shared group contacts need scrutiny, and sparse rows can remain unresolved.
No published rateThis shape has not been measured on a published fixture, so the behaviour above carries no rate.
- Identifier — A company number or an LEI
- 100% 317/317
- Name and postcode — A company name and a registered postcode
- 98.74% 313/317
Zero wrong bindings were observed across the historical six-shape recording and the separate domain fixture. Observed correctness was 1.0000 on accepted outcomes; this does not guarantee an error-free new workload.
317 live GB companies sampled from the 2026-08-01 Companies House snapshot, with same-name siblings included. Identifier-rich arrivals seed the catalogue before the weaker input shapes are evaluated. Historical results on an internal UK fixture with a preloaded catalogue. The September 5 replay has no full-prompt-verified calls and cannot establish current calibration. No independent customer holdout or global coverage claim. The whole table, including the shapes this page does not use, with the safety results and an account of what none of it demonstrates.
Internal fixtures only. The historical 2026-08-29 per-tier recording covers 317 GB companies with identifier-rich arrivals seeding the catalogue first; the context tier includes country and registered-town prose. Its legacy replay has no full-prompt-verified calls and cannot certify current calibration. The September 5 CI reports cover 1,176 labelled pairs and 705 records over 250 companies using offline stubs. These are not independent customer holdouts or live production validation; the 99% minimum-input product target remains unmet. Scope is company and organisation identity only — not people, vessels, bank-account ownership, sanctions or emissions. Results may not be used for eligibility decisions about individuals, including employment, credit and tenancy.
Not sure which of these your export is? Create your Free workspace and inspect your own CSV columns. For an assisted composition preview, contact us with the file: we tier each row by its strongest surviving signal before quoting a Sprint.
Start freeA fictional two-export review
One pass, in order, including the rows that do not resolve. The interesting rows are always the ones at the end.
crm-a:0001 and crm-b:0001 describe Tutorial Willow Limited with the same supplied UK company number. crm-b:0002 describes Tutorial Willow Holdings with another number and the same group website.
- 01Preserve the three source references.
- 02Review identifier agreement for the first pair.
- 03Keep the different legal company separate while checking the source identifiers.
- 04Choose any surviving CRM field values under your own migration controls.
A proposed identity grouping and a separate company to retain, each traceable to the original export. This is a teaching example, not a recorded product result.
Company identity, group membership and the account record you choose to retain are separate decisions. This audit supports the identity review; your team owns the migration and writeback.
That example is ours. The one worth having is the same walk-through on eight rows of yours.
Start freePrefer to put it to a person? Talk to us instead →
What this will not do
Each of these is a decision we intend to keep. Read them before you scope the work.
- Company and organisation identity only. This does not merge people, contacts, bank accounts or sanctions records.
- Free compares the supplied records without registry or model calls. Deeper checks require a paid plan and available sources.
- A supplied company number can be mistyped or attached to the wrong row. Review the evidence before applying a change.
- The export and reversal map are not a rollback guarantee for a CRM migration. Keep your own backup, before values and change controls.
- No resolution-rate, financial-saving or completion-time forecast is made for your migration file.
We will not tell you how many dangerous merges we will find
We do not promise a count of dangerous merges prevented, and you should distrust anyone who does before they have seen your file. Zero is a normal, honest result: two rows carrying contradicting company numbers are refused outright and never reach the guard that would have counted them.
What this product does not have — no SOC 2, no external validation of the accuracy figures, no customer holdout — is published in full, with the retention, erasure and tenancy detail a security review asks for. Read the trust page →
Check these scope limits before integrating. Free signup lets you inspect your own company CSV; if a requirement falls outside the published scope, contact us and we will tell you whether it is supported.
Start freeThe method behind this, at length
3 articles that carry the working this page summarises.
- GuideHow to deduplicate a CRMExport, preview, tier the file, run it, review the abstentions, merge with receipts, measure. The full sequence for deduplicating a CRM account object without making a wrong merge you cannot undo.
- GuideSurvivorship and golden recordsMerging records is only half the job. Field-level survivorship, source precedence, temporal facts, per-field provenance, and why last-confirmed beats first-seen.
- GuideChoose a company matching tool you can defendEvaluate company matching on your records. Download a scorecard for identifier conflicts, unresolved rows, evidence, coverage, controls and pricing.
The same pipeline, in other people's words
One product, described 6 other ways. If your team has a different vocabulary for the same file, start from the page that speaks it.
CRM and RevOps
Which accounts are one company, which merges to refuse, and a receipt for both.
Master data management
An independent admission policy beside the platform you already run.
Supplier master and accounts payable
Duplicate vendors, remittance conflicts and concentration you cannot see.
KYC and onboarding
Counterparty identity with a receipt that survives seven years.
Reference data
Every identifier a company is known by, each separately cited — and the ones nobody holds.
AI agents
A counterparty check before the agent acts, and a receipt for what it acted on.
Start with your own company records.
Create your workspace, verify your email and run your first company file. The Free plan needs no card. Create API keys in your workspace when you need an integration.
300 credits. No card.
For a guided review of your file, explore the Merge Safety Sprint →
Questions about post-merger audit
Will Entity Bind merge the two CRMs for us?
No. It returns company identity decisions and evidence keyed to your source references. Your team reviews the output and applies any CRM or ERP changes under its own controls.
Is the migration template real company data?
No. Its rows and identifiers are fictional teaching inputs. Replace them with your own authorised company records and preserve source IDs and text formatting before upload.