Salesforce to HubSpot Migration: The Agency Playbook

A Salesforce-to-HubSpot migration is a delivery project, not a data export. For an agency, the win is not moving records — it is landing the client in a HubSpot portal where pipelines, automations, and reporting work on day one, without the data loss, workflow gaps, or adoption stall that turns a "quick migration" into a six-month cleanup. This playbook covers how agencies scope, price, and execute those migrations for clients, including the parts that never migrate cleanly and how to set expectations before you touch a single object.

The stakes are higher than a config task. In our experience, failing to meet a client's technical demands — performance, personalization, and CRM integration chief among them — is the single most common reason clients switch agencies. A migration you fumble is a client you lose; a migration you nail is the foundation for a retainer.

Need a delivery team behind you? See our white-label HubSpot migration services.

When should an agency move a client off Salesforce?

Move a client when their Salesforce spend and complexity outrun what they actually use — not because HubSpot is "easier." The strongest migration cases share a pattern: a mid-market client paying for enterprise CRM customization they never operationalized, a marketing and sales team fighting siloed tools, or an admin-dependent org that can't self-serve changes. HubSpot's unified Smart CRM, native marketing and service tooling, and lower administrative overhead are the payoff.

Qualify the fit before you pitch the project. Ask what data must survive the move, what can be left behind, and whether the client needs a full cutover or a phased transition running both CRMs in parallel. The answer reshapes both the scope and the price.

Migration trigger	Good HubSpot fit	Watch-out
Enterprise Salesforce cost without enterprise use	Strong	Confirm no hard dependency on custom Apex/Flows
Siloed marketing + sales tooling	Strong	Marketing Hub tier must match automation needs
Admin-bottlenecked change management	Strong	Rebuild governance, don't replicate the bottleneck
Complex quoting / CPQ workflows	Conditional	Commerce Hub quote templates are more rigid than HubSpot's own legacy Quotes tool — budget rebuild time

Scope and price the migration before you touch data

Run paid discovery before you quote a fixed price. Twelve years and dozens of migrations in, we still build paid discovery into every HubSpot engagement before pricing the work — not because we don't know the platform, but because we remember exactly what it cost us when we assumed we did. A Salesforce instance always hides surprises: dead custom objects, validation rules nobody remembers writing, and automations firing on records the client swore were archived.

Discovery is where you audit and cleanse the source. Do this in Salesforce, before migration, so you are not paying to move garbage:

• Duplicate records — identify and merge duplicate contacts and accounts.
• Stale data — retire inactive leads, dead deals, and unused records.
• Custom fields and objects — flag which have HubSpot equivalents and which need custom properties or custom objects.
• Validation rules and dependencies — catch required fields and rules that need a workaround on the HubSpot side.

Package the engagement to match complexity. A basic migration with a defined automation scope can run as a fixed-fee project with a single dedicated subject-matter expert who owns it end to end; a multi-object migration with custom relationships and heavy reporting belongs in a phased retainer. Anchoring your pricing to the discovery findings — not a gut estimate — is what keeps a migration profitable instead of a break-even favor.

Map Salesforce objects to HubSpot

Object and field mapping is the technical heart of the migration, and Salesforce and HubSpot model data differently enough that a one-to-one copy will break. Build the mapping plan during discovery and get client sign-off on it before you import anything.

Salesforce	HubSpot	Mapping note
Contacts	Contacts	Cleanest mapping; watch merged/duplicate logic
Accounts	Companies	Re-establish contact–company associations post-import
Opportunities	Deals	Rebuild stages as pipeline deal stages
Leads	Contacts	HubSpot has no Lead object; merge into Contacts with a lifecycle stage
Custom objects	Custom objects	No native transfer — requires custom API work

Field-level mapping is where migrations quietly lose data. Salesforce picklists map to HubSpot dropdown values only if the values match exactly; checkboxes need their boolean logic confirmed; and multi-select picklists behave differently and have to be planned around. For clients whose Salesforce build leans on custom objects, plan the relationships deliberately — our guide to HubSpot custom objects walks through modeling them so associations and reporting survive the move.

What doesn't migrate — and how to set the client's expectations

Set expectations up front: several categories of Salesforce data and logic do not transfer, full stop. The agencies that get burned are the ones that say "yes, we'll move everything" before mapping what "everything" actually means. Name the gaps in the statement of work so nothing lands as a surprise mid-project.

Doesn't migrate automatically	What it means for the client
Custom objects	Only standard objects sync natively; custom objects need API work
Task & activity history	Emails, call logs, and activities won't fully carry over
Campaign data	Salesforce campaigns don't transfer
Attachments & files	Documents uploaded to Salesforce won't sync
Process Builder, Flows, workflow rules	Rebuilt manually in HubSpot workflows
Lead scoring models	Recreated on HubSpot's methodology
Reports, dashboards, forecasting	Rebuilt in HubSpot reporting

Quoting is a specific trap worth flagging to the client early. HubSpot Commerce Hub's quote templates offer less layout flexibility than HubSpot's own legacy Quotes tool — the trade-off is broader native payment integration, but the editor is more rigid, which can be a regression for a client migrating over complex, heavily customized quoting workflows. Naming that trade-off before migration protects both the client relationship and your scope.

Choose the migration method

Match the method to the data, not the other way around. Most agency migrations use a combination rather than a single tool, and custom objects almost always force the last row of this table.

Method	Best for	Limitation
HubSpot native Salesforce integration	Ongoing sync, phased cutover	Not built for historical bulk migration
Third-party tools (Import2, Trujay, Insycle)	Structured standard-object migration	Limited custom-object and association handling
Manual CSV export/import	Small, simple datasets	Manual association re-linking; error-prone at scale
Custom API integration	Custom objects, complex relationships	Requires development capacity

Custom objects and non-standard relationships are where migrations become genuine integration engineering. At the enterprise end, advanced HubSpot API work stops being optional — it's the price of admission for serving those clients at all, and it's exactly the technical scope agencies most often refer away. Rather than turn down the technical scope, agencies can white-label it: our HubSpot API integration team builds the middleware and custom-object syncs under your brand. For clients whose stack depends on real-time data movement, our primer on HubSpot webhooks covers the event-driven patterns that keep migrated data in sync afterward.

Configure HubSpot, validate, then cut over

Configure the destination portal before you migrate, then validate on a sample before the full load. Standing up pipelines, deal stages, custom properties, lead scoring, and user permissions in advance means data lands in a structure that works rather than an empty portal you scramble to shape after the fact.

Test on a controlled sample first:

• Migrate a small set of contacts, companies, and deals.
• Verify field mapping against the client-approved plan.
• Confirm contacts associate correctly to companies and deals.
• Validate that rebuilt workflows and lead scoring fire as expected.

Once the sample checks out, run the full migration, re-validate every record and association, and monitor for discrepancies through the first weeks of live use. This is also where automation pays for itself: we've found that templated, automated onboarding built on custom objects and API integrations can cut non-billable setup time by up to 60% versus doing it by hand — the difference between a migration that erodes your margin and one that scales across a book of clients.

Deliver it white-label

Deliver the whole migration behind your agency's brand so the client never sees a subcontractor. For white-label partners, all work is delivered behind the curtain: when accessing a client's HubSpot portal, the delivery team uses partner-provided credentials so end clients are never aware of a third party in their systems. Practically, that means operating from an email address on your domain and showing up as your agency's HubSpot solutions architect on client calls.

That is what lets an agency win Salesforce-to-HubSpot migrations it doesn't have the in-house bandwidth or CRM-engineering depth to deliver alone — the technical scope gets covered, the client relationship stays entirely yours, and the migration becomes the on-ramp to a longer retainer instead of a one-off project you had to refer away.