---
title: "Salesforce to HubSpot Migration Checklist: What Moves, What Doesn’t, and What to Rebuild"
description: What moves, what gets rebuilt, and what to plan separately when migrating Salesforce to HubSpot. Download the checklist and book a migration assessment.
---

[Skip to content](https://www.suprduo.com/blog/salesforce-to-hubspot-migration-checklist#main-content)

[![suprduo\_logo](https://www.suprduo.com/hs-fs/hubfs/Untitled-11-01.png?width=250&height=100&name=Untitled-11-01.png)](https://www.suprduo.com/)

[HubSpot](https://www.suprduo.com/hubspot)[GTM](https://www.suprduo.com/gtm)[Marketing](https://www.suprduo.com/marketing)[RevOps](https://www.suprduo.com/revops)[Web Dev](https://www.suprduo.com/web)[Contact](https://www.suprduo.com/contact)[Blog](https://www.suprduo.com/blog)

[Book A Call↗](https://meetings-na2.hubspot.com/supr2/initial-discovery)

Menu +

[← Back to the journal](https://www.suprduo.com/blog)

# Salesforce to HubSpot Migration Checklist: What Moves, What Doesn’t, and What to Rebuild

Supr Duo 2 November 2026

Most Salesforce to HubSpot migrations don’t go wrong because the export failed. They go wrong because nobody decided, before the move, what would be rebuilt, what would be retired, and what would be left behind. The records usually come across fine. The automation, reporting and habits wrapped around them often don’t.

This Salesforce to HubSpot migration checklist is built around that problem. It starts with a table of what moves, what gets rebuilt and what needs its own plan. Then it walks through six phases in order: scope, data cleanup, mapping, build, test and go-live, plus the first 30 days after launch.

Use it as a planning document with your sales, marketing and service leads. If you’d rather have a certified team run the project, see our [HubSpot CRM migration](https://www.suprduo.com/hubspot) service.

### What moves, what gets rebuilt, and what needs its own plan

Start here, because this table decides your scope.

The pattern is simple: data moves, logic gets rebuilt. Budget your time accordingly.

 

| Salesforce | HubSpot equivalent | What to plan |
| --- | --- | --- |
| Accounts | Companies | Moves with the data import. Keep the Salesforce ID as a property so records stay traceable. |
| Contacts and Leads | Contacts | Moves. Decide how lead status and converted leads map to lifecycle stage and lead status. |
| Opportunities | Deals | Moves, but build pipelines and deal stages first. |
| Cases | Tickets | Moves, but ticket pipelines and statuses must exist before import. |
| Custom objects | Custom objects | Create the objects, properties and associations first, then import. |
| Users, roles, profiles | Users, teams, permissions | Rebuild by hand and map record owners during import. |
| Flows, Process Builder, Apex | Workflows | Does not migrate. Rebuild and simplify. |
| Reports and dashboards | Reports and dashboards | Does not migrate. Rebuild around the questions leadership actually asks. |
| Email templates and sequences | Templates and sequences | Rebuild. |
| List views and queues | Lists and views | Rebuild as active or static lists. |
| Tasks, calls, meetings, emails | Activities | Needs its own plan. Historical activity depends on volume and how much history your reps truly need. |
| Files and attachments | Files and attachments | Follows a separate migration path. Plan it early. |
| Integrations (billing, support, enrichment) | Native or custom integrations | Reconnect and retest. |

### Phase 1: Scope and prepare

- Name a project owner on the RevOps or sales ops side and an executive sponsor who can settle disputes.
- Set a go-live target. If you can’t name one, stop here and get one.
- Decide which objects, record types and how much history are in scope.
- Inventory what lives in Salesforce today: objects, fields, record types, validation rules, flows, reports, dashboards, integrations and users.
- Decide what to retire. If nobody has used a field, report or automation in the last year, question whether it deserves a place in the new system.
- Choose which HubSpot hubs and tiers you need. If you’re unsure, a short [RevOps audit](https://www.suprduo.com/revops) will tell you before you buy.
- Agree a freeze window for Salesforce data entry on the records you’re moving.
- Take a full backup export of Salesforce before you touch anything.

### Phase 2: Audit and clean your data

A migration moves your problems along with your data. Fix them while the data is still in the old system.

- Deduplicate contacts, companies and deals.
- Standardize picklist values, country and state fields, phone formats and company names.
- Archive or remove stale records nobody will miss.
- Check that contacts are linked to the right accounts, because those links drive your HubSpot associations.
- Capture baselines you’ll validate against later: record counts per object, the contact-to-company association rate and open pipeline value by stage.

### Phase 3: Map objects, fields and terminology

- Build a mapping spreadsheet covering every field you plan to bring across: Salesforce field, HubSpot property, field type, owner and notes.
- Create HubSpot properties before you import, and match field types (dropdowns, dates, numbers, text).
- Decide how Salesforce leads become HubSpot contacts, and what lifecycle stage and lead status each group gets.
- Map record owners to HubSpot users, or decide how unowned records will be reassigned.
- Get the mapping signed off by sales, marketing and service leaders, not only by whoever runs the import.

### Phase 4: Build the HubSpot foundation

Build the structure before the data arrives, so records land where they belong.

- Create deal pipelines and stages, and ticket pipelines and statuses.
- Define lifecycle stages and lead status in writing, so sales and marketing use them the same way.
- Create custom objects and their associations.
- Set up users, teams and permissions.
- Rebuild workflows, and keep them paused until validation is complete.
- Rebuild email templates, sequences and lists.
- Rebuild reports and dashboards from the decisions leadership makes, rather than copying every old report one for one.
- Reconnect integrations and test each one.

### Phase 5: Run a test migration

- Migrate a small, representative sample first. Include messy records, not just clean ones.
- Check that associations, owners, dates, currencies and picklist values came across correctly.
- Fix mapping problems, then run the full migration.
- Choose your method deliberately: HubSpot’s import tools for straightforward data, third-party migration tools for larger volumes, or custom API work for complex structures.
- Be clear about what the HubSpot and Salesforce connector is for. It’s designed for ongoing sync, not for moving your history. If you keep it running during a transition, decide which system is the source of truth for each field so records don’t overwrite each other.

### Phase 6: Validate and go live

- Compare record counts and baseline metrics against the numbers you captured in Phase 2.
- Have a few reps spot-check their own accounts and deals. They’ll catch what a spreadsheet won’t.
- Test workflows on a small segment before turning them on broadly.
- Train the team before launch, not after. A system nobody uses isn’t a system.
- Communicate the cutover date, and set Salesforce to read-only once you’re live.
- Run a go or no-go review with the project owner and sponsor.

### The first 30 days after go-live

Go-live is the middle of the project, not the end.

- Daily: confirm new leads are being created, routed and followed up, and check workflows for errors.
- Weekly: compare pipeline and conversion reports against your historical baseline, and collect rep feedback on missing fields or awkward views.
- Fix property gaps and report requests as they surface, and document each change.
- Don’t cancel or fully retire Salesforce until you’ve signed off that the data and reporting match.

### Common Salesforce to HubSpot migration mistakes

1. **Treating it as a data project only.** The logic, automation and reporting are where most of the work sits.
2. **Copying everything one for one.** Migration is a chance to retire unused fields and over-built automation.
3. **Importing before building pipelines.** Records then land in the wrong stages and need fixing.
4. **Skipping baselines.** Without before numbers, you can’t prove the after numbers are right.
5. **Activating workflows too early.** Unvalidated automation can send emails or create tasks against bad data.
6. **Leaving files and attachments until the end.** They follow a different path and are easy to forget.
7. **Under-investing in training.** Adoption decides whether the migration was worth it.

### How long does it take, and what does it cost?

It depends on data volume, the number of custom objects, how many automations and integrations you’re rebuilding, and how much internal HubSpot knowledge you have. 

### When to bring in a partner

A smaller migration with standard objects can sometimes be handled in-house. Bring in help when you have custom objects, heavy automation, several integrations, or no one on the team who has run a HubSpot implementation before.

SuprDuo is a HubSpot Platinum Partner, certified across HubSpot and Salesforce, and we approach migrations as RevOps projects rather than data transfers. We start by auditing how leads, deals and customers move through your business, design the target structure, then build, migrate, validate and train your team. 

### Frequently asked questions

**Can I migrate Salesforce automation to HubSpot automatically?** No. Flows, Process Builder automations and Apex logic need to be rebuilt as HubSpot workflows. This is a good moment to simplify them.

**Will I lose my Salesforce history?** Core records and their associations can move. Historical activity and files need a dedicated plan, and the right scope depends on how much history your team actually uses.

**Should I keep the HubSpot and Salesforce integration running during migration?** Sometimes, if sales and marketing will be split across systems for a while. Define the source of truth for each field and set an end date, or you’ll end up with duplicates and conflicting data.

**How do I migrate custom objects?** Create the objects, properties and associations in HubSpot first, then import the records and link them.

**Can I run both CRMs in parallel?** You can, but keep the overlap short and name one system as the source of truth at every stage.

**Ready to plan your move?** [Book a migration assessment](https://meetings-na2.hubspot.com/supr2/initial-discovery) and we’ll map your Salesforce setup to HubSpot, including what to rebuild and what to retire.

[what doesn’t migrate from Salesforce to HubSpot](https://www.suprduo.com/blog/tag/what-doesnt-migrate-from-salesforce-to-hubspot)[Salesforce to HubSpot data mapping](https://www.suprduo.com/blog/tag/salesforce-to-hubspot-data-mapping)[CRM migration to HubSpot](https://www.suprduo.com/blog/tag/crm-migration-to-hubspot)

BEHIND THE WORDS

## Supr Duo

Ideas and observations

A curious perspective on making things clearer, brighter and a little more human.

[Meet the team↗](https://www.suprduo.com/team)

## Keep the conversation going.

[![Suprduo Logo Grey Yellow-1](https://www.suprduo.com/hs-fs/hubfs/__hs-marketplace__/Suprduo%20Logo%20Grey%20Yellow-1.png?width=1043&height=533&name=Suprduo%20Logo%20Grey%20Yellow-1.png)](https://www.suprduo.com/)

[HubSpot](https://www.suprduo.com/hubspot)[GTM](https://www.suprduo.com/gtm)[Marketing](https://www.suprduo.com/marketing)[RevOps](https://www.suprduo.com/revops)[Web Dev](https://www.suprduo.com/web)[Contact](https://www.suprduo.com/contact)

© 2026 SuprDuo[Back to the good stuff↗](https://www.suprduo.com/blog/salesforce-to-hubspot-migration-checklist#main-content)

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Supr Duo",
    "url" : "https://www.suprduo.com/blog/author/dd"
  },
  "dateModified" : "2026-11-03T14:35:00.311Z",
  "datePublished" : "2026-11-02T08:44:56.000Z",
  "headline" : "Salesforce to HubSpot Migration Checklist: What Moves, What Doesn’t, and What to Rebuild",
  "mainEntityOfPage" : {
    "@id" : "https://www.suprduo.com/blog/salesforce-to-hubspot-migration-checklist",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://www.suprduo.com/hubfs/Suprduo%20Grey%20Yellow-01-01-1.png"
    },
    "name" : "SuprDuo"
  }
}
```