Can I keep my full history when migrating from Salesforce to HubSpot?

Contacts, companies, deals, notes, emails, calls, meetings and attachments can all be migrated with their original dates and owners. What cannot come across: your Salesforce reports and dashboards (rebuild them in HubSpot), workflows and Apex automation (redesign, do not copy), and campaign attribution history, which effectively restarts.

What happens to Salesforce Leads in HubSpot?

HubSpot has no separate Lead object; everyone is a contact with a lifecycle stage. This is the biggest conceptual change in the migration. Map Salesforce Leads to contacts with an appropriate lifecycle stage and lead status, and redesign the marketing-to-sales handoff around lifecycle stages rather than object conversion.

Should I use HubSpot's free Salesforce migration tool or a partner?

HubSpot's native tools and importers handle standard objects on simple orgs well. Use a partner when you have custom objects, heavy activity history you must keep, integrations that need rewiring, or dirty data that should be cleaned before it moves. The tool copies records; it does not redesign the process around them.

What does a Salesforce to HubSpot migration cost?

Simple migrations run roughly EUR 3,000 to 7,500 with a partner. Migrations involving custom objects, deep history, multiple source systems or integrations typically run EUR 10,000 to 40,000+. Data messiness drives cost more than record count.

Salesforce to HubSpot Migration: Timeline, Costs and What Breaks

Q: How long does a Salesforce to HubSpot migration take?

A straightforward migration (standard objects, one team, no integrations) takes 2 to 6 weeks including validation. Complex portals with custom objects, years of activity history and connected systems typically take 2 to 4 months. The single biggest time factor is how clean your Salesforce data is before you start.

First, should you switch at all?

Honest answer: not always. Salesforce is the right tool for deeply customised enterprise processes with a dedicated admin team. Teams switch to HubSpot when the Salesforce bill and admin overhead outgrow the value, when sales stops using it because every action takes five clicks, or when marketing, sales and service live in separate tools that do not talk. If your Salesforce works and people use it, keep it. If you are paying enterprise prices for a system your team avoids, read on.

What maps cleanly, and what does not

MOVES CLEANLYAccounts → Companies. Opportunities → Deals. Contacts → Contacts. Notes, emails, calls, meetings and attachments, with original dates and owners intact. Custom fields, mapped one by one.

NEEDS REDESIGNLeads: HubSpot has no separate Lead object; everyone is a contact with a lifecycle stage. This is the biggest conceptual shift and the place where lazy migrations go wrong. Workflows and Apex automation: redesign in HubSpot, never transliterate. Custom objects: supported, but remodel rather than copy.

DOES NOT MOVEReports and dashboards: rebuild them, usually better. Campaign attribution history: effectively restarts. AppExchange integrations: each connected system needs rewiring to HubSpot’s marketplace equivalent or API.

The process that protects your history

Audit the source first. Field usage, duplicate rates, ownership, which data is actually alive. Decisions about what NOT to migrate save more money than any tool.
Clean before you move. Dedupe and standardise in a staging export, never in the live org mid-migration. Moving dirt costs the same as moving gold.
Map objects and process together. The Lead-to-lifecycle redesign happens here, with sales in the room, not after go-live.
Dry run into a sandboxed portal. Validate counts, spot-check records end to end, let the team click around before the real cutover.
Cutover with a freeze window and validation. A short, announced freeze beats weeks of two-system limbo. Then reconcile record counts, owners and pipeline value against the source, number by number.

The rule that has protected every migration we have run: the story survives. A rep opening any customer in HubSpot on day one must see the whole relationship, every email, call and deal, with the right dates. If that bar is met, adoption follows. This is how Pro Football Academy came off a decade-old custom platform without losing a beat, and the same discipline scaled to a 10-million-contact, 17-brand consolidation.

Timelines and costs, honestly

Standard objects, one team, no integrations: 2 to 6 weeks including validation. Custom objects, deep history, connected billing or telephony: 2 to 4 months. Cost follows the same shape: roughly EUR 3,000 to 7,500 for simple moves, EUR 10,000 to 40,000+ for complex ones. Messiness drives price, not record count; full breakdown in our pricing guide.

The pre-migration checklist

Export field usage: which fields are actually filled, by whom, since when
Run a duplicate report on contacts and accounts; decide the survivor rules
List every AppExchange integration and its HubSpot replacement
Decide the Lead → lifecycle stage mapping with sales sign-off
Screenshot or export the reports leadership actually uses (you will rebuild these first)
Pick the freeze window and name one owner for go/no-go
Define the validation set: 20 real customers you will check end to end after cutover

HOW WE DO IT

Our Data & Migration service runs exactly this process at a fixed price, scoped after a free look inside your current setup. Clean, mapped, deduped, validated, and the story survives.

Scope my migration ↗

Frequently asked questions

How long does a Salesforce to HubSpot migration take?

2 to 6 weeks for straightforward moves, 2 to 4 months with custom objects, deep history and integrations. Data cleanliness is the biggest factor.

Can I keep my full history?

Records, notes, emails, calls, meetings and attachments migrate with original dates and owners. Reports, dashboards and automation are rebuilt; attribution history restarts.

What happens to Salesforce Leads?

HubSpot has no Lead object. Leads become contacts with lifecycle stages, and the handoff gets redesigned around stages instead of object conversion. This is the step to get right.

HubSpot’s free migration tool or a partner?

The native tooling handles simple orgs well. Bring a partner for custom objects, history you must keep, integrations, or data that should be cleaned before it moves.

What does it cost?

Roughly EUR 3,000 to 7,500 for simple migrations, EUR 10,000 to 40,000+ for complex ones. See the full pricing guide.

Still choosing who should run it? Start with our honest guide to HubSpot partners and the seven questions that expose a weak agency.

Salesforce to HubSpot: what moves, what breaks, what it takes.