Salesforce to HubSpot migration
Move the records. Rebuild what matters. Give your team a CRM they can use.
Your migration needs a plan for customer data, connected systems and everyday work. Start with what HubSpot must support, then agree on what moves, what changes and how the result will be checked.
Selworthy lists CRM Migration and CRM Implementation in the HubSpot Solutions Partner Directory. Exact deliverables are agreed in your project scope.
Make the move visible before moving the data.
This illustrative starting map shows common record names to discuss. Your data model, migration route and HubSpot subscription determine the final mapping. It is not an automatic transfer specification.
Source records
Target recordsAgree on matching rules, duplicate handling and which lead details to retain.
Define company matching and how people remain linked to the right business.
Map pipelines, stages, owners and relationships before importing deal data.
Before your team switches
Explain missing, rejected, updated and intentionally excluded records.
Check that contacts, companies and deals connect as agreed.
Test assignment, follow-up and reporting against expected results.
Replace Salesforce, or keep both systems?
A migration and an ongoing integration solve different problems. If Salesforce stays, define which system owns each value, the direction of updates and who resolves sync failures. If it is being retired, define the work and history that must be ready in HubSpot first.
HubSpot documents a Salesforce import-and-sync route for qualifying Professional or Enterprise subscriptions. That route does not, by itself, complete a business transition. Check the current requirements before choosing it. An agreed file-based or other evaluated approach still needs a mapping, test and acceptance plan.
Scope the whole working system.
A record count is a starting point, not a complete brief. Use this scope ledger to separate required migration work from optional changes and information that can remain in an archive.
- Records, fields and owners
Inventory standard and custom data, required properties, picklist values, currencies and active or inactive owners. Decide which records to move, clean, combine or exclude. Keep a source-to-target identifier plan so the team can trace a migrated record back to its origin.
- Relationships and history
Map contact-to-company and deal relationships, including exceptions such as several contacts on one opportunity. Identify which activities, notes, attachments and historical dates need to remain usable. Assess availability and the destination separately instead of promising that every timeline will look identical.
- Workflows and connected apps
For each automation, record its trigger, conditions, actions, owner and business purpose. Decide whether to rebuild, redesign or retire it. Map integrations separately: what sends data, what receives it, which value wins and what happens when an update fails. Moving records does not reproduce Salesforce automation.
- Reporting and access
List the reports people use to make decisions, then trace their inputs and definitions. Map team access and ownership before testing. A total that looks right is not enough if the wrong people can see it, a pipeline stage means something different or a report excludes required records.
For file-based imports, HubSpot requires suitable unique identifiers for updates and associations. A Salesforce ID is not automatically a HubSpot Record ID. Review the import-file requirements.
Test a real pattern, not just a clean row.
Choose representative test records that expose the difficult cases: duplicates, blank fields, inactive owners, multiple relationships and open versus closed deals. Agree on the expected outcome before running a test.
What to reconcile
- Record counts: compare expected new and updated records with actual results. Explain exclusions and errors.
- Values and relationships: spot-check important fields, dates, owners and links back to the source.
- Business behavior: test a representative assignment, handoff and report. Check that unexpected messages or enrollments do not fire.
HubSpot's import dashboard reports new records, updated records, new associations and errors. Use it as one part of acceptance, not as proof that the business is ready. Review past import results.
Plan the switch and the first working day.
Cutover means changing where the team does its everyday work. It needs an owner and a go/no-go decision.
Before the switch
Agree on the final data capture, any period of restricted edits, recovery approach and acceptance owner. Decide how changes made during testing will be handled. Keep unresolved exceptions visible.
At the switch
Reconcile the final scope, verify permissions and check connected systems against the runbook. The named business owner decides whether the acceptance criteria are met. If not, follow the agreed recovery or postponement plan.
After the switch
Train people around their actual roles: finding a customer, updating a deal, handing off work and reading a report. Identify where history lives, who handles issues and what support is included. Salesforce retirement is a separate, deliberate decision.
Bring the decisions that shape the scope.
For an initial conversation, bring your Salesforce setup, current or planned HubSpot subscription and the reason for the move. Be ready to identify:
- The records, history and processes that cannot be left behind.
- Custom objects, connected applications and important reports.
- Whether both CRMs will run during a transition.
- Access constraints, a decision owner and any contractual timing.
Agree on deliverables, exclusions, timing and fees in writing. This page does not quote a standard price or promise a fixed timeline.
Salesforce migration questions
Product documentation checked September 14, 2026.
Does connecting Salesforce mean the migration is finished?
No. A connection and a completed business transition are different outcomes. If the goal is to stop using Salesforce, make access, process readiness and historical-data requirements part of the acceptance plan.
Will all our history and custom data move?
Do not assume a like-for-like transfer. Identify the records, activity types, files and custom data you need, then assess the available source data, migration route and HubSpot requirements. Agree on what will move, what needs another approach and what will remain accessible elsewhere.
Why can imported Salesforce contacts have missing fields?
HubSpot states that the initial Salesforce lead/contact import brings over the email address. Remaining field values depend on a subsequent sync; contacts outside an inclusion segment can retain blank properties after the initial import. Review this behavior before testing.
Can deleting an import undo changes to existing records?
Do not treat deletion as rollback. HubSpot states that deleting imported records does not reverse updates made to existing records. Plan recovery before making changes. Read HubSpot's import-management guidance.
Start with a clear migration brief.
Tell us what you use today and what your team needs from HubSpot. We can start the conversation around the data, processes and decisions that define the work.
Discuss your Salesforce migrationDo not send credentials or customer records through the initial inquiry form.