Salesforce to HubSpot migration checklist for B2B sales teams

A Salesforce to HubSpot migration checklist is not a field-mapping spreadsheet. It is a plan for keeping sales moving while accounts, contacts, deals, activities, automations, and reports move from one CRM to another.

Salesforce and HubSpot can both run a serious B2B sales process, but they make different assumptions. Salesforce teams often rely on custom objects, strict validation rules, complex permission models, and years of admin work. HubSpot teams usually want cleaner pipelines, faster adoption, and less admin drag. The migration fails when the project treats those differences as export/import details.

Use this checklist before the first export. It is written for sales, RevOps, and operations teams that need the new HubSpot portal to be trusted on day one.

Salesforce to HubSpot migration checklist before export

Start by deciding what HubSpot must support on the first Monday after go-live. That answer should be shorter than "everything currently in Salesforce".

Write down the migration scope:

• Accounts and contacts that sales still owns
• Open opportunities, recently closed opportunities, renewals, and expansion deals
• Sales activities that reps need for context
• Products, plans, ARR, contract dates, and renewal fields
• Marketing consent, unsubscribe status, lead source, and lifecycle stage
• Dashboards used in weekly sales, finance, and management meetings
• Integrations that create or update CRM records

Archive the rest. A ten-year-old lead with no owner, no consent, and no commercial value does not become useful because it moved into HubSpot. It becomes a search result somebody distrusts.

For the broader migration structure, read our CRM migration checklist. This article focuses on the Salesforce-to-HubSpot decisions that usually cause friction.

Map Salesforce objects to HubSpot objects

Object mapping is where many migrations get too optimistic. Salesforce can contain custom objects for almost anything: subscriptions, locations, assets, partner accounts, onboarding projects, implementation milestones, support handoffs, or billing references. HubSpot has standard objects too, but the data model is not a copy of Salesforce.

Make a simple decision for every Salesforce object:

• Move it into a standard HubSpot object
• Move it into a HubSpot custom object
• Convert it into properties on company, contact, deal, or ticket records
• Keep it in an external system and connect it through integration
• Archive it outside the working CRM

Do not recreate Salesforce inside HubSpot just because the old setup allowed it. If a custom object only exists to support an old report nobody opens, it is migration debt, not business context.

A useful rule: if reps need to update the data weekly, model it inside HubSpot. If finance needs it for reference twice a year, keep it outside HubSpot and link to the source.

Clean Salesforce data before it reaches HubSpot

Bad Salesforce data looks worse after migration because HubSpot makes it easier for everyone to see and search it. Duplicate companies, abandoned leads, stale owners, and conflicting lifecycle stages should be fixed before import.

Clean in this order:

• Company names, domains, country fields, currencies, and tax or billing IDs
• Contact email validity, role, seniority, consent, and company association
• Duplicate accounts created by regional teams, subsidiaries, or old imports
• Opportunity stages that no longer match the current sales process
• Old required fields that sales filled with placeholders just to save a record
• Activities that matter for active deals versus noise that belongs in an archive

One concrete example: a Salesforce account may have three duplicate records for the same customer, one current owner, two former owners, six stale opportunities, and contacts spread across all three. If you import that as-is, HubSpot starts with broken ownership and a sales team that immediately blames the new system.

Rebuild the pipeline instead of copying stages

Salesforce opportunity stages often include years of compromises. Teams add stages for forecasting, manager review, handoff, partner influence, legal review, or because one region asked for a field in 2019. HubSpot gives you a chance to simplify.

For each pipeline stage, ask two questions:

• What buyer or seller event proves the deal belongs here?
• What action should HubSpot trigger when a deal enters this stage?

If a stage has no clear event and no action, remove it or turn it into a property. A pipeline with six honest stages is easier to run than a twelve-stage pipeline full of reporting habits.

Pay special attention to probability, forecast category, close date, renewal date, lost reason, and handoff status. Sales leaders care about those fields within hours of go-live.

Protect HubSpot automations and integrations

The migration does not stop at records. HubSpot usually connects to website forms, ad platforms, enrichment tools, meeting schedulers, email marketing, customer support, finance, BI, and Slack or Teams alerts.

Inventory every system that reads from or writes to Salesforce:

• Web forms and lead routing rules
• Marketing automation and consent sync
• Quote, contract, billing, subscription, and ERP tools
• Customer onboarding and support handoffs
• Forecasting spreadsheets and BI dashboards
• API jobs, middleware, Zapier, Make, and custom scripts

Then decide what happens during cutover. New leads may pause in a form queue. Salesforce may become read-only for a few hours. Billing IDs may stay locked until finance signs off. These small rules prevent two CRMs from becoming active at the same time.

If the CRM still needs old ERP or finance data after launch, our legacy system integration strategy explains when to use an integration bridge instead of a hard switch.

Test reports before the sales team logs in

Do not judge the migration by imported record counts. Judge it by business questions.

Before go-live, run tests like these:

• Do total open pipeline and weighted pipeline match the agreed Salesforce baseline?
• Can a rep find an account, understand the history, and update the next step?
• Does a new website lead reach the right owner with the right lifecycle stage?
• Do renewal deals show the correct owner, amount, date, and company link?
• Can finance reconcile closed-won deals against invoices or subscriptions?
• Do opt-outs and consent fields block marketing where required?
• Do managers see the same forecast logic they approved before cutover?

Run at least one dry import into a HubSpot sandbox or test portal. Then fix the mapping, clean more data, and run it again. If the second dry run still needs a long manual correction list, the migration is not ready.

A 30-day Salesforce to HubSpot migration plan

A controlled first migration can fit into 30 days when the scope is realistic. Larger teams, multi-region setups, and heavy Salesforce customization will need more time, but this structure still works.

Week 1: audit Salesforce objects, fields, integrations, automations, reports, permissions, and data quality. Decide what will not move.

Week 2: map objects and fields, clean accounts and contacts, define HubSpot pipelines, and prepare transformation scripts.

Week 3: run the first dry import, test sales scenarios, compare reports, fix mappings, and confirm integration behavior.

Week 4: run the final dry import, freeze Salesforce changes, brief users, switch production flows, and keep rollback instructions ready.

The risky part is not the import button. It is the week after go-live, when sales reps either trust HubSpot or start rebuilding their own spreadsheets.

Salesforce to HubSpot migration FAQ

How do you migrate from Salesforce to HubSpot?

Export and clean Salesforce data, map Salesforce objects to HubSpot objects, configure HubSpot pipelines and properties, run dry imports, test reports and integrations, freeze changes during cutover, then import production data with a rollback plan.

How long does a Salesforce to HubSpot migration take?

A small sales team with clean data can migrate in a few weeks. A team with custom Salesforce objects, many integrations, complex permissions, and years of duplicate data may need two or three months.

What Salesforce data should not move to HubSpot?

Do not move stale leads, duplicate accounts, unused fields, old activities nobody reads, invalid contacts, obsolete reports, and custom objects that no longer support a real sales or operational process.

Should HubSpot copy the Salesforce pipeline exactly?

Usually no. Copy the sales logic, not every old stage. Use the migration to remove unclear stages, tighten definitions, and keep only fields that sales or management use.

Do you need a partner for Salesforce to HubSpot migration?

You can handle a simple move internally if the data is clean and the CRM is lightly customized. Bring in help when Salesforce has custom objects, integrations, finance dependencies, or reports that leadership relies on weekly.

Need help with a Salesforce to HubSpot migration?

Syntanea helps teams audit Salesforce data, design HubSpot mappings, build migration scripts, test business scenarios, and protect integrations during cutover. If your CRM migration touches sales, finance, marketing, and custom systems at once, talk to us before the export becomes the project.