A Salesforce to HubSpot migration for a financial services firm usually takes 3 to 6 weeks as a single full cutover, and longer when it is split into phases. Choose a full cutover when one team owns the data and you can freeze the old system for a weekend. Choose a phased move only when business lines, integrations or regulators force you to run both systems for a while.
This guide is written for operations and CRM leaders at wealth managers, banks, credit unions, insurers and lenders who have already decided on HubSpot and now have to decide how to get there. Vantage Point implements both Salesforce and HubSpot, so we have no stake in which platform you pick, only in the move going well.
In a full cutover, everyone stops using Salesforce on the same day. You freeze the old system, load the final changes into HubSpot, switch integrations and turn HubSpot on for every user at once. Salesforce stays available read-only for a short period, then it is archived.
In a phased migration, you move in stages. The stages are usually by team (marketing first, then sales, then service), by business line (the RIA before the trust company) or by data type (contacts and deals first, history later). For a period, both systems are live and something has to keep them in step.
Both approaches end in the same place. The difference is how long you carry two systems, two sets of permissions and two sources of truth.
For a single cutover, our own planning range is 3 to 6 weeks from scoping to go-live, which is how we price our Salesforce to HubSpot migration package (from $12,000). The weeks break down roughly like this:
| Stage | Full cutover | Phased migration |
|---|---|---|
| Scoping and data inventory | Week 1 | Weeks 1 to 2, because each phase needs its own boundary |
| Field mapping and cleanup | Weeks 1 to 2 | Repeated for each phase |
| Test load and user checks | Weeks 2 to 4 | One per phase |
| Sync between systems | Not needed | Built, tested and monitored for the whole overlap |
| Cutover | One weekend, weeks 3 to 6 | One per phase, often weeks or months apart |
| Hypercare | Two weeks | Two weeks after each phase |
A phased move is rarely faster in total. Each phase repeats mapping, testing and training, and the overlap needs a sync that someone has to build and watch. Firms choose it for control, not speed.
Most firms with under a few hundred users fit this profile. A single cutover is also simpler to explain to a compliance team, because there is one date after which the record of truth changed.
If you go phased, keep the overlap short and decide in advance which system is the record of truth for each object during it. Two-way sync between Salesforce and HubSpot works, but it is the part of a phased migration most likely to create duplicates and conflicting updates.
Regulated firms have obligations that do not pause for a migration. SEC Rule 204-2 requires registered advisers to keep required books and records for five years, the first two in an easily accessible place. Broker-dealers follow Exchange Act Rule 17a-4 and FINRA Rule 4511. Banks and credit unions have their own retention schedules, and insurers follow state rules.
| Risk | Full cutover | Phased migration |
|---|---|---|
| Records split across systems | Short window, then one system plus an archive | Longer window, and records can be updated in both |
| Access control | One permission model to review at go-live | Two models to keep consistent during the overlap |
| Email archiving and supervision | Switched once | Must cover both systems until the last phase |
| Vendor oversight (Regulation S-P) | One data flow to document | Additional sync tools and data flows to document |
| Exam requests | Answered from HubSpot and the Salesforce archive | May need records from both live systems |
Whichever approach you take, export Salesforce in full before cutover and keep that export outside HubSpot with a manifest. Reconcile record counts object by object and keep the reconciliation in your files. Our page on CRM recordkeeping for compliance covers the controls in more detail.
Some Salesforce orgs are simple to move and some are not. These are the factors that push a project toward phases or toward a longer single cutover:
Our guide to what transfers from Salesforce to HubSpot goes object by object.
If most answers point to one team, few integrations and a near renewal, plan a full cutover. If two or more answers point to separate business lines or integrations that cannot be ready, plan phases and keep each one short.
A single cutover usually takes 3 to 6 weeks from scoping to go-live. Firms with Financial Services Cloud objects, many integrations or long activity history sit at the longer end. Phased migrations take longer in total because each phase repeats mapping, testing and training.
It lowers the risk of one bad weekend, but it adds the risk of running two systems with a sync between them. For most firms, a well-tested single cutover with a full Salesforce export is the safer option. Phases make sense when integrations or business lines cannot move together.
Yes. HubSpot has a native Salesforce integration and third-party sync tools exist. Decide which system owns each object during the overlap, and keep the overlap as short as you can.
Move the history users need into HubSpot and keep a full export of Salesforce outside HubSpot with a manifest. Many firms also keep Salesforce read-only for a short period before archiving it.
You need somewhere to run a full test load before production. HubSpot sandboxes are available on Enterprise subscriptions. Firms on Professional often use a separate test portal.
Our migration package starts at $12,000 and is quoted after a scoping call. Most firms also buy a Hub setup package so HubSpot is configured before data arrives.
If you are deciding between a single cutover and a phased move, start with a free CRM assessment. We will look at your Salesforce org, your integrations and your records obligations and give you a dated plan. See how we run migrations on our HubSpot migration for financial services page.