Skip to main content
Use HubSpot when your team wants Migma to prepare the email, then finish review, list selection, automation, or send inside HubSpot.

​
What you can do

Existing OAuth connection

Existing HubSpot connections use OAuth. New HubSpot connections are not available.

Export reviewed email

Send HubSpot-ready HTML from Publish after reviewing the email in Migma.

Preserve HubL

Keep HubSpot personalization syntax in the exported email.

Keep a Migma record

External campaign handoff is recorded in Migma when campaigns are exported or scheduled.
HubSpot export and contact import work for existing connections. New HubSpot connections are not available.

​
Export to HubSpot

1

Review the email in Migma

Check content, links, mobile rendering, and preflight before export.
2

Open Publish

Choose HubSpot from the export destinations.
3

Create the draft

Migma prepares HubSpot-compatible HTML and opens the HubSpot handoff when export succeeds.
4

Finish in HubSpot

Review the draft, choose final audience or automation settings, then send from HubSpot.

​
Personalization

Migma preserves HubSpot syntax that you include in the email. Use HubL or contact tokens intentionally, and preview them with HubSpot data before sending.

​
Import contacts from HubSpot

Bring a HubSpot contact list into Migma without exporting a CSV. Imports read from your connected HubSpot account and run in the background.
1

Start from Contacts

In Audience, click Add Contact then Import from integration and choose HubSpot. An existing HubSpot connection is required.
2

Choose a contact list

Pick the HubSpot list you want to import. Static lists appear as lists and smart lists appear as segments.
3

Confirm consent behavior

Migma shows which contacts can receive marketing email before the import starts. HubSpot imports are conservative by design, as explained below.
4

Start the import

The import runs as a background job. Watch progress in the dialog, or check Import History for the final counts.
HubSpot is a CRM, and being on a CRM list is not the same as having permission to receive marketing email. Migma treats HubSpot imports conservatively:
  • Contacts import as subscribed only when their HubSpot marketing email subscription data shows an explicit opt-in.
  • Contacts who opted out of marketing email import as unsubscribed, for record keeping only.
  • Everything else, including plain list membership, imports as non-sendable.
There is no manual override. If Migma cannot verify marketing permission from HubSpot data, the imported contacts stay non-sendable even when the selected list looks like a marketing audience. Existing Migma contacts that unsubscribed or bounced are never resubscribed by an import.

​
Source tag and snapshot segment

Every import creates a source tag named after the list, such as Newsletter Subscribers, and a snapshot segment that targets it. Importing the same list again reuses the same tag and segment, and each import still gets its own Import History record showing the provider, account, source, consent mode, and how many contacts were imported, updated, kept non-sendable, skipped, or failed.
Imports are one-time snapshots. Migma copies the selected list at import time and does not keep syncing it. Run another import when you want fresh data.
If the connected account cannot read contact lists, the HubSpot row offers Reconnect. After reconnecting, Migma returns you to the same import flow, and CSV or paste import remains available as a fallback.

Export Options

Compare platform export and file export.

Platform Integrations

See how HubSpot differs from sending providers.
Last modified on September 1, 2026