CRM Migration Guide: Moving from Salesforce or HubSpot Without Losing Data

CRM Migration Is Not as Scary as Vendors Want You to Think#

The fear of CRM migration keeps thousands of businesses trapped in platforms that no longer serve them. They pay too much, use too little, and dread the switching project enough to tolerate another year of frustration.

Here is the truth: CRM migration is a project, not a crisis. It takes planning, effort, and patience — but it is not the data apocalypse that your current vendor's retention team wants you to believe. Most small-to-mid-sized business migrations (under 100,000 records) can be completed in 2-4 weeks with proper planning. Larger migrations might take 4-8 weeks.

We have helped teams migrate from Salesforce, HubSpot, Pipedrive, Zoho, and spreadsheets. This guide covers everything you need to know — from the initial audit to post-migration verification.

Phase 1: Pre-Migration Audit (Week 1)#

Before you export a single record, you need to understand what you have. Most CRMs accumulate years of data, and not all of it is worth migrating.

Step 1: Inventory Your Data#

Create a spreadsheet listing every object/entity in your current CRM:

Key decisions during inventory:

• Closed/lost deals: Do you need to migrate deals that closed 3+ years ago? Usually the answer is no. Migrate open deals and recent closed-won deals (last 12-24 months) for reporting continuity.
• Activities and notes: Call logs, email logs, and notes from years ago have declining value. Consider migrating only the last 12 months, or consolidating older activity into a summary note on each contact.
• Duplicates: Migration is the perfect time to deduplicate. If you have 12,000 contacts but 2,000 are duplicates, clean them up before migrating.

Step 2: Audit Your Automations#

List every automation, workflow, and sequence in your current CRM:

• Trigger conditions
• Actions performed
• Whether it is still active and used
• Whether it needs to be recreated in the new platform

Most CRMs accumulate automation cruft over time — workflows created for a campaign two years ago that are still technically running, sequences that no one monitors, and triggers that fire but no one acts on. A migration is a chance to be intentional about what automation you actually need.

Step 3: Identify Integration Dependencies#

List every tool that integrates with your current CRM and how data flows:

• Email (Gmail, Outlook) — bidirectional sync?
• Calendar — meeting creation, scheduling links?
• Marketing tools — lead source tracking, campaign attribution?
• Accounting — invoice sync, revenue data?
• Support — ticket creation, customer data sync?
• Phone system — call logging?
• Custom API integrations?

For each integration, determine whether the new platform (a) handles it natively, (b) supports the same integration, or (c) requires a different approach. All-in-one platforms like Coherence often eliminate several integrations entirely because email, chat, and docs are built in.

Phase 2: Data Mapping and Preparation (Week 1-2)#

Step 4: Map Fields Between Platforms#

Create a field mapping document that connects every field in your old CRM to its equivalent in the new platform:

Pay attention to:

• Data type mismatches: A text field containing "yes/no" values might map to a checkbox in the new system. Clean the data first.
• Dropdown value differences: If your old CRM has "Qualified Lead" and the new system uses "SQL," you need to map these values.
• Required fields: If the new platform requires fields that your old data does not have, you need a plan for handling empty values.
• Relationship fields: How contacts link to companies, deals link to contacts, and custom objects link to each other. These relationships need to be preserved.

Step 5: Export and Clean Your Data#

Export your data from the old CRM. Most platforms support CSV export:

• Salesforce: Data Export (Setup > Data > Data Export) or Data Loader for large volumes
• HubSpot: Export from each object's list view, or use the API for bulk export
• Pipedrive: Export from Contacts, Deals, and Activities views
• Zoho: Export from module list views or Backup feature

After export, clean the data:

1. Remove duplicates (use a tool like Excel's Remove Duplicates or a deduplication service)
2. Standardize formats (phone numbers, addresses, dates)
3. Remove clearly invalid records (test data, spam entries, contacts with no useful information)
4. Fill in critical missing data where possible
5. Split or merge fields to match the new platform's structure

Step 6: Prepare Relationship Mapping#

This is the step most people miss and then regret. CRM records have relationships — a contact belongs to a company, a deal is associated with a contact and a company, activities are linked to deals.

When you import data into a new platform, you need a way to reconnect these relationships. The standard approach:

1. Export each object with its ID from the old system
2. Import companies first and record the new IDs
3. Import contacts with the old company ID, then use the mapping to reconnect them to the correct new company record
4. Import deals with the old contact/company IDs, reconnect using the mapping

Most modern CRM platforms handle this through a matching field (usually email for contacts, domain for companies) that automatically links imported records.

Phase 3: Import and Verification (Week 2-3)#

Step 7: Test Import with a Small Batch#

Never import your full dataset on the first attempt. Import 50-100 records from each object type and verify:

• Fields mapped correctly
• Relationships preserved (contacts linked to right companies)
• Data types rendered properly (dates, currencies, dropdowns)
• No truncation of long text fields
• Special characters handled correctly

Fix any issues in your mapping or data before the full import.

Step 8: Full Data Import#

Import your cleaned, mapped data in the correct order:

1. Companies/organizations (these are the parent records)
2. Contacts (link to companies via email domain or explicit mapping)
3. Deals/opportunities (link to contacts and companies)
4. Activities and notes (link to associated records)
5. Custom objects (in dependency order)

Import during a low-usage period. For small teams, this might be a weekend. The import itself is usually fast (thousands of records import in minutes), but verification takes time.

Step 9: Verification Checklist#

After import, verify systematically:

• Record counts match expectations (old count minus excluded records)
• Spot-check 20 random contacts — all fields populated correctly
• Spot-check 10 random companies — contacts linked correctly
• Spot-check 10 random deals — amounts, stages, and dates correct
• Custom fields rendering properly
• Search works (find specific contacts by name, email, phone)
• Reports produce reasonable numbers
• No orphaned records (contacts without companies, if that is not expected)

Phase 4: Rebuild Automations and Workflows (Week 2-3)#

Step 10: Recreate Essential Automations#

Referring to your automation audit from Phase 1, recreate only the automations you actually need. This is a chance to simplify. Common automations to recreate:

• Lead assignment and notification
• Follow-up reminders for stale deals
• Welcome email sequences for new contacts
• Stage change notifications
• Activity-based alerts (no activity on a deal for X days)

If your new platform includes AI agents (like Coherence's Autopilot), many of the automations you previously built as rigid workflows can instead be handled by agents that assess context and act intelligently.

Step 11: Set Up Integrations#

Reconnect your essential integrations:

• Email sync (connect Gmail/Outlook)
• Calendar sync
• Any third-party tools from your integration audit

Test each integration with a small action (send a test email, create a test calendar event) before going live.

Phase 5: Team Training and Go-Live (Week 3-4)#

Step 12: Train Your Team#

Focus training on the daily workflow, not every feature:

• How to find and view contacts, companies, and deals
• How to log activities and notes
• How to update deal stages
• How to use search and filters
• Where to find their pipeline view
• How to use any new features (like AI agents)

Create a one-page "cheat sheet" mapping old CRM actions to new CRM actions. People learn by analogy: "The old Reports tab is now called Dashboard. The old Activities panel is now in the timeline view."

Step 13: Parallel Run (Optional but Recommended)#

For risk-averse teams, run both CRMs in parallel for 1-2 weeks. Keep the old CRM in read-only mode (no new data entry) while everyone works in the new system. This provides a safety net if you discover missing data or broken workflows.

Step 14: Decommission the Old CRM#

After confirming the new CRM is working correctly:

1. Export a final backup from the old CRM (keep it for 6 months)
2. Cancel the old subscription (check contract terms for cancellation timing)
3. Revoke team access to the old system to prevent confusion
4. Celebrate not paying for two CRMs

Common Migration Pitfalls and How to Avoid Them#

Trying to migrate everything. You do not need 10 years of activity logs. Be selective. Migrate what you need for current operations and recent history.

Skipping the test import. Always test with a small batch first. Every time. The 30 minutes you spend on a test import can save you days of cleanup.

Forgetting about relationships. Records without relationships are just a spreadsheet. Plan your relationship mapping before you start importing.

Under-investing in training. The best CRM in the world fails if your team does not know how to use it. Invest more time in training than you think you need.

Migrating on a deadline. Do not schedule a migration the week before your busiest quarter. Give yourself buffer time for unexpected issues.

Frequently Asked Questions#

How long does a CRM migration typically take?#

For small-to-mid-sized businesses (under 100,000 records, 5-50 users), expect 2-4 weeks from planning to go-live. Larger or more complex migrations can take 4-8 weeks. The data import itself takes hours; the planning, cleaning, and training take weeks.

Will I lose my email history during migration?#

Your past emails are stored in your email provider (Gmail, Outlook), not your CRM. The CRM only stores a log of emails sent through or tracked by the CRM. Most platforms let you export this log, but re-importing email history into a new CRM can be complex. For most teams, starting fresh with email tracking in the new CRM while keeping access to email history in the email client is the practical approach.

Should I hire a consultant for the migration?#

For teams under 20 users with straightforward data (contacts, companies, deals), self-service migration is very doable. For teams with complex custom objects, heavy automation, or large data volumes, a consultant or the new vendor's migration support can save time and reduce risk. Expect to pay $1,000-$10,000 for assisted migration.

What if I discover missing data after migration?#

This is why you keep the old CRM accessible (read-only) for 30-60 days after migration. If you discover missing records or fields, you can re-export the specific data and import it into the new system. Having a final backup from the old CRM is your insurance policy.