Moving from Pipedrive and Mailchimp to HubSpot: what to plan for
If you switched off Pipedrive and Mailchimp tomorrow, would you know exactly what you'd lose?
Lots of growing agencies and consultancies end up with sales in Pipedrive, email in Mailchimp and something else again for events. Each tool works on its own, but nothing joins up, and the same person can be a lead in one, a subscriber in another and a ticket buyer in a third.
Moving everything into HubSpot fixes that. But a rushed migration can lose history, scramble your tags and, worst of all, start emailing people who unsubscribed years ago.
In short: decide whether you really want a full move, export everything, map your fields before importing, bring Mailchimp tags across as properties, sync unsubscribes on day one, and run both systems side by side while you check. If you sell event tickets, connect your ticketing platform so bookings land in HubSpot automatically.
We moved a UK design consultancy, which also runs large industry events, from Pipedrive, Mailchimp and Tito into HubSpot. Here's how we go about it, and what to watch for.
Decide between a full move and a hybrid
Before anything else, list the jobs your team actually needs to do: chasing sponsors, selling tickets, nurturing past clients, reporting to the board. Then compare a full move to HubSpot against connecting your existing tools together.
A hybrid costs less upfront, but someone has to keep the connections working. A full move costs more to set up, but leaves you with one place to look. There's no wrong answer, as long as you choose it on purpose.
Map your fields before you import anything
How Pipedrive and Mailchimp usually map to HubSpot
Where it lives now | Where it goes in HubSpot | Worth knowing |
Pipedrive people | Contacts | Keep the Pipedrive ID as a property, so you can re-import updates safely |
Pipedrive organisations | Companies | Check domains, as HubSpot links contacts to companies by email domain |
Pipedrive deals and pipelines | Deals and pipelines | A good moment to simplify stages, not copy them |
Pipedrive notes and activities | Notes and tasks on the record | Bring across what people will genuinely look at |
Mailchimp audiences | Contacts with the right marketing status | Only mark people as marketing contacts if they opted in |
Mailchimp tags | A property or list for each group | Turn the tags you use into segments, drop the rest |
Mailchimp unsubscribes | Unsubscribed from the matching email types | Do this before the first send, not after |
Export everything, then export again
Take a full export early so you can test your imports, then a final export right before you switch the old system off. Anything added in between is easy to miss otherwise.
Handle duplicates carefully
Merging duplicates sounds simple until you find people using a personal email for event tickets and a work email for everything else. Automatic merging can quietly send the wrong emails to the wrong address.
Where someone genuinely uses two addresses for different things, keeping two associated contacts is often safer than one merged record. Expect a few hundred records that need a human to look at them.
Thinking about moving to HubSpot?
Our free HubSpot health check takes a few minutes and shows where your setup is getting in the way, whether you are planning a move or tidying up after one.
Connecting Tito to HubSpot
At the time of writing, there's no ready-made integration between Tito and HubSpot, so we built one with Make. Every booking now lands in HubSpot as it happens:
- The person who bought the tickets and each person attending are recorded separately, because they are often not the same person
- Ticket type, event and order details are saved against the contact and a deal
- Waitlisted and interested people are captured too, not just buyers
- A Slack alert lets the team see bookings coming in without checking HubSpot
That means the team can segment by event, ticket type and attendance in a few clicks, for example everyone who attended two or more events but hasn't booked this year.
Run both systems side by side, then switch off
Give yourself a few weeks of overlap. Rebuild your email templates in HubSpot, move your forms, spot-check a sample of records against the old systems, and only then switch Mailchimp and Pipedrive off. Keep the final exports somewhere safe.
Train the team and write it down
The migration is the easy bit. What makes it stick is people knowing how to use the new setup. Short hands-on sessions, recorded so people can rewatch them, plus simple written processes for marketing, sales and events, go a long way.
Common mistakes we see
- Importing every field and tag, including ones nobody has used in years
- Forgetting to bring unsubscribes across before the first send
- Merging duplicates automatically without checking
- Switching the old tools off before checking the data
- Treating training as optional
A few questions we often get asked
Does HubSpot integrate with Tito?
Not natively, at the time of writing. A tool like Make or Zapier can send bookings into HubSpot as they happen, including ticket type and attendee details.
Can we keep our Pipedrive history?
Yes. Contacts, companies, deals, notes and activities can all be imported. Keeping the original Pipedrive IDs on each record makes it much easier to fix or update things later.
How long does a move like this take?
For a small team with a few thousand contacts, plan for a few months end to end, including running both systems side by side. The import itself is the quick part.
Over to you
So, back to switching everything off tomorrow. Would you know what you'd lose? If you're not sure, it's worth mapping it out before you start.
At Disruptive Thinking, we help agencies, consultancies and event businesses move to HubSpot with their data, tags and history intact, and get their team confident using it.
If you'd like a second pair of eyes on your setup, take our free HubSpot health check or book a free 30-minute consultation. No obligation, just a sensible conversation about what your business actually needs.