Guides
Import from HubSpot, Pipedrive, Mailchimp or Brevo
Published November 10, 2026 · 8 min read
Switching tools feels like a chore for one reason: the data. Years of contacts, companies, deals and notes live in your current CRM or email tool, and nobody wants to export ten CSV files, match columns and then find out half the contacts were duplicated.
If you are coming from HubSpot, Pipedrive, Mailchimp or Brevo, there is a shorter route: a direct import using the source tool's API key. This guide covers what you can bring from each one, how to get the key, what to clean up first and what you will rebuild by hand.
Key takeaways
- With an API key you can bring contacts, companies, pipelines, deals and notes from HubSpot and Pipedrive, and contacts with their lists and subscription status from Mailchimp and Brevo.
- Volume is not the only thing that matters. Keeping unsubscribes is: anyone who opted out in the old tool must stay opted out.
- A good import never duplicates records and can be run again safely.
- Automations, templates and journeys don't migrate. You rebuild them, which is a good chance to simplify.
- Clean up before you import. What goes in messy stays messy.
What data can you bring from each tool?
| Source | What is imported | Which key you need |
|---|---|---|
| HubSpot | Owners, companies, contacts, pipelines and stages, deals and notes | Access token of a private app |
| Pipedrive | Users, organizations, people, pipelines and stages, deals, activities and notes | Personal API token |
| Mailchimp | Contacts from your audiences, tags and subscription status | API key |
| Brevo | Contacts, lists and subscription status | API key |
HubSpot and Pipedrive are CRMs, so your whole sales process comes from them. Mailchimp and Brevo are email marketing tools: what you mainly bring from them is contacts and, crucially, who is subscribed and who is not.
How do I get the API key?
Each vendor moves its menus around over time, so treat these steps as directions rather than exact paths:
- HubSpot. Create a private app from the integrations settings (newer accounts may show it under the development section). Give it read access to contacts, companies, deals and owners, and copy its access token.
- Pipedrive. Open your personal preferences, go to the API section and copy your personal token.
- Mailchimp. In your account, find the API keys section and create a new key.
- Brevo. In the SMTP and API section, generate an API key.
Use a read-only key where the tool allows it. When the migration is done, revoke it in the source tool: you won't need it again.
Checklist before you import
An hour spent here saves weeks of cleanup later:
- Delete what you don't need in the source: test contacts, obvious duplicates, empty companies.
- Line up the owners. If records have an assigned salesperson, invite your team first with the same email they use in the old tool. Each record then arrives with its owner.
- Review the pipelines. Remove stages you no longer use. Stages are imported as they are.
- Check subscription status in Mailchimp or Brevo. Unsubscribes and bounces are the most valuable information you will bring.
- Check your plan's contact limit. If you have more contacts than the limit, decide whether to clean up first or upgrade.
- Tell the team not to create records in both tools while the migration is running.
For a deeper cleanup, the CRM data cleanup guide has a full procedure.
What happens to unsubscribes and consent?
This is the step people overlook and the one that causes the most trouble. If someone unsubscribed in Mailchimp and shows up as subscribed in your new tool, your next send will reach them. That is both a legal issue and a deliverability one.
The rules a serious import should follow:
- An unsubscribe or a bounce in the source always wins.
- A contact already unsubscribed in the destination is never re-subscribed.
- Consent is only carried over for people who were subscribed and have no contrary history in the destination.
What happens if I import twice?
A good import is idempotent: running it again duplicates nothing. Records are recognised by their ID in the source tool and, failing that, by email (contacts) or by domain and name (companies). A second run only fills empty fields and never overwrites what your team edited since.
That allows a simple approach: import once as a test, review, fix the source if needed and import again.
What doesn't migrate?
No API import brings over the logic of your old tool. You will need to rebuild:
- Automations and workflows from HubSpot or Pipedrive.
- Journeys and sequences from Mailchimp or Brevo.
- Email templates and forms.
- Reports and dashboards.
- Integrations with other tools.
Don't see it as a loss. Most accounts pile up automations nobody remembers the reason for. Rebuild only the ones that still earn their place.
How to check the import went well
- Compare the number of contacts, companies and deals with the source.
- Open five random contacts and check they have their company, notes and owner.
- Look up a contact you know unsubscribed and confirm they still are.
- Review the pipelines: stages, open, won and lost deals.
- Send a test to a small segment before any campaign.
The general guide to migrating to a new CRM also covers spreadsheets and other sources.
Frequently asked questions
Is my API key stored?
In Flowgration, no. The key is used only for that import and is never saved, logged or shown again. Still, revoke it in the source tool when you are done.
Are emails sent or journeys started during the import?
No. Records are written straight into the CRM: nothing is sent and no journey starts.
What happens to records owned by someone who is not on my team?
They are assigned to the person who runs the import. The final report lists the owners that could not be matched.
What if the key can't read something?
Contacts are required, but if the key lacks permission for companies, deals, notes or activities, that part is skipped and the report says so. Add the permission and run the import again: nothing is duplicated.
Can I bring data from other tools?
Flowgration also has a separate importer for Holded, and you can always upload a CSV file for anything else.
How Flowgration does it
In Flowgration the import lives in the contact list and in the getting-started checklist, behind the "Import from another tool" button. You pick HubSpot, Pipedrive, Mailchimp or Brevo, paste the key, and the import keeps running in the background even if you close the window. You can see which phase it is in (companies, contacts, pipelines, deals, notes, activities) and cancel it.
When it finishes you get a report: records created, already there, skipped and failed; how many unsubscribes and bounces were respected; which owners were matched to your team by email. If your plan hits its contact limit, the rest is left out and the report explains why; you can upgrade and run it again without duplicates.
What it doesn't do: it doesn't migrate automations, templates, forms or reports, and only one import can run at a time. If you are coming from HubSpot or Pipedrive, compare first on the HubSpot alternative and Pipedrive alternative pages. There is a free plan and a 14-day trial with no card on the pricing page.
Build your WooCommerce CRM in 60 seconds
Flowgration turns your store's orders into a living CRM and runs email, SMS and WhatsApp on autopilot. Free up to 500 contacts.
Start free