HubSpot migration
A Salesforce to HubSpot migration moves your accounts, contacts, leads, opportunities, cases and activities into HubSpot, and rebuilds the flows, validation rules, reports and permissions that do not transfer. Selleris, a HubSpot Solutions Partner, first checks whether a full move pays off or Salesforce should stay and connect to HubSpot, then fixes the price, from $5,000, and you pay when the migrated data passes the checks on this page.
Facts checked against HubSpot and Salesforce documentation on November 12, 2026.
[Sergey Danishevskiy]
I wrote this page. Every migration starts with a call with me.
If moving is not the right call for you, Sergey will say so on the call.
Leaving Salesforce pays off when the team works around it instead of in it. Keeping it is the better call when Salesforce carries logic that HubSpot would have to rebuild at great cost, or while its contract runs for another year.
Maps, moves, rebuilds and checks, from $5,000.
Connects Salesforce to HubSpot, builds your sales system in HubSpot and proves it on part of your pipeline first.
Plans the move back from the date your notice is due.
When Salesforce stays, a full move can follow later, when it pays off.
HubSpot has two tools for Salesforce, built for different jobs. HubSpot warns that using both at the same time creates duplicate records in HubSpot and Salesforce, so a migration picks one for each stage.
Keeps both CRMs in sync. A staged switch starts here, with HubSpot next to Salesforce for marketing or part of the team while the contract runs.
HubSpot's tool for a clean switch, with HubSpot's APIs where Smart Transfer stops.
Most Salesforce standard objects have a direct place in HubSpot. Smart Transfer's Salesforce mapping covers the core of them; the rest move through HubSpot's APIs or are rebuilt.
Salesforce automation and configuration do not transfer to HubSpot. Each piece is rebuilt with HubSpot's own tools, or retired if nobody relies on it.
Territory management, opportunity splits and custom fiscal years need a decision in the mapping, since HubSpot handles some of them differently and some not at all.
Tasks, events, notes and emails stored in Salesforce move with their records. Three kinds of history need a plan before the move.
HubSpot does not sync them, because Salesforce does not store them as task activities. They stay in each person's mailbox, or are exported and attached to their records.
Salesforce keeps field history for 18 months in its interface and 24 months through the API. What you need from it is exported before the move and kept as an archive or as properties.
HubSpot records the date a deal enters each stage by itself. Selleris copies Salesforce's opportunity stage dates into properties of their own, so last year's conversion rates can still be reported.
Work back from the day your notice to Salesforce is due, not from the renewal date; your order form sets how much notice it needs. Starting four to six months before the notice date leaves room for the test batch, the rebuild and a read-only period.
Salesforce counts API calls per org and per day, and every integration shares that budget, so large objects move through Salesforce's Bulk API on a schedule that keeps your other integrations working.
Your org, your reasons, and whether to move, connect or stay.
Every object, field and automation, what moves, what is rebuilt and what stays behind. You sign it off.
A full Salesforce export first, then a sample of your trickiest records moved and checked.
The data moves; workflows, reports and permissions are rebuilt; integrations are reconnected.
The checks below, training for your team, and Salesforce kept read-only until your contract ends.
Custom objects, Apex logic and integrations add time. Your fixed-price proposal sets the dates.
Acceptance
A migration is finished when these checks pass, not when the import ends. They are part of the result you pay for.
Contacts, companies, deals, activities and notes in HubSpot match the count in the old CRM, or each difference has a reason you signed off.
On a sample from every pipeline, each deal is linked to the same contacts and company as before, with the same notes and activities.
Records belong to the same people as before. Records of people who have left go to an owner you name.
Create dates, close dates and deal amounts match the old CRM, and the open pipeline adds up to the same total.
Each workflow that replaces an old automation runs on test records before your team relies on it.
A full export of the old CRM is kept before the first record moves, and the old CRM stays read-only until you close it.
Salesforce to HubSpot migration
Your core Salesforce objects moved to HubSpot, automations and reports rebuilt, and every check on this page passed. The final price is fixed after the free diagnostic.
One fixed price agreed after the free diagnostic
Get your free diagnosticHow you pay
The price is fixed before we start. You pay when the checks above pass. No upfront fee.
Yours from day one HubSpot, data and documentation in your name
See pricing
Solutions Partner (opens in a new tab) 
Partner 
Partner 
Partner 
Partner 
Partner The questions Salesforce teams ask before they move. If yours is missing, bring it to the call.
For a team of up to 50 users with a standard Salesforce org, plan on six to ten weeks from the free diagnostic to the day the team works in HubSpot. Custom objects, Apex logic, files and integrations add time. Start four to six months before your Salesforce notice is due, so the test batch, the rebuild and a read-only period fit without a rush. Your fixed-price proposal sets the dates.
A Salesforce to HubSpot migration with Selleris starts at $5,000. The final price is fixed after the free diagnostic and depends on the objects, records and years of history you move, custom objects and quoting logic, the flows, Apex, validation rules and reports to rebuild, and files and integrations. You pay when the migrated data passes our checks. HubSpot licences are separate, in your name, at HubSpot’s price.
Yes. When Apex, CPQ or an industry cloud runs your quote-to-cash, or your Salesforce contract runs for another year, Salesforce can stay. The HubSpot Salesforce connector keeps both CRMs in two-way sync and needs a Professional or Enterprise HubSpot subscription. Selleris builds your sales system in HubSpot, connects Salesforce to it and proves the approach on part of your pipeline first.
Use the HubSpot Salesforce connector to keep both CRMs in sync while Salesforce stays, and HubSpot Smart Transfer for a one-time move. HubSpot warns that using both at the same time creates duplicate records in HubSpot and Salesforce, so a migration uses one per stage. Smart Transfer does not move custom objects; those move through HubSpot’s APIs.
No. Salesforce flows, Process Builder, Apex, validation rules, formula fields and reports do not transfer to HubSpot. They are rebuilt: flows as HubSpot workflows, Apex as workflows, custom code or a function in your own Azure tenant, validation rules as property rules, formulas as calculated properties, and reports as HubSpot reports. Each rebuilt automation is tested on test records before your team relies on it.
Yes, as HubSpot custom objects, which need a HubSpot Enterprise subscription. HubSpot Smart Transfer does not move custom objects, so they are created in HubSpot first and loaded through HubSpot’s APIs, with their associations to companies, contacts and deals. Lookup fields between custom objects become associations, decided object by object in the mapping you sign off.
Tasks, events, notes and emails stored in Salesforce move with their records. Emails from Einstein Activity Capture do not sync to HubSpot, because Salesforce does not store them as task activities. Field history is kept by Salesforce for 18 months in its interface and 24 months through the API, so what you need is exported before the move. Opportunity stage dates are copied into their own properties for reporting.
Check your Salesforce order form for how much notice it needs before renewal, and plan back from that date. A migration with rebuilt automations and reports typically takes six to ten weeks for a team of up to 50 users, so start four to six months before the notice is due. Keep Salesforce read-only after the cutover until the checks pass and the contract ends.
Pipedrive restructured in October 2026. What moves to HubSpot, what does not, and how to switch without a rush.
From $2,000
Smart Transfer moves the core; emails, custom modules and Blueprints need a plan. What moves and what stays in Zoho.
From $2,000
Essentials plans lose the REST API on November 30, 2026. Export first; what moves to HubSpot and what can stay.
From $2,000
SuiteCRM 7.14 left support in March 2026. Upgrade to 8 or move; what comes across from your SuiteCRM database.
From $2,000
Now Constant Contact Lead Gen & CRM. Contacts and deals move; emails, pages, workflows and scoring are rebuilt.
From $2,000
No fee for the diagnostic, and no obligation to buy.
