Migrate from HubSpot to Lea CRM
Leaving HubSpot is daunting for one simple reason: everything has been piling up in there for years. Lea connects to your portal and brings back your sales pipeline, your companies, your contacts and your history of exchanges, without going through an integrator.
Included from the Starter plan. The import is started from an Owner or Admin account.
How it works
You paste your token
Lea identifies your HubSpot portal and checks the four read permissions. If one is missing, you know before starting, with its exact name.
Lea tells you what it will do
The screen lists what will be brought over and what will not, before anything runs. You confirm with full knowledge.
The import runs in the background
You can close the page. Progress is shown step by step, with counters per object type.
You get back to work
Your deal pipelines are recreated with their stages, your deals sit at the right stage, and your exchanges are attached to the right records.
Where to find your HubSpot token
HubSpot asks you to create a read-only private app. It takes longer to describe than to do, and it guarantees that Lea cannot change anything on your side.
HubSpot ↗In HubSpot, open Settings, then Development and Legacy apps.
Create a read-only private app.
Tick the four required read permissions: contacts, companies, deals and owners. Add the email read permission if you want to bring your emails over.
In the Auth tab, copy the token starting with “pat-”, then paste it into Lea.
Lea checks the four required permissions before starting the import and tells you exactly which ones are missing. Without the email read permission, the import still runs, just without the emails, and Lea tells you so. Your token is encrypted with AES-256-GCM, used for the duration of the import, then erased.
What Lea brings over from HubSpot
The sales pipeline and its history, not just a contact database.
Deal pipelines and stages
Your deal pipelines are recreated with their stages in the right order.
Companies
Name, website, phone, address, city, region and country. HubSpot exposes more company fields than most CRMs, and Lea brings them over.
Contacts
Name, email and phone, attached to their company.
Deals
Amount, stage, won or lost status, creation and close dates.
Notes
Brought over as text, attached to their contact or their deal.
Calls, meetings and tasks
Calls and meetings become activities. HubSpot tasks become Lea tasks.
Custom fields
The custom properties of your deals and contacts are recreated in Lea and filled in on the imported records. HubSpot's native, calculated or hidden properties are left out.
Emails
Each email arrives with its subject, its text, the sender, the recipient and the date, attached to its contact or deal. This requires the email read permission.
What will not be brought over
Better to know now than later. Lea shows you this same list inside the app, before you start the import.
- Custom properties on companies, as well as calculated or hidden properties.
- Files and attachments.
- Emails not attached to any imported contact or deal.
- The currency of amounts: they are brought over as they are.
- Tickets and ticket pipelines.
- Products, quotes and invoice line items.
- Sequences, workflows and marketing automation.
- The change history.
- User accounts and their permissions: no account is created.
- Archived records.
- Anything beyond the first association of a given type: a contact linked to three companies arrives linked to the first one.
If any of these matters to you, write to us before migrating. We will tell you honestly whether it can be handled another way, including when the answer is no.
You can run the import again without breaking anything
Lea remembers what it has already imported from HubSpot. A second run only adds what is new: it does not create duplicates. One caveat though, this is not a sync: a record edited in HubSpot after the first import will not be updated in Lea.
Who gets which deal
Lea matches HubSpot owners to your users by email address. Create your reps' Lea accounts with the same addresses before importing, otherwise their deals will be assigned to whoever runs the import. The screen tells you how many users were recognised.
Still weighing up the two?
Our comparison sets out what Lea does that HubSpot does not, with public pricing on both sides.
Frequently asked questions
How do I migrate from HubSpot to Lea CRM?
Create a read-only private app in HubSpot (Settings › Development › Legacy apps), tick the four required read permissions, plus the email one if you want to bring your emails over, copy the “pat-” token and paste it into Lea under Settings › Integrations › Import from another CRM. Your pipelines, companies, contacts, deals, notes, activities and custom fields are brought over automatically.
Does migrating from HubSpot cost anything?
No. The import is included from the Starter plan, with no surcharge and no integrator.
Are my HubSpot custom properties brought over?
Yes, for deals and contacts: Lea recreates those properties and fills them in on the imported records. Custom properties on companies, and calculated or hidden properties, are not brought over. Lea shows these limitations inside the app before you start the import.
Are my HubSpot emails imported?
Yes, if your private app has the email read permission. Each email arrives with its subject, its text, the sender, the recipient and the date, attached to its contact or deal. Without that permission, the step is simply skipped, and Lea tells you so both before and after the import.
Can Lea modify my HubSpot data?
No. The permissions requested are all read-only, emails included. Lea cannot create, change or delete anything in your HubSpot portal.
What happens if I run the import twice?
Lea recognises what has already been imported and only adds what is new, without creating duplicates. Records already imported are not updated: this is a migration, not a continuous sync.