Switching from Mailchimp to a venue marketing platform: lists, templates and consent

{{asset:header_image.png}}

You can switch from Mailchimp to a venue marketing platform such as Purple Engage in five phases without a flag day, provided every contact keeps its GDPR consent record. Import consented contacts with their timestamps and load everyone else as suppression. Run both senders side by side, then let guest WiFi sign-ins grow the list.

When you finish, one platform holds your list and sends every campaign. Each guest WiFi sign-in adds a consented, first-party contact with a visit history. The template rebuild is not the hard part. The real risk is losing proof of consent, or emailing a diner who unsubscribed in Mailchimp three years ago. This guide sets out the five phases, the exit test for each, the rollback and the proof that the move worked.

What changes when you leave Mailchimp, and what stays the same?

Mailchimp sends campaigns well, but it does not build your list. Every contact in it arrived through a form, an integration or an import that someone set up and now maintains. A venue marketing platform works the other way round. The guest signs in to your WiFi and makes a conscious-choice opt-in. They then join your audience with a visit history attached.

That changes four things. Most of your marketing habits stay as they are.

Area	Mailchimp today	Purple Engage after the move
How the list grows	Signup forms, imports and integrations you maintain	Guest WiFi sign-in with an opt-in at each venue
What you know about a contact	Email activity plus any fields you import	Email activity plus visit frequency, recency and venue
What starts an automation	Signup date, tags or email activity	A first visit, a return visit or a period without a visit
Where consent comes from	The form or import that added the contact	The WiFi sign-in, with the time and venue
What stays the same	Your brand, offers and sending calendar	Your brand, offers and sending calendar

Your accountability does not change. Under GDPR you remain the controller, and the software does not take that on for you. The duty to show how each contact consented stays with you. If you are also rethinking what to send once the move is done, start with venue email campaigns: what to send and when.

What has to be true before phase 1 starts?

Do not export anything until these six conditions hold.

• One owner. A single named person signs off each phase exit test. On a multi-site estate this is usually the CRM manager, not each site manager.
• A lawful basis for every audience. Know whether each Mailchimp audience relies on consent or the soft opt-in. Under PECR, marketing email to individuals needs consent unless the soft opt-in applies. The ICO's direct marketing guidance explains both.
• Guest WiFi live, or a date for it. Engage builds the list from WiFi sign-ins, so each venue needs Purple running on the access points it already has.
• Admin access to Mailchimp. Full exports and audience settings need owner-level rights.
• Someone who can edit DNS. Your sending domain must be authenticated for Engage before the first live send.
• A 10-week send calendar. Mark which campaigns leave from which platform each week, so nothing goes out twice.

{"tone":"warning","title":"The risk that bites","text":"Mailchimp's unsubscribed and cleaned contacts must reach Engage as suppression before the first send. Import only the subscribed file and you will email diners who opted out, which breaches PECR and the trust you built."}

Consent records matter just as much. GDPR Article 7(1) requires you to be able to demonstrate that each person consented. If the source and timestamp do not survive the move, that evidence is gone.

What are the five phases, in order?

Each phase has one owner and one exit test. Do not start the next phase until the test passes. The timeline below assumes a multi-site estate. A single venue can compress it.

{"kind":"timeline","direction":"lr","caption":"A 10-week migration plan from Mailchimp to Purple Engage for a multi-site estate","alt":"Timeline showing five migration phases, from audit and export in weeks 1 to 2 through to cutover and close-out in weeks 9 to 10.","nodes":[{"id":"p1","label":"Phase 1: audit and export","sub":"Map audiences, consent basis and suppression files","tone":"neutral","when":"Weeks 1-2"},{"id":"p2","label":"Phase 2: import and suppress","sub":"Consented contacts in, everyone else blocked","tone":"brand","when":"Weeks 2-3"},{"id":"p3","label":"Phase 3: rebuild templates","sub":"Templates and visit-based automations in Engage","tone":"brand","when":"Weeks 3-5"},{"id":"p4","label":"Phase 4: parallel running","sub":"Both platforms live, split by campaign type","tone":"brand","when":"Weeks 5-8"},{"id":"p5","label":"Phase 5: cutover and close-out","sub":"Mailchimp sends stop, final export archived","tone":"success","when":"Weeks 9-10"}],"edges":[{"from":"p1","to":"p2","label":"Exit test passed"},{"from":"p2","to":"p3","label":"Exit test passed"},{"from":"p3","to":"p4","label":"Exit test passed"},{"from":"p4","to":"p5","label":"Go decision"}]}

{"caption":"Phase plan: scope, owner and exit test for each phase","asOf":"2026-06-10","columns":[{"key":"phase","label":"Phase"},{"key":"scope","label":"Scope"},{"key":"owner","label":"Owner"},{"key":"exit","label":"Exit test"}],"rows":[["Phase 1: audit and export","Every audience, automation and consent field listed; all contact statuses exported","CRM manager","Export counts match the Mailchimp dashboard for every audience"],["Phase 2: import and suppress","Consented contacts imported with source and timestamp; unsubscribed and cleaned loaded as suppression","CRM manager with data protection lead","A test send to a seeded suppressed inbox is blocked"],["Phase 3: rebuild templates and automations","Core templates rebuilt; welcome, post-visit and win-back automations rebuilt on visit data","Marketing manager","Every email passes a seed test on desktop and mobile; each automation fires for a test sign-in"],["Phase 4: parallel running","Automations live in Engage; one-off campaigns split by an agreed calendar","CRM manager","Two weeks with no duplicate sends, no sends to suppressed contacts and complaints at or below baseline"],["Phase 5: cutover and close-out","Mailchimp sends stopped, forms redirected, final export archived","Marketing director","No campaign has left Mailchimp for 30 days and every new contact arrives in Engage"]],"footnote":"Baseline means the complaint and unsubscribe rates of the same campaign types in Mailchimp over the previous quarter.","download":{"filename":"mailchimp-to-engage-phase-plan.csv"}}

Phases 1 to 3: moving your list, consent and templates

Phase 1: audit the Mailchimp account and export it

List every audience in the account. Venue groups often hold more than one, such as one per site or one left over from an old competition. For each audience, record three things: the lawful basis, the signup source and the date range.

Then export. Mailchimp's export function produces separate files for each contact status, including subscribed, unsubscribed and cleaned. Keep all of them. Archive the original files with the export date. If a regulator or a diner asks how a contact consented, those files are your evidence.

Worked scenario: a 12-site restaurant group

Situation. A 12-site group held three Mailchimp audiences totalling 42,000 contacts. One came from a 2019 competition, and nobody could find the consent wording used.

What was done. The audit split contacts into three buckets. 29,000 had a dated opt-in and a known form. 7,000 were unsubscribed or cleaned. 6,000 came from the competition with no consent record. The group imported the 29,000 and loaded the 7,000 as suppression. They left the 6,000 out and did not email them asking for permission. The ICO fined Flybe £70,000 in 2017 for exactly that kind of re-permission campaign.

Outcome. The Engage list started 31% smaller than the Mailchimp headline. Every contact on it had a source and timestamp that the data protection lead could produce on request. The 6,000 can rejoin only one way: by signing in to WiFi at a venue and opting in.

Phase 2: import consented contacts and load suppression

Order matters here. Suppression goes in first, so no import can ever reach an address that opted out.

{"title":"Phase 2: import consented contacts and load suppression","steps":[{"title":"Load suppression first","body":"Combine the unsubscribed and cleaned exports from every audience into one file. Load it into Engage as suppression before any contact import.","check":"The suppression count equals unsubscribed plus cleaned, less duplicates."},{"title":"De-duplicate the subscribed file","body":"Merge subscribed contacts from every audience. Keep the earliest opt-in timestamp and remove any address that also appears in suppression.","check":"One row per email address, and no row matches the suppression file.","variants":[{"label":"One audience","body":"Remove duplicates within the file and check it against the unsubscribed export."},{"label":"One audience per venue","body":"Add a venue column before merging, so each contact keeps the site where they signed up."}]},{"title":"Map the fields","body":"Map email, first name, venue, consent source and opt-in timestamp. Confirm with Purple which fields Engage accepts, and drop any column with no destination.","check":"Every column has a named destination or a written reason it was dropped."},{"title":"Import a test batch","body":"Import 100 rows drawn from different venues and audiences.","check":"Five sampled contacts show the right venue, consent source and timestamp."},{"title":"Import the full file","body":"Import the rest once the test batch passes. File the import with your archived exports and the date.","check":"Imported plus suppressed plus excluded equals the Mailchimp export total."},{"title":"Seed-test suppression","body":"Unsubscribe an inbox you control, add it to suppression, then send a test campaign to an audience that includes it.","check":"The seeded inbox receives nothing."}]}

Phase 3: rebuild templates and automations on visit data

Rebuild your templates in Engage rather than porting HTML. Mailchimp templates use Mailchimp merge tags such as *|FNAME|*. If you move them across as code, they can arrive as literal text in a guest's inbox. Rebuild three to five core templates: newsletter, offer, event and post-visit thank-you.

Rethink the automations rather than copying them. A Mailchimp welcome series starts on signup date. In Engage, automations start on what the guest does at your venue: a first visit, a return visit or no visit for a period you set. Give each Mailchimp automation one of three verdicts: rebuild on visit data, rebuild as it is, or retire.

If you are weighing up flow-based alternatives, see Klaviyo for hospitality: where it fits and where it does not. The exit test for this phase is mechanical. Every email must pass a seed test on desktop and mobile. Every automation must fire for a test WiFi sign-in.

How do Mailchimp and Engage run side by side before cutover?

Phase 4: parallel running with a clear split

One rule governs parallel running: each guest receives each campaign from one platform only. Split by campaign type, not by contact. Splitting contacts across two senders makes suppression unmanageable.

• Automations move first. Switch each one on in Engage and off in Mailchimp on the same day. Two live welcome series will send every new guest two welcome emails.
• One-off campaigns move second. Keep them in Mailchimp for the first two weeks of phase 4, then send them from Engage.
• Forms stop feeding Mailchimp. Redirect or pause every signup form, booking engine link and till integration that writes to Mailchimp. Otherwise new contacts keep arriving in the platform you are leaving.
• Unsubscribes sync both ways every week. Anyone who opts out in either platform goes into suppression in the other within the week.
• Volume ramps. Start Engage sends with your most engaged contacts, then widen. A new sender sending its full volume on day one risks the spam folder.

Worked scenario: a 180-room hotel

Situation. A 180-room hotel had 18,000 Mailchimp contacts, a monthly newsletter and a three-email welcome series.

What was done. In week 5 the hotel moved the welcome series to Engage and triggered it on a guest's first WiFi sign-in. The Mailchimp version was switched off that afternoon. The week 5 newsletter went from Mailchimp and the week 7 newsletter from Engage. Every Monday, the CRM manager synced unsubscribes in both directions.

Outcome. The Monday sync carried 140 Mailchimp unsubscribes into Engage before its first newsletter. The seeded suppressed inbox received nothing. Complaint rates on the Engage newsletter sat at the Mailchimp baseline. The hotel passed its go decision in week 9 with no duplicate sends recorded.

Phase 5: the go or no-go decision and cutover

Run this decision for each venue, not just for the estate as a whole. A venue whose WiFi capture is not yet live can wait without holding up the rest.

{"title":"Cutover go or no-go","start":"q1","nodes":[{"id":"q1","question":"Does every imported contact carry a consent source and timestamp?","help":"Sample 20 contacts across every venue and audience.","options":[{"label":"Yes","to":"q2"},{"label":"No","to":"o1"}]},{"id":"q2","question":"Did the seeded suppressed inbox receive nothing during parallel running?","help":"Use an inbox you control that unsubscribed in Mailchimp.","options":[{"label":"Yes","to":"q3"},{"label":"No","to":"o2"}]},{"id":"q3","question":"Are Engage complaint and unsubscribe rates at or below your Mailchimp baseline?","help":"Compare the last two weeks of parallel sends by campaign type.","options":[{"label":"Yes","to":"q4"},{"label":"No","to":"o3"}]},{"id":"q4","question":"Are WiFi sign-ins at every venue adding opted-in contacts to Engage?","help":"Check each site, not the estate total.","options":[{"label":"Yes, every venue","to":"o4"},{"label":"Some venues","to":"o5"}]},{"id":"o1","outcome":"No-go: fix the import","detail":"Re-map consent fields from the archived export and repeat the phase 2 exit test."},{"id":"o2","outcome":"No-go: fix suppression first","detail":"Reconcile both suppression lists and re-seed before any further send."},{"id":"o3","outcome":"Roll back that campaign type","detail":"Return it to Mailchimp, fix content or volume, then repeat phase 4 for it."},{"id":"o4","outcome":"Go: cut over","detail":"Stop Mailchimp sends and start the 30-day close-out.","link":"[Plan your first Engage campaigns](pillar:)"},{"id":"o5","outcome":"Partial go","detail":"Cut over the venues that pass and hold the rest until their sign-in capture is live."}]}

On a go, stop every Mailchimp send. Pause campaigns rather than deleting them, and keep the account open for 30 days. That window is your rollback route.

How do you roll back if the cutover goes wrong?

Roll back one campaign type at a time, never the whole migration. Guest WiFi capture keeps running whatever you decide, so the Engage list keeps growing while you fix the send.

Roll back when any of these happens:

• A suppressed or seeded address receives an Engage email.
• Complaint or unsubscribe rates rise above your Mailchimp baseline for two sends in a row.
• An automation fires for the wrong venue or the wrong guests.
• Inbox placement drops on your seed accounts.

Then follow this order:

1. Pause the Engage campaign or automation.
2. Copy every Engage unsubscribe since cutover into Mailchimp suppression. Do this before anything sends.
3. Reactivate the paused Mailchimp equivalent.
4. Find the cause and fix it in Engage.
5. Re-enter phase 4 for that campaign type and repeat its exit test.

Step 2 is the one teams skip. Without it, guests who opted out of Engage after cutover will get the Mailchimp send. That is the same breach in reverse.

How do you know the move is finished?

The move is finished when four tests pass and you can show the evidence for each.

1. The numbers reconcile. Imported plus suppressed plus excluded equals the Mailchimp export total. The figures are written down and signed off.
2. Mailchimp is silent. No campaign has left it for 30 days. No form, booking engine or till integration still writes to it.
3. Consent is provable on demand. Pick 10 contacts at random and produce the source and timestamp for each within a working day.
4. The list grows from WiFi. New contacts in Engage come from guest WiFi sign-ins, with an opt-in rate you can report per venue.

Once those pass, change what you report. Measure opt-in rate at sign-in by venue. Compare the repeat visit rate of guests you emailed against guests you did not. Report revenue per send wherever you can match sends to till data. Those three numbers tell your board whether the switch paid off.

{"title":"Mailchimp to Purple Engage migration checklist","groups":[{"heading":"Before phase 1","items":[{"text":"Name one owner for every phase exit test"},{"text":"Record the lawful basis for each Mailchimp audience","why":"PECR requires consent for marketing email unless the soft opt-in applies"},{"text":"Confirm guest WiFi go-live dates for every venue"},{"text":"Confirm who can add DNS records for your sending domain"}]},{"heading":"List and consent","items":[{"text":"Export every audience, all contact statuses"},{"text":"Archive the original exports with the date"},{"text":"Load unsubscribed and cleaned contacts as suppression before any import"},{"text":"Import only contacts with a consent source and timestamp"},{"text":"Reconcile imported, suppressed and excluded totals against Mailchimp"}]},{"heading":"Templates and automations","items":[{"text":"Rebuild core templates without Mailchimp merge tags"},{"text":"Rebuild welcome, post-visit and win-back automations on visit data"},{"text":"Seed-test every email on desktop and mobile"}]},{"heading":"Parallel running","items":[{"text":"Switch off each Mailchimp automation the day its Engage version goes live"},{"text":"Redirect or pause every Mailchimp signup form and integration"},{"text":"Sync unsubscribes both ways every week"},{"text":"Compare complaint and unsubscribe rates with the Mailchimp baseline"}]},{"heading":"Cutover and close-out","items":[{"text":"Pass the go or no-go decision for each venue"},{"text":"Pause Mailchimp campaigns, do not delete them, for 30 days"},{"text":"Take a final Mailchimp export and archive it"},{"text":"Close or downgrade the Mailchimp account after the rollback window"}]}],"download":{"filename":"mailchimp-to-purple-engage-migration-checklist.csv"}}

Which failure modes catch venue teams out?

These failures come up again and again in Mailchimp migrations. Each one maps to a test in the plan above.

• Importing only the subscribed file. Opt-outs then look like fresh contacts. Load suppression first, every time.
• Two live versions of one automation. A guest gets two welcome emails, and some unsubscribe from both platforms. Switch off the Mailchimp version on the same day the Engage version goes live.
• Chasing the headline number. The Mailchimp contact count is not a target. A smaller list with consent evidence sends better and carries less risk.
• Re-permission emails. Asking unconsented contacts for consent by email is itself a marketing email. Let them rejoin at WiFi sign-in instead.
• Forgotten forms. An old website form or booking engine link keeps writing to Mailchimp for months. Check each one during phase 4.
• Losing the venue field. Merging per-site audiences without a venue column stops you sending site-specific offers.
• A weekend cutover in peak season. Cut over midweek, outside your busiest trading period, with the CRM manager on hand for 48 hours.

Where Purple Engage fits

Purple Engage is the CRM and email marketing platform built for physical venues. Its campaigns and automations run on WiFi visit data. The difference from Mailchimp is where the list comes from. Engage builds your list from guest WiFi logins as consented, first-party data, rather than waiting for imports and form fills.

Purple is hardware-agnostic and runs as a cloud overlay on the access points you own. That includes Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. Purple is ISO 27001 certified and aligned with GDPR and PECR.

{"items":[{"value":"80,000+","label":"live venues on Purple","note":"Purple's own data"},{"value":"90","label":"countries","note":"Purple's own data"},{"value":"57x","label":"ROI from guest WiFi loyalty at Harrods","note":"Purple customer result"}]}

To see how the list is captured at sign-in, read the WiFi marketing guide. To compare platforms feature by feature, use the Purple Engage comparison page. If you run restaurants or hotels and are still shortlisting, Constant Contact alternatives for restaurants and hotels covers the wider field.

Frequently asked questions

How long does it take to switch from Mailchimp to Purple Engage?

Plan for about 10 weeks on a multi-site estate and less for a single venue. Most of that time goes on the consent audit and four weeks of parallel running, not on the import itself. The phases run in sequence, so a delay in proving consent pushes everything back. Start the audit early, and run it while guest WiFi goes live at each venue.

Can I move my whole email list from Mailchimp into Purple Engage?

No, and you should not try. Import only contacts with a recorded consent source and timestamp. Load unsubscribed and cleaned contacts as suppression, so Engage can never email them. Contacts with no consent record stay out. They come back the lawful way, by signing in to your guest WiFi and opting in on their next visit. A smaller list with proof beats a larger one without it.

Do I need new WiFi hardware to use Purple Engage?

No. Purple is hardware-agnostic and runs as a cloud overlay on the access points you already own. It works with Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. Guest WiFi sign-ins at your venues then add contacts to Engage. That is how the list keeps growing after the Mailchimp import is done.

Is a list migrated from Mailchimp GDPR compliant?

It is compliant only if the consent evidence comes with it. GDPR Article 7 puts the burden of proving consent on you as controller, and switching platforms does not change that. Purple is ISO 27001 certified and aligned with GDPR and PECR. New contacts from WiFi sign-in arrive with a conscious-choice opt-in. Imported contacts are only as sound as the records you bring.

Can I keep Mailchimp running alongside Purple Engage?

Yes, during the parallel-running phase, and that is the safe way to switch. Split by campaign type so no guest receives the same email twice. Sync unsubscribes both ways every week. Over the long term, two senders double the suppression work and split your reporting. Close Mailchimp once the cutover has held for 30 days and the final export is archived.

How does Purple Engage compare with Mailchimp, Klaviyo and HubSpot?

The difference is where the list comes from. Mailchimp, Klaviyo and HubSpot send campaigns to contacts you collect through forms, imports and integrations. Purple Engage builds the list from guest WiFi sign-ins, capturing consent at the point of connection with visit data attached. That lets you trigger automations on visits and absence, not only on email activity. See the side-by-side on the Engage comparison page.

What does Purple Engage cost compared with Mailchimp?

Ask Purple for a quote based on your venue count. Engage is one of three Purple plans, alongside Connect and Capture. When you compare it with Mailchimp, include the cost you stop carrying. Today you maintain the forms, integrations and imports that keep the list growing. With Engage, guest WiFi sign-ins grow the list at every venue, and the consent record arrives with each new contact.