How to migrate from hubspot to salesforce without losing data (and stay sane)

How to migrate from hubspot to salesforce without losing data sounds simple on paper, but this is exactly where teams accidentally torch years of CRM history in a single weekend.

Done right? You keep every contact, deal, and activity intact and come out with a cleaner, more powerful Salesforce setup.

Done sloppy? You spend months untangling duplicates, broken reports, and missing revenue history.

Here’s the fast version.

• Move in stages: audit, clean HubSpot, design Salesforce, test, then go live.
• Protect data: full exports, backups, and sandbox test runs before touching production.
• Map smart: align objects, fields, and picklists deliberately—no 1:1 brainless copying.
• Control sync: freeze or tightly manage any active HubSpot–Salesforce connectors.
• Validate: spot-check records, reports, and automations before users fully switch.

What does “how to migrate from hubspot to salesforce without losing data” actually involve?

At a basic level, you’re doing four things:

1. Pulling data out of HubSpot (objects like contacts, companies, deals, activities).
2. Transforming it so it fits Salesforce’s data model and rules.
3. Loading it in the right order so relationships (like company → contacts → deals) stay intact.
4. Locking down quality with testing, validation, and user checks.

Think of it less like “moving boxes to a new house” and more like “remodeling while you move in.” You’re not just copying; you’re upgrading.

Key concepts before you touch a single record

Core objects: HubSpot vs Salesforce

You can’t learn how to migrate from hubspot to salesforce without losing data if you don’t understand how the two think about data.

• HubSpot:
  • Contacts
  • Companies
  • Deals
  • Tickets (if you use Service Hub)
  • Activities (emails, calls, meetings, tasks, notes)
  • Custom properties
• Salesforce:
  • Leads
  • Contacts
  • Accounts
  • Opportunities
  • Cases
  • Tasks, Events, Emails, Notes
  • Custom objects and fields

Biggest mental shift: HubSpot doesn’t really separate “Lead” and “Contact” like Salesforce does. In Salesforce, that Lead object matters for many sales processes.

Fast comparison: tools and approaches

Here’s a simple table to help you pick a migration approach based on your situation.

Approach	Best For	Pros	Cons	Typical Effort
Manual Export/Import (CSV)	Small databases (<50k records), simple setup	Full control, low cost, transparent	Time-consuming, higher human error risk	1–3 weeks with focused effort
Third-Party Migration Tool	Growing teams, multiple objects, need speed	Accelerated mapping, built-in connectors, logs	Licensing cost, still needs oversight	1–4 weeks including testing
Consultant / Partner-Led	Complex orgs, multiple integrations, compliance needs	Expertise, best practices, risk reduction	Higher cost, scheduling, vendor dependency	4–10 weeks depending on complexity

Step-by-step plan: how to migrate from hubspot to salesforce without losing data

This is the practical, “what do I actually do next Monday” breakdown.

1. Lock scope and freeze risky changes

Before anything:

1. Decide what’s in scope:
   • Which objects? (contacts, companies, deals, tickets, activities)
   • What date ranges? (all time vs last 3 years)
   • Which properties/fields are must-keep vs nice-to-have?
2. Set a code-freeze for structural changes in HubSpot:
   • No new pipelines, no big workflow overhauls, no field renames during migration.
3. Communicate timelines to sales, marketing, and support.

What usually happens is teams start migrating while marketing is still launching new workflows and sales is editing fields on the fly. That’s how you end up with misaligned snapshots and missing records.

2. Back up HubSpot like your job depends on it

Because it does.

1. Export each major object:
   • Contacts
   • Companies
   • Deals
   • Tickets (if applicable)
   • Custom objects (if your plan includes them)
2. Export activity data if needed:
   • Email engagements, call logs, meetings, tasks, notes.
3. Store backups securely:
   • A private cloud folder with versioned exports is usually sufficient.
4. Document export dates and filters used.

If you’re not sure what’s included or how exports behave, HubSpot’s own documentation on data export is worth a careful read from the source.

3. Clean HubSpot before moving anything

You don’t want to forklift junk into Salesforce. That’s like bringing every box from your old garage—including the broken lawnmower.

In my experience, this is where you win or lose the migration.

Focus on:

• Duplicates:
  • Merge obvious duplicates in HubSpot where possible.
  • Use email as a primary identifier; phone and company domain as secondary.
• Bad or incomplete data:
  • Remove bounced/unsubscribed contacts if they’ll never be used.
  • Archive or exclude obviously dead records from the initial migration.
• Field hygiene:
  • Standardize picklist values (states, countries, industries).
  • Normalize formats (phone number formats, date formats).

What I’d do if budget is tight: run quick Excel/Sheets cleanup on exported CSVs to fix obvious issues like ALL CAPS NAMES, blank critical fields, and invalid email addresses before import.

4. Design your Salesforce data model intentionally

This is the heart of how to migrate from hubspot to salesforce without losing data and actually use it.

Map objects and fields on paper (or in a shared doc) before you touch Salesforce:

• HubSpot Contacts → Salesforce Leads or Contacts (or both)
• HubSpot Companies → Salesforce Accounts
• HubSpot Deals → Salesforce Opportunities
• HubSpot Tickets → Salesforce Cases
• HubSpot custom properties → Salesforce custom fields

Key decisions:

• Lead vs Contact strategy:
  • Will all marketing leads come in as Salesforce Leads?
  • When do you convert Leads to Contacts/Accounts/Opportunities?
• Required fields:
  • Identify required fields in Salesforce that don’t exist in HubSpot.
  • Decide default values or create mapping rules so imports don’t fail.
• Picklists:
  • Align HubSpot options with Salesforce picklists to avoid import errors.
  • For any mismatch, decide whether to expand Salesforce picklists or remap values.

Salesforce’s own Trailhead modules on data modeling and data import best practices are solid, vendor-neutral grounding straight from the platform’s owner.

5. Build your field mapping document

Don’t skip this. It’s your blueprint.

Include:

• HubSpot object → Salesforce object
• HubSpot property name → Salesforce field name
• Data type (text, number, picklist, date, boolean)
• Transformation rules (e.g., “if Lifecycle Stage = Customer, set Lead Status = Closed – Converted”)
• Required? (Y/N)
• Notes on edge cases

This reference saves hours when troubleshooting later.

6. Set up Salesforce for migration

Now prep Salesforce for the incoming data.

1. Create any custom fields you need.
2. Adjust page layouts so users can actually see critical migrated fields.
3. Set permissions and field-level security so imports don’t get blocked.
4. Decide on your tools:
   • Salesforce Data Import Wizard (simpler, limited objects).
   • Salesforce Data Loader or Data Import tools for bulk, multi-object loads.
   • Third-party data migration platforms if your volume is large.

Salesforce’s help documentation and admin guides explain each tool’s limitations and use cases directly from the official source—worth reviewing before you pick your weapon.

7. Run a sandbox test migration

Never go straight to production if you can avoid it.

1. Spin up a Salesforce sandbox (if your edition allows).
2. Take a sample data set:
   • 500–2,000 records per object is usually enough to surface issues.
3. Import objects in this order:
   1. Accounts (Companies)
   2. Contacts (and/or Leads)
   3. Opportunities (Deals)
   4. Cases (Tickets)
   5. Activities (Tasks, Events, emails, notes)

This order matters because of lookups and relationships.

Then test like a cynic:

• Are Account–Contact relationships preserved?
• Do Opportunities attach to the right Accounts/Contacts?
• Do required fields have valid values?
• Are picklists mapping correctly?
• Any UTF-8/encoding issues with notes or emails?

Fix issues in your mapping and import templates until your sandbox looks clean.

8. Manage integration and sync timing

Here’s the thing: many teams already have some flavor of HubSpot ↔ Salesforce integration or plan to turn it on.

To avoid overwriting good data or duplicating records:

• If you already use an integration:
  • Pause or limit sync directions during the bulk migration.
  • Decide one system of record for each field during the transition.
• If you’re enabling Salesforce and turning HubSpot into “marketing only”:
  • Clarify which fields will still sync post-migration.
  • Strip down HubSpot to necessary marketing data only.

You want a clean, controlled cutover—not a messy tug-of-war where systems overwrite each other.

9. Production migration: the controlled go-live

Once your test run looks solid, you’re ready for the real thing.

High-level sequence:

1. Lock changes in HubSpot:
   • Announce a “freeze window” where users avoid major changes.
   • If possible, keep new record creation to a minimum during the window.
2. Run fresh exports from HubSpot matching your tested structure.
3. Import to Salesforce in the same order as your sandbox test:
   • Accounts
   • Contacts / Leads
   • Opportunities
   • Cases
   • Activities
4. Track import logs:
   • Log success counts vs error counts for each file.
   • Address errors systematically (often picklists, required fields, or bad IDs).

Plan this for low-activity hours in your primary time zones so you can fix surprises without blocking the entire sales team.

10. Post-migration validation and cleanup

This is where you confirm you actually pulled off how to migrate from hubspot to salesforce without losing data.

Validate at three levels:

• Record-level checks:
  • Pick random sets of contacts, accounts, and opportunities.
  • Compare HubSpot exports to Salesforce records field by field.
• Aggregate checks:
  • Count total records by object (e.g., number of contacts) in HubSpot vs Salesforce (allowing for intentional exclusions).
  • Compare pipeline totals by stage and amount between systems.
• Process checks:
  • Run a few key workflows in Salesforce (e.g., creating a new Opportunity, converting a Lead).
  • Ensure automation (assignment rules, validation rules) still behaves with the migrated data.

Then:

• Train users:
  • Short, focused sessions for sales, marketing, and support.
  • Show “before/after” views for records to build confidence.
• Collect feedback:
  • Create a simple channel for users to report data issues.
  • Fix systematic issues quickly to avoid trust erosion.

Common mistakes in HubSpot → Salesforce migration (and how to fix them)

Mistake 1: Ignoring lifecycle and stage mapping

Symptoms:

• Leads land in Salesforce with random statuses.
• Pipeline stages don’t match reality.
• Forecasting becomes useless overnight.

Fix:

• Explicitly map:
  • HubSpot Lifecycle Stage → Salesforce Lead Status / Contact fields.
  • HubSpot Deal Stages → Salesforce Opportunity Stages.
• If HubSpot stages are messy, normalize them before mapping to Salesforce.

Mistake 2: Treating HubSpot Contacts as Salesforce Contacts only

HubSpot doesn’t enforce the Lead/Contact distinction the way Salesforce does.

If you import everything as Salesforce Contacts:

• Your lead management process breaks.
• MQL → SQL tracking gets fuzzy.
• Reporting on lead conversion becomes painful.

Fix:

• Build clear rules:
  • Example: “If HubSpot Lifecycle Stage = Subscriber / Lead / MQL → Salesforce Lead. If SQL / Opportunity / Customer → Salesforce Contact.”
• Apply these rules during mapping and transformation.

Mistake 3: Over-migrating junk data

Dragging every field, every list, every historical activity into Salesforce is tempting. It’s also how you end up with a slow, cluttered CRM that nobody trusts.

Fix:

• Define retention rules:
  • Example: migrate only last 3 years of activities.
  • Keep legacy data archived in spreadsheets or a data warehouse.
• Prioritize:
  • Fields actively used in workflows, reports, and day-to-day operations.
  • Drop “nice to have but never actually used” fields.

Mistake 4: Not planning for ongoing sync or coexistence

Sometimes HubSpot doesn’t fully go away. It stays as a marketing tool.

Without clear boundaries:

• Fields get overwritten unexpectedly.
• Users don’t know which system to trust.
• Marketing and sales argue about “where that lead actually is.”

Fix:

• Post-migration “data contract”:
  • Which data lives primarily in Salesforce.
  • Which marketing fields can sync back and forth.
  • Ownership rules—marketing vs sales.

Mistake 5: Skipping structured testing

What usually happens is someone uploads a few CSVs into production “just to test” and ends up with thousands of broken records and duplicates.

Fix:

• Always test in sandbox (or at minimum, with a small, controlled subset).
• Use a shared checklist:
  • Objects imported successfully.
  • Critical relationships intact.
  • Key reports match expectations.

Beginner-friendly action plan: how to migrate from hubspot to salesforce without losing data

If you’re not a CRM architect, here’s the simplified track.

1. Inventory your data
   • List objects: contacts, companies, deals, tickets, activities.
   • Note any critical custom fields (e.g., renewal date, product line, region).
2. Export and back up
   • Export each object from HubSpot to separate CSV files.
   • Store them securely and label clearly with dates.
3. Clean the obvious mess
   • Remove test records.
   • Merge obvious duplicates.
   • Fix clearly broken emails and phone numbers where possible.
4. Map objects and fields
   • Decide:
     • Which HubSpot records should become Salesforce Leads vs Contacts.
   • Create a simple mapping spreadsheet: HubSpot field → Salesforce field.
5. Set up Salesforce fields
   • Create missing custom fields.
   • Align picklist values to match what you’re importing.
6. Test with a small batch
   • Import a few hundred records into a sandbox or a test-only area.
   • Check relationships and field values.
7. Run full migration
   • Import in the logical order (Accounts → Contacts/Leads → Opportunities → Cases → Activities).
   • Monitor error logs and fix issues as they appear.
8. Verify and train
   • Compare record counts and spot-check data.
   • Do quick training sessions so teams know how to find what they need.

How to migrate from hubspot to salesforce without losing data: advanced tips for intermediate users

If you’re a bit more technical or have admin experience, you can level this up.

Use stable IDs and external IDs

• Add an “External ID” field in Salesforce for HubSpot IDs (e.g., HubSpot Contact ID).
• This makes:
  • Upserts easier.
  • Future syncs safer.
  • Data reconciliation straightforward.

Script transformations where possible

Instead of manually editing large CSVs:

• Use tools like:
  • Python scripts
  • Google Sheets formulas
  • Data prep tools
• Automate:
  • Lifecycle → Lead/Contact mapping.
  • Picklist value translations.
  • Concatenation (e.g., combine multiple fields into a single description).

Keep one source of truth for every phase

During migration:

• Phase 1 (pre-cutover): HubSpot is source of truth.
• Phase 2 (migration window): your exported snapshot is source of truth.
• Phase 3 (post-cutover): Salesforce is source of truth.

Make that explicit in documentation and internal communication.

Key Takeaways

• how to migrate from hubspot to salesforce without losing data is less about tools and more about disciplined planning, mapping, and testing.
• Backups are non-negotiable—export everything and store safely before touching Salesforce.
• Clean data before migrating, or you’ll import your problems and multiply them.
• Map HubSpot lifecycle stages and deal stages thoughtfully into Salesforce Lead/Contact/Opportunity structures.
• Always test in a sandbox or with a small, controlled dataset before a full production import.
• Import in the right order to preserve relationships: Accounts → Contacts/Leads → Opportunities → Cases → Activities.
• Define a clear post-migration “data contract” if HubSpot will continue as a marketing system.
• Invest an extra week in planning and validation; it often saves months of messy cleanup later.

FAQs