why teams leave HubSpot.
- →HubSpot migrations need an explicit boundary around what the API exposes.
- →Teams want a dry-run report before rebuilding subscribers, lists, segments, custom fields.
- →Subscription preference mapping may require portal-specific rules
what mailexodus pulls from HubSpot.
can migrate
- +subscribers
- +lists
- +segments
- +custom fields
- +suppressions
- +campaigns
needs review
- ?Subscription preference mapping may require portal-specific rules
cannot migrate
- xtags
- xtemplates
- xautomations
- xsender reputation and domain warmup
- xhistorical analytics, revenue attribution, and aggregate reporting
- xcontacts already mid-flight inside active automations
- xA/B test results and provider-specific experiment history
- xprovider-native design blocks, product widgets, coupons, and private assets that are not exposed by API
source adapter
// the playbookAutomated adapter
Contacts map to subscribers. Static lists map to lists; active lists map to segments. Properties map to custom attributes. Marketing emails map to campaigns
Subscription preference mapping may require portal-specific rules
how an agent migrates HubSpot → Sequenzy.
This is exactly what mailexodus hands your agent: authenticate, then for each object type — read it from HubSpot, map it to the portable schema, write it to the destination. mailexodus never writes; your agent does, with this report in hand.
01 · authenticate
Paste a HubSpot private app access token with read scopes for CRM contacts, lists, marketing email, and subscription preferences
01subscribersmigrates
readGET /crm/v3/objects/contacts (Read subscribers from HubSpot.)
mapContacts map to subscribers. Static lists map to lists; active lists map to segments. Properties map to custom attributes. Marketing emails map to campaigns mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST add_subscriber (Write or stage subscribers in Sequenzy.) PATCH update_subscriber (Write or stage subscribers in Sequenzy.)
02listsmigrates
readGET /crm/v3/lists (Read lists from HubSpot.)
mapContacts map to subscribers. Static lists map to lists; active lists map to segments. Properties map to custom attributes. Marketing emails map to campaigns mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_list (Write or stage lists in Sequenzy.) POST add_subscribers_to_list (Write or stage lists in Sequenzy.)
03segmentsmigrates
readGET /crm/v3/lists?listType=dynamic (Read segments from HubSpot.)
mapContacts map to subscribers. Static lists map to lists; active lists map to segments. Properties map to custom attributes. Marketing emails map to campaigns mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_segment (Write or stage segments in Sequenzy.)
04custom fieldsmigrates
readGET /crm/v3/properties/contacts (Read custom fields from HubSpot.)
mapContacts map to subscribers. Static lists map to lists; active lists map to segments. Properties map to custom attributes. Marketing emails map to campaigns mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePATCH update_subscriber.customAttributes (Write or stage custom fields in Sequenzy.)
05suppressionsmigrates
readGET /communication-preferences/v3/status/email/{emailAddress} (Read suppressions from HubSpot.)
mapContacts map to subscribers. Static lists map to lists; active lists map to segments. Properties map to custom attributes. Marketing emails map to campaigns mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePATCH update_subscriber.status (Write or stage suppressions in Sequenzy.)
06campaignsmigrates
readGET /marketing/v3/emails (Read campaigns from HubSpot.)
mapContacts map to subscribers. Static lists map to lists; active lists map to segments. Properties map to custom attributes. Marketing emails map to campaigns mailexodus renders normalized provider data into destination subscribers, lists, segments, campaigns, sequences, and review notes.
writePOST create_campaign (Write or stage campaigns in Sequenzy.)
stays behind
- tags
- templates
- automations
- sender reputation and domain warmup
- historical analytics, revenue attribution, and aggregate reporting
- contacts already mid-flight inside active automations
guardrails
- Sender reputation is earned at the destination — set up SPF/DKIM/DMARC and a warmup ramp; it does not transfer.
- Keep the source platform active until authentication, warmup, and in-flight automations have finished.
- Honor suppressions before the first send.
- After writing, verify counts per object type against the source before switching live sends.
guide your agent, or follow it yourself.
Pull the full playbook from the skill prompt, CLI, or MCP server, then work the steps. Start by confirming credentials: Paste a HubSpot private app access token with read scopes for CRM contacts, lists, marketing email, and subscription preferences
inspect
provider coverage
npx mailexodus@latest info hubspot
guide
agent playbook
npx mailexodus@latest guide --from hubspot --to sequenzy
agent
Use mailexodus skill: HubSpot → Sequenzy playbook