Moving marketing automation into HubSpot is two projects that look like one. The data (contacts, consent, lists, engagement history) can be migrated. The logic (journeys, programs, scoring, completion actions) can’t; it has to be rebuilt. Teams that treat it as one job usually move the contacts and lose the consent records, or move everything and email people who unsubscribed years ago. This guide covers the order of work and what each source platform lets you take out.
What moves from a marketing automation platform to HubSpot?
| Data | Moves as data? | How |
|---|---|---|
| Contacts and custom fields | Yes | Smart Transfer, import or migration tool |
| Unsubscribes and consent | Yes, but must be mapped | Opt-out import or per-contact status |
| Lists, segments, tags | Partly | Static lists once; tags as properties; rebuild active lists |
| Email templates | Partly | Smart Transfer for four sources; otherwise rebuild |
| Engagement history (opens, clicks, form fills) | Not into the HubSpot timeline | Carry as contact properties |
| Automations, programs, journeys | No | Rebuild as HubSpot workflows |
| Lead scores | Value yes, model no | Carry last score; rebuild the scoring model |
| Landing pages and forms | No | Rebuild in HubSpot |
What can I take out of each platform?
Mailchimp. The account export produces a zip with audiences (separate files for subscribed, unsubscribed, cleaned and transactional contacts), a CSV of regular campaigns with their HTML and text content, reports including per-contact activity, templates and files. You can run one account export per 24 hours. Landing pages, ads and website content aren’t exportable. Smart Transfer moves contacts and email templates.
ActiveCampaign. Smart Transfer is the broadest here: contacts, deals, accounts as companies, email templates, segments, users and groups as teams, with lists, notes and tags (as a custom contact property) as one-time transfers.
Account Engagement (Pardot). Smart Transfer moves prospects as contacts, email templates and users, plus lists and tags once. For a full extract, the Export API produces CSV files from a query; export data expires after 7 days.
Marketo Engage. Smart Transfer moves contacts, email templates and users, plus lists once. People can be exported from a list or smart list to a spreadsheet in Marketing Activities. Programs, smart campaigns and scoring stay behind.
Oracle Eloqua. Not supported by Smart Transfer. Segment contacts can be exported to a file, and the data export tool exports contacts, accounts or activities, one-time or scheduled, with files hosted for 14 days. Activity exports need an administrator to set up activity capture first, and only capture activity after that point.
How do I migrate marketing data into HubSpot?
- Inventory consent first. Export every unsubscribe, bounce, cleaned and suppression list from the source, with dates if available.
- Set up HubSpot subscription types to match the source’s consent categories.
- Import opt-outs before contacts. HubSpot’s opt-out list import sets “Unsubscribed from all email” for those addresses without creating contacts or adding to your billable count.
- Deduplicate across lists. Mailchimp audiences, Pardot lists and Marketo partitions can hold the same person more than once. Decide which record wins.
- Create properties for custom fields, tags, last engagement date and the source’s lead score.
- Import or transfer contacts, choosing marketing status deliberately. Imported contacts are non-marketing by default; marketing contacts count toward your billable tier.
- Load engagement history as properties: last open, last click, total sends, last form fill. HubSpot’s timeline shows emails sent from HubSpot, so past campaign activity is best kept as data you can filter on.
- Rebuild lists as active lists based on those properties, not as static copies.
- Rebuild automation and scoring as HubSpot workflows, then test with internal contacts before switching on.
- Warm up sending. Start with your most engaged contacts.
How do I keep sending email during the switch?
Most teams can’t stop marketing for the length of a migration. A safe overlap looks like this:
- Pick a cutover date for new sign-ups. From that day, forms post to HubSpot, and the old platform only sends what’s already scheduled.
- Sync unsubscribes both ways until the old platform is off. Anyone who opts out in either system must be suppressed in both. This is the step most often missed.
- Run a final delta of contacts, consent changes and engagement after the last send from the old platform.
- Pause the old automations before HubSpot’s go live, so no one gets two welcome series.
What should I check before the first HubSpot send?
- Opt-out and bounced addresses from every source list are unsubscribed in HubSpot.
- Subscription types match the consent categories people agreed to.
- Marketing contact status is set on purpose, not by default.
- A test send to internal addresses renders correctly and the unsubscribe link works.
- Workflows are tested on internal contacts and switched on one at a time.
What about the CRM side of these platforms?
ActiveCampaign has deals and accounts. Pardot and Marketo usually sit next to Salesforce. If the CRM is also moving to HubSpot, migrate it first so marketing contacts land on the right companies and deals. If Salesforce stays, read integration vs migration before you connect anything.
How long should both platforms run side by side?
Long enough to finish one full cycle of your regular sends and to confirm that unsubscribes, bounces and form submissions are all landing in HubSpot. Shorter overlaps risk missing a consent change; longer ones mean paying for two platforms and keeping two sets of lists in step.
Where do native routes fall short?
- Eloqua isn’t on Smart Transfer’s list.
- Engagement history isn’t listed for any of the four supported marketing sources.
- One-time list transfers don’t stay up to date, so lists drift if the old platform keeps running.
- Consent is easy to lose in a CSV round-trip, and the cost of getting it wrong is emailing people who opted out.
- Logic never moves. Every program, journey and scoring rule needs redesign.
When to bring in FlitStack AI
FlitStack AI is a data-migration platform sold as software plus a done-for-you service. It extracts contacts from the source’s API, deduplicates by email, maps custom fields, tags and subscription status, and migrates engagement history as contact properties so segmentation keeps working. Every record is validated and every run can be rolled back. The HubSpot implementation service rebuilds workflows, lead scoring and lifecycle rules.
See Mailchimp to HubSpot, ActiveCampaign to HubSpot and Act-On to HubSpot, or the HubSpot migration hub. For a quote, book a free scoping call.