---
title: "Marketing automation to HubSpot: Mailchimp, Pardot, Marketo"
description: "Move contacts, consent, lists, templates and engagement history from Mailchimp, ActiveCampaign, Account Engagement (Pardot), Marketo or Eloqua into HubSpot."
url: "https://flitstack.ai/guides/marketing-automation-to-hubspot"
---

# How do I move from Mailchimp, ActiveCampaign, Pardot, Marketo or Eloqua to HubSpot?

Short answer

Move contacts and consent first, then lists, templates and engagement history, then rebuild automation. HubSpot Smart Transfer covers Mailchimp, ActiveCampaign, Pardot and Marketo contacts, templates and lists, but not Eloqua or past campaign activity, and workflows never move as data. FlitStack AI migrates contacts with opt-out status and engagement history, and rebuilds journeys in HubSpot.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Have it done for you ](https://flitstack.ai/contact) [Back to the hub →](https://flitstack.ai/migrations/crm/hubspot)

******What we handle 5

- Contacts and custom fields
- Unsubscribes and consent
- Marketing contact status
- Lists, segments and tags
- Email templates

## What the native tool does, and where it stops

| Task                                    | Native tool                                                                                                                                  | With FlitStack AI                                                                                            |
| --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| Contacts and custom fields              | Smart Transfer for Mailchimp, ActiveCampaign, Pardot and Marketo; CSV import for anything, including Eloqua.                                 | Extracts from each platform's API, deduplicates by email across lists and maps custom fields.                |
| Unsubscribes and consent                | Opt-out list import sets Unsubscribed from all email; per-subscription-type opt-outs are set in bulk from the contacts index or by workflow. | Carries subscription status per contact and maps it to HubSpot subscription types before any email can send. |
| Marketing contact status                | Imported contacts are non-marketing by default; a single-file import can set them as marketing.                                              | Sets marketing status from rules you agree, so billing tiers aren't inflated by unengaged contacts.          |
| Lists, segments and tags                | Smart Transfer moves lists once (no ongoing update); tags become a custom contact property for some sources.                                 | Maps tags and segment membership to properties and lists you can rebuild as active lists.                    |
| Email templates                         | Smart Transfer moves templates for Mailchimp, ActiveCampaign, Pardot and Marketo.                                                            | Templates are rebuilt as part of the implementation service where design work is needed.                     |
| Past opens, clicks and campaign history | Not listed for Smart Transfer. Exports carry it as CSV reports.                                                                              | Migrates engagement history as contact properties so segmentation and scoring still work.                    |
| Automations, journeys, scoring          | Never migrate as data; rebuild in HubSpot workflows.                                                                                         | The HubSpot implementation service rebuilds workflows, lead scoring and lifecycle rules.                     |

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?

1. **Inventory consent first.** Export every unsubscribe, bounce, cleaned and suppression list from the source, with dates if available.
2. **Set up HubSpot subscription types** to match the source’s consent categories.
3. **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.
4. **Deduplicate across lists.** Mailchimp audiences, Pardot lists and Marketo partitions can hold the same person more than once. Decide which record wins.
5. **Create properties** for custom fields, tags, last engagement date and the source’s lead score.
6. **Import or transfer contacts,** choosing marketing status deliberately. Imported contacts are non-marketing by default; marketing contacts count toward your billable tier.
7. **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.
8. **Rebuild lists** as active lists based on those properties, not as static copies.
9. **Rebuild automation and scoring** as HubSpot workflows, then test with internal contacts before switching on.
10. **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](https://flitstack.ai/guides/hubspot-salesforce-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](https://flitstack.ai/services/hubspot-implementation) rebuilds workflows, lead scoring and lifecycle rules.

See [Mailchimp to HubSpot](https://flitstack.ai/migrations/crm/mailchimp/to/hubspot), [ActiveCampaign to HubSpot](https://flitstack.ai/migrations/crm/activecampaign/to/hubspot) and [Act-On to HubSpot](https://flitstack.ai/migrations/crm/act-on/to/hubspot), or the [HubSpot migration hub](https://flitstack.ai/migrations/crm/hubspot). For a quote, [book a free scoping call](https://flitstack.ai/contact).

![Aditya Kumar](https://flitstack.ai/images/authors/aditya-kumar.webp)

About the author

[Aditya Kumar](https://flitstack.ai/about/aditya-kumar)

Founder, FlitStack AI

Aditya Kumar is the founder of FlitStack AI and Jetstack AI, both built at Ambrstack. FlitStack AI migrates CRM and business data between platforms; Jetstack AI is the AI platform HubSpot partners and RevOps teams use to audit portals, build implementations and reuse their best setups across portals. He writes about CRM data, migrations, HubSpot architecture and automation from the work of building them.

[More from Aditya](https://flitstack.ai/about/aditya-kumar) [LinkedIn](https://www.linkedin.com/in/aditya-ambrstack/)

On this page

Questions, answered

## A few useful answers.

Can HubSpot Smart Transfer move my Mailchimp data?

Partly. For Mailchimp, HubSpot lists contacts and email templates as supported, with no one-time extras. Campaign reports, opens and clicks aren't listed, so plan to carry engagement history another way.

Does HubSpot Smart Transfer support Eloqua?

No. The 13 supported apps include Account Engagement (Pardot), ActiveCampaign, Mailchimp and Marketo, but not Oracle Eloqua. Eloqua data comes in through exports and the HubSpot importer, or a migration tool.

Will my unsubscribed contacts stay unsubscribed in HubSpot?

Only if you bring the status across. HubSpot's opt-out list import marks addresses as unsubscribed from all email without creating contacts. For contacts you import, map their opt-out status before sending any email from HubSpot.

Do my Marketo or Pardot programs and automations move to HubSpot?

No. Programs, engagement programs, completion actions and automation rules are logic, not data. They have to be redesigned as HubSpot workflows, lists and lead scoring.

## Related

### [Migrate to HubSpot](https://flitstack.ai/migrations/crm/hubspot)

[Read →](https://flitstack.ai/migrations/crm/hubspot)

### [What do HubSpot Smart Transfer and HubSpot's paid migration cover, and what don't they?](https://flitstack.ai/guides/hubspot-smart-transfer)

[Read →](https://flitstack.ai/guides/hubspot-smart-transfer)

### [What does the HubSpot importer keep, and what does it drop?](https://flitstack.ai/guides/hubspot-import)

[Read →](https://flitstack.ai/guides/hubspot-import)

### [Mailchimp to HubSpot migration](https://flitstack.ai/migrations/crm/mailchimp/to/hubspot)

[Read →](https://flitstack.ai/migrations/crm/mailchimp/to/hubspot)

### [ActiveCampaign to HubSpot migration](https://flitstack.ai/migrations/crm/activecampaign/to/hubspot)

[Read →](https://flitstack.ai/migrations/crm/activecampaign/to/hubspot)

### [HubSpot implementation and data migration](https://flitstack.ai/services/hubspot-implementation)

[Read →](https://flitstack.ai/services/hubspot-implementation)

## Sources

1. [HubSpot KB: Supported apps for HubSpot Smart Transfer](https://knowledge.hubspot.com/integrations/supported-apps-for-hubspot-smart-transfer)
2. [HubSpot KB: Set contacts as marketing](https://knowledge.hubspot.com/records/set-contacts-as-marketing)
3. [HubSpot KB: Import an opt-out list](https://knowledge.hubspot.com/contacts/import-an-opt-out-list)
4. [Mailchimp: Export and back up account data](https://mailchimp.com/help/export-and-back-up-account-data/)
5. [Account Engagement Export API overview](https://developer.salesforce.com/docs/marketing/pardot/guide/export-v5.html)
6. [Oracle Eloqua: Exporting contacts or accounts](https://docs.oracle.com/cloud/latest/marketingcs_gs/OMCAA/Help/DataImportExport/Tasks/ExportingContactsOrAccounts.htm)
7. [Adobe Marketo Engage: Export people to Excel from a list or smart list](https://experienceleague.adobe.com/en/docs/marketo/using/product-docs/core-marketo-concepts/smart-lists-and-static-lists/managing-people-in-smart-lists/export-people-to-excel-from-a-list-or-smart-list)

Get a quote

## Rather have it done for you?

FlitStack AI maps, validates and migrates your data, sets up the process in the new system, and keeps a one-click rollback.

[Get a quote](https://flitstack.ai/contact)
