Use case
Post-Acquisition & Multi-Instance Cleanup
After an acquisition, you inherit a second Salesforce org, another HubSpot portal, or an additional Stripe account — each with its own customer data. The same companies and people exist in both, but nothing connects them. Anchord lets you connect all instances to one tenant, resolve overlapping identities, and see exactly where records came from — without writing back to any system.
The multi-instance problem
Acquisitions, regional expansions, and departmental splits create the same pattern: multiple CRM instances with overlapping customer data and no shared identity layer.
- Two Salesforce orgs — the acquired company's org and yours, with the same accounts under different IDs.
- Multiple HubSpot portals — marketing ran on one portal, sales on another, and both have "Acme Corp."
- Separate Stripe accounts — each business unit bills independently, but customers overlap.
Migrating everything into one system is a multi-month project. In the meantime, agents and pipelines writing across these systems create duplicates, update wrong records, and lose track of which instance is authoritative.
How Anchord handles multi-instance cleanup
Anchord supports multiple integrations of the same provider per tenant. You connect both Salesforce orgs, both HubSpot portals, or all Stripe accounts to the same Anchord tenant and resolve identities across all of them.
Connect all instances
Add each Salesforce org, HubSpot portal, or Stripe account via OAuth. Each instance gets its own label, sync status, and health monitoring in the Anchord console.
Ingest and resolve across instances
Records from every instance are matched to canonical AnchorIDs. When "Acme Corp" exists in both Salesforce orgs, Anchord links both source records to the same AnchorID — or flags the case for review if the match is ambiguous.
See where records came from
The Review Queue, target projection, and reports show instance labels on every record. You always know whether a record came from "SF Prod" or "SF Acquired" — no digging into raw source data required.
Merge and clean up
Use duplicate detection and merge to consolidate overlapping entities. Merge previews show exactly which source records from which instances will be combined. Merged entities accumulate identifiers from both sides into a single golden record.
What the operator sees
Multi-instance support is built into the Anchord console, not bolted on:
Per-instance integration cards
Each connected instance appears as its own card with status, last sync, and record counts. Connect another instance with one click.
Instance-aware health reports
Integration Health shows sync status, record counts, and cursors per instance — not collapsed to one row per provider.
Instance labels in review
The Review Queue shows which instance each candidate and incoming record came from, so humans can make informed decisions.
Per-instance sync and disconnect
Sync, toggle nightly sync, and disconnect are scoped to a specific instance. Disconnecting one org does not affect the other.
Important: what this does not do
- Read-only. Anchord ingests and resolves but never writes back to any connected system. Migration and cleanup writes are up to you.
- No cross-instance merge automation. Anchord identifies overlapping identities and recommends merges, but a human confirms before anything is combined.
- Matching is identity-level, not instance-aware. Scoring uses domain, email, provider IDs, and name + location signals. The matching pipeline does not apply different rules based on which instance a record came from.
Resolve identity across acquired systems
Connect all your instances. See the overlap. Clean up on your terms.