Skip to content
Northstar Solutions

The first call is free.

Contact us

Implementation

Migrating to HubSpot from another CRM: what moves and what you rebuild

Companies, contacts and deals move to HubSpot. History takes more work and automations are rebuilt. How to migrate from Pipedrive or Lime.

By , founder and RevOps consultant

Implementation · Sales· 10 min read

When you migrate to HubSpot from another CRM, companies, contacts, deals and products come with you, whichever system you are leaving. The history can be moved too: notes, calls, meetings and tasks, and emails partly. It takes more work, and attachments are moved in a step of their own. Automations, reports and integrations do not come along. You rebuild those in HubSpot. From Pipedrive, Salesforce, Dynamics 365 and Zoho CRM you can use HubSpot's own tool, Smart Transfer. From Lime, Upsales and SuperOffice you migrate with file imports or through the API.

The facts about HubSpot come from HubSpot's own documentation and were checked on 15 November 2026.

What data moves when you switch to HubSpot?

Most customer data can be moved. The difference is how much work each part takes.

Data Does it move? How
Companies, contacts and deals Yes Smart Transfer or file import
Products and the stages of your sales process Yes Smart Transfer, or built by hand in HubSpot
Custom fields Yes, after mapping Each field in the old system is paired with a field in HubSpot
Notes, calls, meetings and tasks Yes Smart Transfer or a file import of activities
Emails Partly Can be imported as activities. What comes along depends on how the old system stored them
Attachments and documents Partly A separate step after the migration, or through the API
Automations No Rebuilt as workflows in HubSpot
Reports No Rebuilt in HubSpot
Integrations, for example with Fortnox No Reconnected to HubSpot
Email and quote templates No Created again

Three ways to move data into HubSpot

There are three routes in, and the system you are leaving decides which one you take.

Smart Transfer. HubSpot's own tool for moving from another system. It is available in every HubSpot licence, but some features need additional licences. Custom field mappings need Data Hub (formerly Operations Hub), for example. The tool supports 13 systems: Pipedrive, Zoho CRM, Dynamics 365, ActiveCampaign, Copper, Mailchimp, Keap, Salesforce, Account Engagement (Pardot), Marketo, Zendesk, Freshdesk and Monday.com. Only a Super Admin can run it, and the transfer goes one way, into HubSpot.

File import. You export data from the old system and import the files into HubSpot. HubSpot accepts .csv, .xlsx and .xls with one sheet per file. On a paid licence a file can be up to 512 MB and hold 1,048,576 rows. On the free tools the limit is 20 MB per file. Activities can be imported too: notes, calls, emails, meetings and tasks.

The API or a migration tool. When the history is large, when attachments have to come along or when the data models differ a lot, you need a migration through HubSpot's API. A consultant does it, or a third-party tool.

From Pipedrive, Smart Transfer moves most of it

Smart Transfer moves Pipedrive's people, organisations and deals to contacts, companies and deals in HubSpot. Products, currencies, users and notes come along. So do calls, meetings, tasks and email activities.

Four things to know before you start:

  • Activities need Data Hub. HubSpot states that a Data Hub licence is required to sync Pipedrive activities.
  • Logged emails don't come along. Smart Transfer syncs email activities from Pipedrive, but not logged emails.
  • Custom objects aren't supported. If you built custom objects in the old system, they have to be moved another way.
  • Attachments move in a step of their own. Attachments, deal participants, products on deals and relationships between organisations are transferred once, after the first sync. They are not kept up to date afterwards.

The migration itself has four steps in the tool. First an audit that shows how objects and fields in Pipedrive fit HubSpot and how many records are involved. Then you choose what to bring, and HubSpot creates the fields and pipelines it needs. After that the sync starts, which can take several hours. It keeps running in the background and keeps the transferred records up to date until you turn it off. Last, you transfer what the sync doesn't support.

From Lime, Upsales or SuperOffice you migrate with file imports or the API

Lime, Upsales and SuperOffice are not among the 13 systems Smart Transfer supports. The migration is done with exports and file imports, or through the API when the history is large.

Start with the key between the files. HubSpot recognises contacts by email address and companies by domain name. Many Swedish companies in a CRM have no domain, and groups often share one. So create a field for the organisation number (organisationsnummer) in HubSpot and set it to require unique values. Then the organisation number can be the key when contacts, deals and activities are linked to the right company.

Import in this order:

  1. Companies, with their organisation number.
  2. Contacts, with the company's organisation number in its own column.
  3. Deals, linked to company and contact.
  4. Activities: notes, calls, meetings, emails and tasks. Include the activity date. Otherwise HubSpot uses the date of the import, and the whole history looks as if it happened on one day.

Read the contract with your old vendor before you set a date. Lime's pricing page says the contract term is 12 months and the notice period is 60 days before the next contract period. Check what applies to your vendor, and how long you can reach your data after the contract ends. Do the final export while you still have full access.

How a migration works, step by step

  1. Decide what to bring. All open deals and all customers, but how many years of lost deals and old activities? Someone has to own everything you move.
  2. Clean up in the old system. Merge duplicates and remove fields nobody has filled in for years. Cleaning before the move is easier than after. How to do it in HubSpot is covered in How to clean up HubSpot before you switch on the AI agents.
  3. Build HubSpot first. Pipelines, deal stages, fields and permissions should exist before the data arrives. Don't copy the old system's structure as it is. The migration is the moment to drop stages and fields nobody uses. For what the record can look like per team, see One customer, one place.
  4. Map the fields. A table with three columns: the field in the old system, the field in HubSpot, and what happens to values that don't fit. A free-text field that becomes a dropdown needs a translation for each value.
  5. Test with about fifty companies. Pick companies with a lot of history, several contacts and both won and lost deals. Ask a rep to compare the records in both systems.
  6. Move everything. Keep the order: companies, contacts, deals, activities. Download the error file after each import and fix the rows that failed.
  7. Check. Compare the number of companies, contacts and open deals between the systems, and the total value of open deals per deal stage. Have every rep go through their own deals.
  8. Switch on a set date. From that day the old system is read-only. Connect the reps' inboxes and calendars to HubSpot the same day, so new emails and meetings land on the right record.

What doesn't move, and what can't be undone

Automations don't come along. Smart Transfer creates a few workflows that handle differences between the two data models, but your own flows for lead routing, reminders and follow-ups are rebuilt as workflows in HubSpot. The same goes for reports and templates.

Integrations are reconnected. A connection between the old system and Fortnox stops working the day you switch. Plan the new connection together with the migration. What should flow in which direction is covered in From quote to invoice in HubSpot.

Two things can't be reversed:

  • Merges. HubSpot states that merged records can't be unmerged.
  • Updates through an import. Records an import created can be deleted afterwards. Values an import overwrote on existing records can't be restored. You have to import the correct values again or fix them by hand.

That is why the test migration should happen before the team has started working in HubSpot.

Don't move personal data you don't need

A migration is a good time to clear out. Contacts nobody has been in touch with for years, and that you have no reason to keep, shouldn't follow you to a new system. Decide on a cut-off before you export, for example no activity in two years and no open deal, and have the person responsible for GDPR at your company approve it.

Look at where the data ends up, too. HubSpot has data centres in the US, Canada, Australia and the EU, where the EU data centre is in Germany. Which one your account gets depends on where you are when you buy the licence, and it is shown when you sign up. Check that it says EU before you import anything.

What does a migration to HubSpot cost?

With us, the import or migration of existing data is part of a HubSpot implementation, which costs SEK 25,000–50,000 for a smaller team and from SEK 50,000 for larger setups, excluding VAT. Where you land in that range depends on how much history comes along, how many custom fields you have and whether an integration has to be reconnected. What else drives the price is in What does a HubSpot implementation cost?. The HubSpot licence comes on top, and we work through that in What does HubSpot cost per user?.

Start with one thing this week: export the list of every field in your current CRM and mark the ones that were filled in during the past year. That list shows how big the migration is.

Common questions

Can we migrate to HubSpot ourselves? Yes, if you have a few thousand contacts, one pipeline and don't need the history. A file import is enough then. What usually goes wrong is the links between the files, so contacts end up without a company and deals without a contact. Test with about fifty companies before you import everything.

Does our email history move to HubSpot? Partly. Emails can be imported as activities with a body and a direction, but it depends on how the old system stored them. From Pipedrive, Smart Transfer syncs email activities but not logged emails. Once the reps connect their inboxes to HubSpot, new emails are logged automatically from that day.

How long should we keep the old CRM? Keep it read-only until the reps have gone through their deals in HubSpot and one full month of reporting adds up. Check it against the notice period in your contract, so you don't pay for another year. Do a full export before your access ends.

Do we have to clean the data before we migrate to HubSpot? Yes. Duplicates and empty fields don't improve by changing system, and merges in HubSpot can't be undone. Merge duplicate companies first and decide which fields to bring.

Can we run the old CRM and HubSpot side by side for a while? Avoid it. With two systems the reps can write in, nobody knows where the latest information is. Set a date, make the old system read-only and keep it as an archive.

About the author

Viktor Olsson, founder and RevOps consultant

Viktor has worked with HubSpot for six years, with teams from 3 people to organisations with 30 sales reps across the Nordics. He also works in RevOps at an international SaaS company.

LinkedIn →

Want to get your sales and CRM in order?

The first call with Viktor takes 30 minutes and is free. We'll go through how you work today and what would make the biggest difference.

Contact us