Skip to content
crm migration
HubSpot CRMSalesforce CRM

Move your HubSpot CRM data into Salesforce CRM

Your custom fields, your history, your relationships. Not only the fields both apps happen to have in common.

Start free assessment

We run HubSpot CRM to Salesforce CRM migrations. The assessment is free and comes before any commitment.

Running this for a client? Explore partnership options.

What moves

See where each object lands in Salesforce CRM.

HubSpot CRM

Companies
Accounts
Contacts
Contacts
Deals
Opportunities
Notes
Tasks with the files still attached
Calls and emails
Tasks
Meetings
Events with the files still attached
Deal pipelines and stages
Opportunity stages matched on what your stage meant, won, lost or still open, with the HubSpot stage name kept in a field beside it
Owners
Matched to your Salesforce users
Custom properties
Created as custom fields on the object they belong to
Associations between records
Salesforce relationships and junction records
Attached files
Salesforce Files
Start free assessment
What comes across

Keep the data that matters to you.

Keep records connected

Keep deals linked to contacts and companies, and activities linked to their records in Salesforce CRM.

Your custom fields come with you

We find your custom fields in HubSpot CRM and plan how their values will travel to Salesforce CRM before migrating their records.

Bring your activity history

Your activity history arrives on the record it belongs to. This page names which types transfer and any limit on them.

Match owners, pipelines and stages

We match them to your Salesforce CRM users and stages.

Review changes before the run

The plan flags values that change during migration. The original value comes across beside the converted one.

Keep data with no matching field

Where possible, we create a field in Salesforce CRM for data with no matching field.

A Contacts plan showing standard fields, a custom field, usage percentages and migration switches.
Demo output. Our HubSpot demo uses synthetic records. This Contacts plan shows custom field usage and which fields will migrate. View at full size.

Demo output from our own system. Synthetic records, not customer data.

Limits and changes

Know what changes and what stays behind.

Each row explains a limit and what you can do about it. Open the details for the reason and supporting source.

Needs setup or a plan change

How many custom fields Salesforce will hold per object depends on your edition

View detailsHide details

Salesforce allows 100 custom fields per object on Professional, 500 on Enterprise and 800 on Unlimited. A HubSpot CRM object carrying more custom properties than your edition allows cannot bring them all across.

Verified against help.salesforce.com

The free assessment counts them first, so you see that before you commit.

Attached files count against a fixed storage allowance in your Salesforce org

View detailsHide details

Salesforce allocates 10 GB of file storage per org on Professional, Enterprise and Unlimited, and 1 GB on Essentials and Starter. Attachments count against it.

Verified against help.salesforce.com

Where years of HubSpot CRM files would land above what your org holds, we tell you before the run rather than after it fills.

Moves with changes

Your notes, calls, emails and meetings all share one pool of custom fields

View detailsHide details

Salesforce keeps Tasks and Events on a single Activity object, and it allows up to 300 custom fields for activities in total rather than per kind. So custom properties from HubSpot CRM notes, calls, emails and meetings compete for the same allowance.

Verified against help.salesforce.com

We agree which ones matter before anything is written.

Stay in control

Paused runs resume. You can undo the migration.

Undo the migration

One action removes the records we wrote to Salesforce CRM. Review what will remain before you undo and retry.

Paused runs resume

A paused run resumes where it stopped, without losing progress or duplicating records.

Read-only in HubSpot CRM

We only read HubSpot CRM. Nothing is written back to it.

Catch up before switching over

Keep working in HubSpot CRM while you check the results. Then bring across the latest changes before switching over.

What undo removes and what remains

In Salesforce CRM after the migration

The records we wrote
Removed
The history and attachments that came with them
Removed
Except products and price lists, where we brought them across
Left in placeThese may be used in your quotes or reports, so removing them could affect other work.
The custom fields we created
Left in place, emptyWe can remove these separately on request.
What it costs

One payment, based on the records you move.

From $799

Covers up to 20,000 records. Larger migrations use higher tiers. You pay once per migration, with no recurring charge.

Get your exact price for free

Connect HubSpot CRM to see your record count and price before you commit.

A 30-day money-back guarantee

Ask for a refund within 30 days of your migration being marked complete. We reverse the migrated data out of Salesforce CRM and refund you.

View pricing.

FAQ

Questions about moving HubSpot CRM to Salesforce CRM

Will my HubSpot custom properties come across?

Yes. The free assessment finds them in HubSpot, and they are created as custom fields on the matching Salesforce object before records are migrated. Review the plan and choose whether to leave unused custom properties behind.

What happens to my notes, calls, emails and meetings?

Notes, calls and emails land as Salesforce Tasks, and meetings land as Events, each one on the record it belongs to. The file attachments, owners and timestamps come with them.

Do my deal pipelines and stages survive?

Your HubSpot stage names are not recreated in Salesforce. Each deal lands on the Salesforce stage that matches what its HubSpot stage meant, won, lost or still open, so a won deal lands in a won stage rather than at the top of the funnel, and the original HubSpot stage name is carried across in a field beside it so you can still see what it was.

Do I have to build a field map?

No. We work out what each value becomes, so nobody builds a field map. You review the plan before the migration runs. A HubSpot field with no native home in Salesforce can be brought along as a new field instead of being left behind.

Who actually runs the migration?

We run the migration and stay reachable. Connect HubSpot for the free assessment and price, then Salesforce to complete the plan. Nothing moves until you ask.

Can I keep working in HubSpot while this happens?

Yes. We only read HubSpot and never write back to it. Keep working while you check the results, then bring across the latest changes before switching over.

What if the result is not what I expected?

You can undo the migration, correct the issue and run again. Created fields, shared catalogue data and any other items listed as retained stay in place.

What does it cost?

One payment, based on the records that move. The free assessment of HubSpot gives you the exact count and price before you commit. Payment is by invoice, with no subscription.

Next step

Create an account and connect HubSpot CRM for your free assessment. See your record count and price before you commit. Nothing moves until you ask.

Start free assessment