Audiences
Each Mailchimp audience comes across as a YionStack marketing list. Audience-level merge fields map to contact custom fields so the historical personalisation tokens continue to work.
Move from Mailchimp
Your audience, campaigns and consent — close to the CRM they belong to.
Export your Mailchimp audiences and campaign reports, upload them to YionStack, and the AI-assisted Import surface maps subscribers, tags and consent records into the marketing module — alongside the CRM that already shares the same contact record. See every supported source →
File-based — you upload an export from your old system, we map it. No connection to your old account.
At a glance
marketing- From
- Mailchimp
- How
- Upload an export
- Records
- 7 types come across
- Steps
- 3-step migration
- Stays put
- 5 items intentionally
- Residency
- UK (europe-west2)
What lands in your business
The records you depend on, in their right places.
Subscribers
Subscribed, unsubscribed, cleaned and pending contacts all come across with status preserved. Duplicate detection runs on email so the same person across multiple audiences stays as one CRM contact.
Tags and segments
Mailchimp tags map to YionStack contact tags one-to-one. Saved segments (the live filters) come across as YionStack saved segments so the recipient lists you used continue to resolve correctly.
GDPR consent records
Per-contact GDPR consent, opt-in source, opt-in date, IP at opt-in and the marketing-permission categories all come across — the ICO-grade opt-in audit trail is preserved on every contact.
Campaign send history
Past campaign sends, opens, clicks and bounces come across as read-only history attached to each contact. New campaigns are composed and sent from the YionStack marketing module.
Suppression and unsubscribe lists
Every unsubscribed and complaint-listed address comes across as a hard suppression on the YionStack marketing module so the same person never receives an unwanted email.
Email templates (as reference)
Existing template HTML can be archived as design references; new sends are composed in the YionStack marketing module’s template editor so they share design tokens with the website.
How it works
Three steps. Reversible at any point.
- 1
Export from Mailchimp
From Mailchimp, use Audience → All contacts → Export Audience for each audience. Optionally export campaign reports from Reports → Export. The Import surface reads the column headers and routes each file to the right entity.
- 2
Review the mapping
YionStack’s AI-assisted mapper reads the headers (email, FNAME, LNAME, plus your merge fields) and suggests where each one lands. You approve or adjust before any data is written.
- 3
Run the import
The job runs in the migration dashboard. Suppression and unsubscribe records apply immediately so no campaign sent from YionStack ever reaches a contact who has opted out.
What stays where it is
We are honest about scope.
A migration is not the same as a clone. The records below are intentionally out of scope — either because they belong with the system that produced them, or because their meaning changes once they live inside an operating system instead of a point-tool. You can still reference the originals while you run YionStack alongside.
- —Live automation journeys — re-authored inside the YionStack marketing module so triggers can fire from CRM, accounting and booking events too, not only marketing engagement.
- —Signup forms and popups — re-built using the YionStack Builder so they live on the same website and share one design system.
- —Mailchimp Transactional (Mandrill) — transactional sends move to YionStack’s built-in transactional layer via the existing Postmark integration.
- —Subdomain warming and IP reputation — YionStack uses Postmark for marketing sends with established UK-region IP reputation, so warm-up is handled on our side.
- —Mailchimp websites and landing pages — re-built with the YionStack Builder so the public site, the CRM, the books and the AI all share one operating environment.
Common questions
Straight answers.
Will my opt-in audit trail be preserved?
Yes. Per-contact opt-in source, opt-in date, IP address at opt-in and marketing-permission categories all come across on every imported subscriber so the ICO-grade audit trail is intact. Future opt-ins captured by YionStack signup forms continue the same audit.
What about my Mailchimp signup forms?
Forms re-build using the YionStack Builder’s form blocks. The new forms drop directly into your website pages, create contacts in the unified CRM and apply the same tags and audience assignments.
Do unsubscribes carry across?
Yes — unsubscribed contacts come across with the unsubscribe date, the campaign that triggered it (if known) and the reason. They land as hard-suppressed in YionStack so no future send can reach them by mistake.
What about my Mailchimp templates and design tokens?
Existing template HTML can be archived as reference. New templates are composed inside the YionStack marketing module using its template editor, which shares design tokens with the YionStack website so brand colours and typography stay consistent across email and web.
Can I still use the same "From" email address?
Yes. The sending domain re-authenticates inside YionStack (SPF, DKIM, DMARC) through the same DNS records you set up for Mailchimp — most of the records stay; only the verification host changes. Postmark, YionStack’s send infrastructure, supplies the new authentication values.
Ready to run your business smarter?
Join thousands of UK businesses already running on YionStack.
- No credit card
- 14-day free trial
- Cancel anytime