Salesforce to HubSpot Migration: The 14-Day Playbook
Salesforce-to-HubSpot migrations have a reputation for being 6-month nightmares. They're not — when done right. Here's the 14-day playbook we've run 30+ times, including the 6 things you should redesign on the way over.
If you have heard a Salesforce-to-HubSpot migration story, it was a 6-month story. It involved a stalled project, a frustrated CMO, and an eventual decision to either give up or hire a second partner to clean up. That story is real. It is also not the only version.
The same migration, done right, is a 14-day project. Not 14 calendar days end-to-end across procurement and change management — but 14 active working days from kickoff to production go-live. We have run this version 30+ times. The difference between the 6-month nightmare and the 14-day project is not heroics. It is sequencing.
This is the playbook. If you are inheriting a Salesforce org you want to leave behind, follow it. If you are evaluating partners, use it as the test — ask any partner you are considering to walk you through what they do on Day 8, and listen for whether the answer is specific.
The framing question: how complex is your Salesforce org actually?
Before Day 1, run this filter. The 14-day version assumes a “normal” Salesforce org:
- Standard objects (Contact, Account, Opportunity, Case) with up to ~100 custom fields per object.
- Up to 5 custom objects, none deeper than two levels of relationship.
- Up to 50 active workflow rules / Flows.
- Pardot or Marketing Cloud Account Engagement (or no marketing platform on Salesforce side).
- Under 10 active integrations.
If your org has more than that — heavy CPQ, multi-org consolidation, Field Service Lightning, Industry Cloud customization — the 14-day timeline stretches to 4–6 weeks. That is still much faster than the typical 6-month story; it is just not the playbook below.
Day 1–3: data audit, deduplication, custom-object mapping
The first three days happen mostly outside HubSpot. The work is understanding what is actually in Salesforce.
Day 1: extract and inventory. Pull every object, every custom field, every workflow rule, every Flow. Document what each one does and whether anyone actually uses it. The deliverable is a single spreadsheet with every Salesforce object and a column called “Migrating? Y/N/Redesign.” Most orgs will have 30–60% of objects flagged “do not migrate” — fields nobody uses, workflows that have not fired in a year, custom objects that lost their owner three reorgs ago. This is the most valuable hour of the project.
Day 2: deduplication. Pull contact and account records out of Salesforce. Run dedup. The typical Salesforce org has 8–15% duplicate contacts, often higher in companies that have been on Salesforce for 5+ years. Cleaning this in HubSpot post-migration is twice as hard as cleaning it pre-migration. Do it on the way out.
Day 3: custom-object mapping. For each custom object that survived Day 1’s “Migrating? Y” filter, decide what it becomes in HubSpot. Three options:
- Custom object in HubSpot (Enterprise only). Direct port. Use this when the object has more than 5 properties and meaningful relationships.
- Properties on an existing object. A custom Salesforce object with 3 fields and no relationships often becomes 3 properties on the contact or company object in HubSpot. Simpler, easier to maintain.
- Out of scope. Some custom objects existed because Salesforce allowed them. They never had a real business reason. Mark them as out of scope and let them die.
The output of Day 1–3 is a migration map: the Salesforce schema on the left, the HubSpot schema on the right, and a column for “transformation logic” in the middle.
Day 4–7: HubSpot portal setup
With the migration map in hand, build the destination portal. This is configuration, not data movement.
Day 4: pipelines and lifecycle. Build deal pipelines and contact lifecycle stages from scratch in HubSpot. Do not copy the Salesforce stages. (More on this in the redesign section below.) Define the pipeline stages, the entry/exit criteria, and the deal probability per stage. This is a 4-hour exercise with the Head of Sales. Skipping it is the single most common reason migrations fail.
Day 5: properties. Create every contact, company, and deal property identified in the migration map. Use a consistent naming convention (we use lower_snake_case for internal property names and Title Case for labels). Every property gets a description field — what it is, who owns it, what it is used for. This documentation pays back at month 4 when someone asks “what does this field do?”
Day 6: workflows. Rebuild the Salesforce workflows and Flows that survived the Day 1 cull. Do not lift-and-shift — write each workflow’s intent in plain English, then build the HubSpot version of that intent. Most Salesforce workflows can be simplified by 30–50% in HubSpot because HubSpot ships with built-in lifecycle stage automation, lead scoring, and association management.
Day 7: integrations. Stand up the connections — product events, billing, support tickets, calendar, anything talking to the CRM. Use HubSpot’s native integrations where they exist and Data Hub flows where they do not. Keep the Salesforce → HubSpot live sync running during the migration; you will need it for the cutover gate on Day 13.
Day 8–10: the 10% test migration (the go/no-go gate)
This is the most important step in the playbook and the one most cheap migrations skip.
Day 8: pick the 10%. Take a representative slice of the data — typically 10% of contacts, the accounts attached to them, and any deals on those accounts. Choose for representativeness, not size. You want a slice that exercises every property, every association type, every custom object.
Day 9: run the test migration. Push the 10% into HubSpot using your migration tools (we use a combination of HubSpot’s import tooling, custom scripts, and middleware depending on the source). Watch for what breaks. Common failures: association integrity (deals not linking to the right contacts), property type mismatches (Salesforce text fields with values that do not fit HubSpot’s character limits), date/timezone handling, and lookup mappings that worked in Salesforce but do not have a home in HubSpot.
Day 10: validation and the go/no-go gate. Open a 50-point validation checklist and run through it. Sample tests:
- Does every imported deal have the correct contact and company associations?
- Do lifecycle stage values land where expected?
- Do calculated properties calculate correctly?
- Do workflows fire on imported records the way they should?
- Does reporting return sane numbers for the imported slice?
The go/no-go gate is binary. If validation passes — defined in advance as 95%+ on the checklist — you proceed to full migration. If it fails, you fix the migration logic and re-run the 10% before going further. Most migrations that fail in production failed at this gate and the team proceeded anyway.
Day 11–13: full migration and integration cutover
Day 11: full migration run. With the validated migration logic, run the full data set. Typical timing: 2–8 hours depending on volume. Run during off-hours or a planned freeze window.
Day 12: re-validation. Run the same 50-point checklist on the full data set. Spot-check a random 50 records across each object type. Confirm reports match expected counts. Reconcile against Salesforce — the contact count, account count, and open deal count should match Salesforce’s at the snapshot time, within an acceptable tolerance (typically <0.5%).
Day 13: integration cutover. Switch every integration from “writing to Salesforce” to “writing to HubSpot.” This includes product events, billing platforms, support systems, calendar integrations, marketing tools. Test each integration end-to-end. Keep Salesforce in read-only mode as a safety net — do not delete it for at least 30 days post-cutover.
Day 14: production go-live and first-week monitoring
Day 14 morning: go-live. Move sales and marketing teams to HubSpot as the system of record. Salesforce becomes read-only. Send a clear announcement with the new login, training links, and the named human to escalate to. Run a 60-minute live training session for sales reps and a separate one for marketing.
Day 14 afternoon and beyond: monitoring. The first 7 days post-go-live are the highest-risk period. We watch:
- Workflow firing rates. Workflows that fired 1,000x/day in Salesforce should fire approximately the same number in HubSpot. Big deviations mean misconfigured triggers.
- Sync errors. Any integration error queue. Address daily for the first week.
- Sales rep usage. Login rate, deal updates, activity logging. If reps are not using HubSpot in week 1, the training was not enough or the workflow design has friction.
- Deal pipeline integrity. Reconcile the pipeline against the last Salesforce snapshot daily. Any discrepancy needs same-day investigation.
The 30-day audit happens on Day 44. Most issues found at Day 44 are issues that started in week 1 and were not noticed.
The 6 redesigns (do not lift-and-shift)
Every Salesforce org has accumulated 5+ years of decisions made for reasons nobody remembers. A migration is the rare opportunity to fix them. Lift-and-shift is the wrong call on these six:
1. Pipeline stages. Salesforce orgs typically have 8–12 opportunity stages with overlapping definitions. Redesign to 5–7 stages with clean entry/exit criteria. Sales reps will thank you.
2. Lifecycle definitions. Most Salesforce-Pardot setups have the lifecycle smeared across both systems with conflicting rules. Pick one definition of MQL, SQL, Customer in HubSpot and own it.
3. Property naming. Salesforce custom fields accumulate naming chaos — Custom_Field_2__c, MainContactEmail__c, mainContactEmailV2__c. Rename on the way over. Once.
4. Workflow logic. Most Salesforce workflows are 20% complexity that adds value and 80% accumulated patches. Rebuild for the original intent.
5. Dashboard structure. Salesforce dashboards drift over years. Most teams have 50+ saved dashboards and use 5. Build 5 in HubSpot.
6. Integration topology. Five years of bolt-on integrations create a spaghetti that nobody can diagram. The migration is when you draw the topology you actually want and rebuild the connections to match it.
Common Salesforce-isms that do not translate
A few patterns that will trip you up if you are not expecting them:
- Formula fields. Salesforce’s calculated fields have no direct HubSpot equivalent at the field level. Use HubSpot’s calculation properties (Enterprise) or Data Hub flows to recompute on update.
- Validation rules. Salesforce’s field-level validation does not port. HubSpot has property requirements but not arbitrary validation logic. Bake validation into workflows or front-end forms.
- Complex Flows. Salesforce Flows with branching, looping, subflow calls are powerful and they do not map 1:1. Most can be rebuilt as HubSpot workflows; some need to move to a middleware layer (Data Hub, Zapier, custom code).
- Permission sets. Salesforce’s permission set model is more granular than HubSpot’s. Document the access matrix during Day 1 and rebuild it using HubSpot teams + permissions.
- Record types. Salesforce record types do not exist in HubSpot. Replace with property-based segmentation or, if the volume is high, separate pipelines.
The Salesforce → HubSpot lookup table (quick reference)
| Salesforce | HubSpot |
|---|---|
| Account | Company |
| Opportunity | Deal |
| Lead | Contact (with lifecycle stage = Lead) |
| Case | Ticket |
| Custom Object | Custom Object (Enterprise) or Properties |
| Workflow Rule | Workflow |
| Flow | Workflow (or middleware) |
| Process Builder | Workflow |
| Formula Field | Calculation Property (Enterprise) |
| Validation Rule | Workflow + Property Requirement |
| Permission Set | Team + Permission Role |
| Record Type | Pipeline (deals) or Property Segmentation |
| Pardot / MCAE | Marketing Hub |
| Salesforce Reports | HubSpot Custom Reports |
| Salesforce Dashboards | HubSpot Dashboards |
What to do next
If you are starting this migration, the next step is the Day 1 inventory. Do that before signing the partner contract. The inventory determines scope, and partners who quote without seeing it are quoting blind.
If you are weighing whether to migrate at all, the HubSpot vs Salesforce decision framework covers when each platform actually wins. And if you have already migrated and are debugging a portal that ships fine but feels broken, the HubSpot Audit Checklist is the same 50-point framework we use post-migration.
If you would like us to run this migration with you — including the Day 8 test gate that keeps it from sliding into a 6-month story — book a free 30-min consultation. We start with a free 30-minute scoping call where we will tell you honestly whether the 14-day version is realistic for your org or whether yours is one of the more complex cases that needs longer.