Salesforce to HubSpot
Salesforce to HubSpot migration.
Salesforce is the migration that punishes shortcuts. The data moves cleanly, but the logic around it does not, because Salesforce holds a decade of Apex, flows, validation rules, and formula fields that have no one-to-one equivalent in HubSpot. The job is deciding what to rebuild, what to retire, and what was never doing anything useful in the first place.
What breaks
What does not survive a copy, and what we do instead.
Apex and Visualforce
Custom code has no HubSpot equivalent. Anything it did is re-implemented as workflows, calculated properties, or an integration, or retired if it was legacy.
Formula and roll-up summary fields
These do not migrate as live values. They are rebuilt as HubSpot calculated properties or workflow-maintained fields, so the numbers keep updating.
Record types
Salesforce record types usually map to a mix of HubSpot pipelines, property options, and separate objects. This is a design decision, not a copy.
Flows and Process Builder
Automation is rebuilt as HubSpot workflows. This is the moment to remove the automations nobody remembers turning on.
Report types and sharing rules
HubSpot reporting and its permission model work differently. Reports are rebuilt against the new schema and access is remapped to teams.
Carries over
Migrates in, intact
- Leads, Contacts, Accounts, and Opportunities
- Activity and email history, notes, and tasks
- Most standard and custom fields, mapped to a clean schema
- Record owners and team assignment
- Attachments and files
Rebuilt, not copied
Does not carry over
- Apex classes, triggers, and Visualforce pages
- Formula and roll-up fields as live formulas (rebuilt)
- Flows and Process Builder automation (rebuilt as workflows)
- Report types and dashboards (rebuilt)
- Permission sets and sharing rules (remapped to HubSpot teams)
Timeline
How long it takes
A typical Salesforce migration runs two to four weeks: three to five days to audit and inventory the org, about a week to design and approve the mapping and rebuild plan, then one to two weeks to migrate, validate, and rebuild automation. Volume and the amount of custom logic drive the range, and the exact scope is fixed in writing after the audit.
Preparation
What to prepare
- Freeze schema changes in Salesforce during the migration window
- Deduplicate contacts and accounts, or ask us to do it on the way in
- Confirm which history you need: everything, or a cut-off date
- List every integration touching Salesforce today
- Identify which reports leadership actually looks at
FAQ
Salesforce migration questions.
Will I lose my Salesforce history?
No. Activity history, emails, notes, and tasks migrate in and attach to the right records. You decide whether to bring everything or set a cut-off date, and the source org stays intact until you approve the cutover.
What happens to my Apex code and flows?
Custom code does not move. Everything it did is re-implemented as HubSpot workflows, calculated properties, or an integration, and legacy automation nobody uses gets retired instead of rebuilt.
Can we run both systems during the switch?
Yes. Salesforce stays live until the cutover you sign off on, so there is no window where your team has no CRM.
How long does a Salesforce migration take?
Usually two to four weeks depending on data volume and how much custom logic has to be rebuilt. The exact timeline is scoped in writing after the audit.
What about our Salesforce integrations?
We inventory every integration first, then re-point or rebuild each one against HubSpot as part of the integration phase, so nothing is left dangling after the cutover.
Start with a Salesforce audit.
Before anything moves, you get a written inventory of your source system and the mapping plan. The fee is credited in full toward the build if you move forward.
The audit fee is credited in full toward the build if you move forward.