You don't switch CRMs because you feel like it. You do it because HubSpot can't hold the architecture you've just acquired -- or the architecture you're about to build.
If you're running a roll-up with three, five, or ten companies under one platform, you're probably staring at a messy patchwork: one entity on HubSpot, two on Pipedrive, another on a decade-old Salesforce instance nobody quite remembers configuring. It's death by a thousand integrations. You can't see pipeline across the group. Your CFO wants a consolidated revenue forecast. Your PE sponsor wants clean numbers. And your internal IT team is already at capacity keeping the lights on.
This article covers the practical, operational realities of HubSpot to Salesforce data migration in a post-acquisition context. We'll walk through the fundamental architecture differences, deal pipeline mapping, what marketing automation should (and shouldn't) move, custom property migration, rebuilding workflows, and when full migration makes more sense than integration. We won't tell you that it's simple, because it's not. But we will tell you where the value leaks, what breaks, and how to plan around it.
Why Roll-Ups Outgrow HubSpot and Move to Salesforce
When CRM Consolidation Becomes Unavoidable
The trigger is rarely "HubSpot is bad." The trigger is "we just closed deal four, and we need group-level pipeline reporting by Friday." Or: "We're trying to track cross-sell opportunities across three entities, and nobody can agree on which CRM holds the truth."
HubSpot works beautifully when you're one company, one sales team, one process. It starts to fray when you're operating multiple business units with different sales motions, approval hierarchies, or reporting lines. Salesforce's architecture-accounts, contacts, leads, opportunities, and unlimited custom objects-offers the layering and segmentation you need to model a portfolio structure. You can tag deals by entity, roll up forecasts by business unit, and still drill down into individual rep performance.
The other inflection point: when your acquired companies already live in Salesforce. If three of your five portfolio companies are on Salesforce, and two are on HubSpot, you've got a choice to make. Migrating two companies is almost always cheaper and less painful than migrating three.
The Real Cost of Operating Multiple CRMs Across Portfolio Companies
Operating two or three different CRMs across your platform isn't just inconvenient -- it's expensive, invisible, and compounding.
You're paying for duplicate licences. HubSpot Professional at £40/user/month, Salesforce at £60/user/month, maybe a Pipedrive instance still running at one entity. Multiply by 40 sales and service staff, and you're spending £5,000–£7,000 a month on CRM licences alone before you count integrations, training, or admin time.
Then there's the operational drag. Your Head of Sales can't build a consolidated pipeline report without exporting three CSVs and duct-taping them together in Excel. Your CFO is chasing revenue data from multiple sources. Cross-sell gets talked about in board meetings but never happens because nobody can see what the other business units are selling.
And the integration tax is real. Every time you add a new tool-your billing system, your customer success platform, your marketing automation engine-you're building connectors to two or three CRMs. Each connector is another failure point, another thing to troubleshoot when data doesn't sync.
CRM consolidation becomes unavoidable when the cost of not consolidating-in licence spend, manual work, lost visibility, and missed cross-sell-outweighs the cost and risk of migration.
What Makes HubSpot to Salesforce Data Migration Different
Data Model Incompatibilities You'll Actually Encounter
HubSpot and Salesforce don't speak the same language. That's the first thing to understand. They model customer data differently, and it matters.
HubSpot uses a flat, contact-centric model: Contacts, Companies, Deals, and Tickets. Salesforce uses a hierarchical, account-centric model: Leads, Contacts, Accounts, Opportunities, and Cases. The two systems don't map 1:1.
Here's where it gets messy:
- HubSpot Contacts → Salesforce Leads or Contacts. In HubSpot, a contact is a contact. In Salesforce, you've got to decide: is this person a Lead (not yet qualified, no account) or a Contact (qualified, linked to an account)? If you migrate everyone as Contacts, you lose lead qualification workflows. If you migrate everyone as Leads, your existing customers show up as unqualified prospects. You'll need logic: contacts associated with closed deals become Contacts: everyone else becomes Leads.
- HubSpot Companies → Salesforce Accounts. This one's straightforward on paper, but the devil's in the relationships. HubSpot allows one contact to be associated with multiple companies. Salesforce expects a primary account relationship. If your data model relies on many-to-many company associations, you'll need to flatten or choose a primary.
- HubSpot Deals → Salesforce Opportunities. Deal stages, close dates, and amounts migrate cleanly. Deal pipelines? Less so. If you've got multiple pipelines in HubSpot (Sales, Partnerships, Renewals), you'll need to map those to Salesforce record types or separate objects. And if your deal stages don't align with Salesforce's default opportunity stages, you'll be rebuilding picklists and automation.
- HubSpot Tickets → Salesforce Cases. Fine for support workflows, but if you've been using Tickets for internal project tracking or onboarding workflows, Salesforce Cases won't replicate that. You may need a custom object instead.
Where Custom Fields and Workflows Break Down
Every CRM implementation accumulates custom fields. Some are critical. Most are digital archaeology: "Why do we have a field called 'TempFlag_Q32019'?" Nobody remembers. Nobody's game to delete it.
Custom properties in HubSpot don't automatically migrate to Salesforce. You'll export a field list from HubSpot, audit it, decide what's still needed, and manually recreate fields in Salesforce with matching data types. Text fields are easy. Dropdowns (picklists) are harder-especially if HubSpot allowed free text entry and Salesforce enforces strict picklist values. If someone typed "UK" in one record, "United Kingdom" in another, and "U.K." in a third, you've got cleanup work before migration.
Workflows and automation are where things properly break. HubSpot workflows are visual, trigger-based, and tightly integrated with email sequences. Salesforce automation-Process Builder, Flow, Apex triggers-is more powerful but requires different thinking. You're not "migrating" workflows: you're rebuilding them. That means:
- Auditing every active workflow in HubSpot.
- Deciding which ones still matter.
- Rebuilding the logic in Salesforce using Flow or Process Builder.
- Testing to make sure triggers fire correctly and notifications reach the right people.
It's not a technical problem. It's a translation problem. And it takes time.
The Five-Phase Migration Execution Framework
Phase 1: Data Audit and Mapping
Timeline: 2–3 weeks. Deliverable: Migration plan, field mapping document, data quality report.
You start by understanding what you've actually got. Export everything from HubSpot: contacts, companies, deals, tickets, custom properties, active workflows, email templates, forms, and reports. Then you ask the hard questions:
- Which records are active? Which are duplicates, test data, or junk?
- Which custom fields are still in use? Which can be archived?
- How many deals are in each pipeline stage? How do those stages map to Salesforce?
- Who owns which records? Are ownership rules consistent, or will you need to reassign?
- What workflows and automations are business-critical?
This is also when you map HubSpot objects and fields to Salesforce equivalents. Build a spreadsheet: HubSpot field name, data type, Salesforce field name, data type, transformation rules. If a HubSpot checkbox becomes a Salesforce picklist (Yes/No), document it. If a text field needs to be split into two fields, document it.
The audit phase is boring. It's also the phase that prevents disaster. Skip it, and you'll discover data issues during migration-when your sales team is offline and your CFO is asking why pipeline numbers don't match.
Phase 2: Salesforce Environment Configuration
Timeline: 2–4 weeks. Deliverable: Configured Salesforce sandbox, rebuilt workflows, user roles and permissions.
Now you build the Salesforce environment that will receive the data. This isn't a default Salesforce install: it's a configured system that mirrors your business processes and accommodates your migrated data.
You'll:
- Create custom fields to match your HubSpot properties.
- Set up record types if you're running multiple pipelines or business units.
- Build or configure page layouts so your sales team sees the fields they need (and not the 47 fields they don't).
- Configure validation rules to prevent bad data from sneaking in post-migration.
- Rebuild critical workflows using Salesforce Flow or Process Builder.
- Set up user roles, profiles, and permission sets so the right people see the right data.
- Configure reports and dashboards that replace the HubSpot reports your team relies on.
Do all of this in a Salesforce sandbox-a parallel test environment-not in production. You'll use the sandbox for testing in Phase 3.
Phase 3: Migration Testing and Validation
Timeline: 1–2 weeks. Deliverable: Successful test migration, validated data, signed-off UAT.
This is where you find out if your mapping and configuration actually work. You take a subset of data-maybe 500 contacts, 50 companies, 100 deals-and migrate it into the Salesforce sandbox. Then you check:
- Did all records migrate? Any failures or errors?
- Do field values match? Is "HubSpot Deal Stage: Proposal Sent" correctly mapping to "Salesforce Opportunity Stage: Proposal/Price Quote"?
- Are relationships intact? Is each contact linked to the correct account? Is each opportunity linked to the correct contact and account?
- Do workflows fire correctly? If a deal closes, does the right person get notified?
- Can users log in, navigate, and perform their daily tasks?
You'll run User Acceptance Testing (UAT): get a few sales reps, account managers, and your operations lead to click around, test workflows, and flag anything that feels wrong. Fix issues. Re-test. Repeat until you're confident.
Testing is not optional. A test migration in a sandbox costs you a week. A botched production migration costs you a month and your sales team's trust.
Phase 4: Cutover and Hypercare
Timeline: 1 week cutover, 2 weeks hypercare. Deliverable: Live Salesforce environment, migrated data, support coverage.
Cutover is go-live day. You'll:
- Freeze HubSpot. Set it to read-only or stop users from adding/editing records. Communicate clearly: "HubSpot is locked as of 5 PM Friday. Any new leads or updates need to be captured in a holding spreadsheet until Monday."
- Run the production migration. Use your tested scripts and tools (Data Loader, third-party migration tools, or custom scripts) to move data from HubSpot into Salesforce production.
- Validate. Check record counts, spot-check key accounts and deals, confirm workflows are firing.
- Open Salesforce. Notify users, provide login credentials, and go live.
The first two weeks post-cutover are hypercare. You're on call. Sales reps will have questions. Things will break in ways you didn't anticipate. You'll find edge cases: "Why can't I see deals from the old Midlands office?" or "This automated email isn't sending."
Hypercare means fast response times, daily check-ins, and a clear escalation path. It's the difference between a rocky migration that stabilises and a migration that becomes a morale disaster.
Phase 5: User Adoption and Optimisation
Timeline: 4–8 weeks post-go-live. Deliverable: Training materials, documentation, adoption metrics, iterative improvements.
The system's live. Now you've got to make sure people actually use it.
Role-specific training is critical. Sales reps don't need a full Salesforce admin course: they need 30 minutes on "how to log a call, update an opportunity, and run your pipeline report." Account managers need to understand how to manage cases and track customer health. Your ops team needs to know how to build reports and troubleshoot common issues.
Adoption doesn't happen by accident. Track it: Are users logging in? Are they updating opportunities? Are deal stages progressing, or is everything stuck in "Prospecting" because reps don't understand the new stages?
Build feedback loops. Weekly check-ins for the first month, then biweekly. Ask: "What's frustrating? What's missing? What's slower than it used to be?" Then optimise: tweak page layouts, add fields, simplify workflows, build missing reports.
You'll also decommission HubSpot-cancel licences, archive data, and make sure nobody's still secretly using it because it's "easier." Adoption fails when you leave the old system accessible as a fallback.
The Three Decisions That Determine Timeline and Cost
Clean Migration vs. Historical Data Strategy
Here's the trade-off: migrate everything, or migrate what matters?
Option 1: Full historical migration. Every contact, company, deal, note, email, and activity from HubSpot moves to Salesforce. Pros: complete audit trail, no data loss, continuity for long-tenured reps. Cons: longer timeline, higher cost, more data quality issues, and you're dragging years of junk into a clean system.
Option 2: Clean migration with archival. Migrate active records and recent history (e.g., open deals, contacts active in the last 12–24 months, closed deals from the last fiscal year). Archive the rest in a read-only HubSpot export or a separate database. Pros: faster, cleaner data, easier testing. Cons: sales reps lose deep history on older accounts unless you provide access to the archive.
The right answer depends on your business. If you're in a high-touch, relationship-driven industry where sales cycles span years and reps need to reference five-year-old notes, migrate more. If you're running a transactional sales model where last quarter's data is all that matters, migrate less.
The approach that tends to work best is a selective migration: active opportunities, contacts touched in the last 18 months, closed-won deals from the last two years, and key account history. Everything else gets archived. It's faster, cleaner, and still operationally sufficient.
Parallel Running Period and Rollback Planning
You can't run HubSpot and Salesforce in parallel for long-at least not without losing your mind. Bidirectional sync between two CRMs is fragile, expensive, and a recipe for duplicate records and conflicting data.
But you do need a plan for the gap between "HubSpot stops" and "Salesforce starts." That might be a weekend. It might be three days if your migration is complex. During that window:
- Leads still come in. Forms on your website, inbound emails, trade show sign-ups. You need a holding pattern: maybe leads flow into a Google Sheet, or your marketing automation platform queues them, or you manually import them into Salesforce once you're live.
- Sales activity continues. Reps are still making calls, sending emails, closing deals. If they can't log it in HubSpot and Salesforce isn't live yet, they need a temporary solution. A shared spreadsheet. A Slack channel. Something.
- Rollback risk. If the migration fails-data doesn't load, relationships break, workflows don't fire-can you roll back to HubSpot? That means keeping HubSpot accessible (read-only) for at least a week post-cutover, and having a plan to export any new Salesforce data and re-import it if you need to revert.
The shorter your parallel running period, the less painful this is. That's why testing (Phase 3) is non-negotiable. You want to go into cutover weekend confident, not hopeful.
Where Switching from HubSpot to Salesforce Fails
Your sales team doesn't care that Salesforce is more powerful. They care that HubSpot was easy and Salesforce feels complicated.
This is the failure mode that crops up most often: technically successful migration, organisationally disastrous adoption. Data migrates cleanly. Workflows work. But three months later, reps are still complaining, pipeline visibility has decreased, and half the team is logging activity in spreadsheets because "Salesforce is too slow."
Why? Because nobody explained why the change was happening, what would be better, and how their day-to-day work would improve. They were told "we're moving to Salesforce," handed login credentials, and expected to figure it out.
Change management starts before migration:
- Communicate early. Explain the business reason: consolidating CRM across portfolio companies, better reporting, tighter integration with other systems. Don't sugarcoat: "This will be uncomfortable for a few weeks, but here's what we're doing to support you."
- Involve power users. Identify two or three respected reps, bring them into UAT, get their input on page layouts and workflows. When they tell the team "I tested this, it works," adoption improves.
- Role-specific training. Not a two-hour generic Salesforce overview. Fifteen-minute walkthroughs tailored to each role: here's how you log a call, update a deal, run your weekly pipeline review.
- Support during hypercare. Dedicated Slack channel. Daily drop-in office hours. Fast responses to "how do I..." questions.
You can migrate systems faster than people change behaviour. Plan accordingly.
Integration Debt from Marketing Automation and Third-Party Tools
HubSpot isn't just a CRM-it's an ecosystem. Marketing automation, forms, landing pages, email campaigns, chatbots, reporting dashboards. When you migrate to Salesforce, you've got decisions to make:
Option 1: Keep HubSpot Marketing Hub, integrate with Salesforce. This is common. Salesforce handles sales pipeline and customer data: HubSpot handles marketing automation, email nurture, and lead capture. You integrate the two so leads flow from HubSpot into Salesforce, and closed deals sync back to HubSpot for reporting. Pros: you keep the marketing tools your team knows. Cons: integration complexity, ongoing sync issues, and you're still paying for HubSpot licences.
Option 2: Replace HubSpot with Salesforce Marketing Cloud or Pardot (Account Engagement). Full consolidation. Pros: single platform, unified data model, tighter integration. Cons: expensive, steep learning curve, and Marketing Cloud is overkill for many mid-market roll-ups.
Option 3: Replace HubSpot with a lighter marketing automation tool (Mailchimp, ActiveCampaign, Brevo) that integrates with Salesforce. Pros: cheaper, simpler, still functional. Cons: rebuild all your campaigns, forms, and workflows.
There's no universal right answer, but here's a practical framework: if your marketing team is small and your campaigns are straightforward (monthly newsletters, simple nurture sequences), replace HubSpot entirely and simplify your stack. If marketing automation is a revenue driver and your team is deeply embedded in HubSpot workflows, keep HubSpot Marketing Hub and integrate it. Just be realistic about the integration tax: it's another system to maintain, another sync to troubleshoot, another thing that breaks when you make changes.
And don't forget third-party tools. Every Zapier integration, every API connector, every reporting dashboard that pulls from HubSpot-those all need to be reconfigured or rebuilt to work with Salesforce. That's integration debt. Budget time and cost for it.
Realistic Timelines and Resource Requirements
Here's what to budget for, in time and people.
A straightforward HubSpot to Salesforce data migration for a single business unit-clean data, basic workflows, no custom integrations-takes 8–12 weeks from kickoff to hypercare. That assumes:
- ~5,000–20,000 contacts
- ~500–2,000 companies
- ~500–1,500 deals/opportunities
- 10–20 active workflows to rebuild
- 5–15 users
- Limited custom objects or integrations
A complex migration-multiple business units, messy data, custom integrations, marketing automation decisions-takes 12–20 weeks.
Resource requirements:
- Project lead (internal): 10–15 hours/week. Someone from ops, IT, or sales ops who understands the business and can make decisions.
- Salesforce admin/consultant: Full-time during Phases 2–4. Part-time during Phases 1 and 5. If you don't have one in-house, you'll hire a contractor or partner (like us).
- Data/migration specialist: Full-time during Phases 1, 3, and 4. Handles exports, mapping, scripting, testing, and cutover.
- Change management/training lead: Part-time during Phases 2–5. Builds training materials, runs sessions, supports users during hypercare.
- End users (sales, service, ops): 2–3 hours each for UAT, training, and feedback.
Cost? Budget £15,000–£40,000 for a straightforward migration (single entity, clean data) and £40,000–£80,000+ for complex, multi-entity consolidation with custom integrations. That includes configuration, migration execution, testing, training, and hypercare. It doesn't include ongoing Salesforce licences or Marketing Cloud if you're replacing HubSpot's marketing automation.
If your internal IT team is already stretched thin with BAU-and most are-this isn't a side project. It's a dedicated workstream that needs focus, expertise, and accountability. That's where partners like PMI Stack come in: we become the execution arm, working with your IT team, not around them. We handle the audit, mapping, migration, and hypercare, then hand off cleanly so your team can focus on running the business.
Making the Switch Without Losing Momentum
Switching from HubSpot to Salesforce isn't a technical project with a people problem. It's a business change with a technical execution component.
The architecture differences-contacts vs. leads, flat vs. hierarchical data models, workflow rebuilds-are solvable. The timeline is predictable. The cost is manageable. What's not solvable with better scripts or more licences is the human side: sales teams who resist change, marketing workflows that nobody documented, and integration debt that sneaks up three months after go-live.
If you're running a roll-up and facing CRM consolidation across your portfolio, here's what matters:
- Audit before you move. Understand your data, workflows, and integrations. Build a migration plan that reflects reality, not aspiration.
- Decide what stays and what moves. Clean migration with selective history is almost always faster and cleaner than a full historical dump.
- Test relentlessly. A week in a sandbox prevents a month of post-cutover chaos.
- Invest in change management. Your sales team will make or break adoption. Communicate, train, support.
- Plan for integration debt. Every third-party tool, every marketing workflow, every reporting dashboard-account for it.
CRM consolidation in a roll-up context isn't just a technical project -- it's an operational change that touches sales, marketing, finance, and frontline teams. If you're facing a HubSpot to Salesforce migration and need an execution partner who understands both the systems and the M&A context, we should talk.
No pressure, no pitch. Just a conversation about your specific situation and whether we can help.
Get in touch
