crm-migration-consolidation

Coexist when:

• You want to preserve operational independence (each business unit runs its own sales motion, separate customers, separate forecasts)
• One CRM is clearly superior for its use case and switching costs more than it saves (e.g. Salesforce for complex enterprise deals, HubSpot for SMB transactional pipeline)
• The businesses integrate at finance/reporting only, not at the workflow level
• You accept the cost of dual systems, data reconciliation overhead, and the risk that reporting lags reality

Real example: HubSpot for marketing and SMB sales (fast, simple, direct-to-customer); Salesforce for enterprise sales (complex deal management, strong forecasting, compliance). Identity stitching happens at the warehouse/BI layer.

The coexistence integration layers: identity (one customer view across both), finance (unified ARR reporting), reporting (single KPI dashboard, two data sources).

System of Record: The Critical Decision

Before any data moves, decide for each object which system wins. This decision cascades down to field mapping, data quality validation, survivorship rules, and reconciliation.

| Object | Questions | Example Decision |

|---|---|---|

| **Account/Company** | Which CRM has the authoritative account hierarchy? Which owns the primary customer ID? Which system do customers reference in contracts? | Old CRM holds 8 years of hierarchy. New parent company policy requires single account ID. Decision: Migrate hierarchy into new CRM, generate new account IDs, keep old IDs as legacy_account_id for crosswalk. |

| **Contact** | Where does the primary contact record live? Which CRM is the source of truth for contact-to-account association? Who owns dedupe? | Two instances have overlapping contact bases. Decision: New CRM is system of record. Dedupe first in old CRM, then migrate. |

| **Deal/Opportunity** | Which CRM does revenue reporting feed from? Which stages drive forecast? Which system tracks multi-threaded deals? | Salesforce tracks complex enterprise deals better. New SMB pipeline lives in HubSpot. Decision: Salesforce is record for enterprise (>$50K), HubSpot for SMB. Deal associations link them. |

| **Subscription/ARR** | Which system tracks active subscriptions? Where do renewals originate? Where is churn recorded? | Legacy billing platform held subscription contracts, new CRM tracks usage. Decision: the billing platform is source of record for subscription status; CRM reflects current state only. |

| **Activity** | Email, calls, notes: which system logs them? Which is authoritative? Which do you archive? | Old CRM has 5 years of email history via Gmail sync. New CRM will sync going forward. Decision: Archive old CRM read-only; Gmail sync to new CRM from cutover onward. |

**Critical rule:** Every object must have an owner and a system. Ambiguity during the merge creates data chaos post-cutover.

The Data Harmonization Layer: 80% of the Work

Before you run a single migration script, harmonize the object models. This is where 80% of effort lives and where most projects fail.

### What to Harmonize

1. **Object model itself:** HubSpot has no native Lead object (contacts + lifecycle stage); Salesforce splits Lead vs. Contact/Account. Decide which model your merged org uses, then map both old models into it.

2. **Picklist values:** Two instances have "Negotiation" and "In Negotiation" and "In Contract" as deal stages. Decide the canonical pipeline and create the mapping before ETL.

3. **Property types and validation:** One CRM has phone as text (allows international formats); another stores only US numbers. Decide the harmonized format, then transform.

4. **Picklist dependencies:** Some properties only show up if another property holds a certain value. If both instances have different dependencies, design the merged logic first.

5. **Currency:** Multi-entity companies have GBP, EUR, and USD deals. Decide: store all ARR in one currency (EUR base with FX conversion) or preserve original at deal level?

6. **Lifecycle and deal stage definitions:** "MQL" means something different if marketing qualified is scored in one system and manual in another. Agree the definition across both orgs. This drives adoption later.

### Harmonization Anti-Patterns

• Assuming "we'll merge and clean up after cutover." Post-migration data work costs 3x pre-migration work (industry data). Clean first.
• Keeping every field because "someone might use it." Consolidation is a chance to delete custom fields nobody touches. Audit and kill ruthlessly.
• Migrating historical data in the wrong format. Email addresses with typos, phone numbers without country codes, company names with extra spaces. Standardize the source data, not the destination schema.

Deduplication and Identity Resolution

This is the number-one landmine. Two CRM instances hold overlapping accounts and contacts. Merging them without proper deduplication creates duplicate records, corrupts pipelines, and breaks reporting.

### Identity Resolution Framework

Think of this as a CDP identity problem. You need:

1. **Match keys:** Deterministic identifiers to match records across instances.

• For contacts: Email is the strongest (most unique, persistent across job changes). Secondary: phone.
• For accounts: Domain (company.com) is reliable. Secondary: legal company name + country.
• For deals: Deal name + creation date + amount (probabilistic).

2. **Fuzzy matching:** Exact-key matching alone catches only 60 to 70% of duplicates (vendor blogs: DigitalApplied, WinPure, DataLadder, 2026). Use fuzzy matching for near-duplicates: "Acme Corp" vs. "Acme Inc.", "Sarah Jones" vs. "S. Jones", email domain variations (old employee alias email).

3. **Survivorship rules:** When two records match, which one wins? Which fields come from which source?

• **Most recent:** Last-modified date usually wins (more current data).
• **Most complete:** Record with most populated fields wins.
• **Authoritative source:** HubSpot contact record has enriched data; Salesforce contact is incomplete. Take HubSpot as the base, merge in Salesforce only where HubSpot is blank.
• Example rule: "On email match, merge into new CRM record. Kee