← Every platform we move you from

You are paying for people who unsubscribed

Your audience, every merge field you added, and consent handled properly: from the audience export.

One file, minutes.

subscribed_members_export_....csv

read locally

This is a Mailchimp audience export

We can tell from the columns and the file name.

Audience

128 of 129 ready

128 audience ready: 1 row will be skipped.

Must fix

Row 84: this record has no name.

Nothing has been saved yet.

The pricing is per contact, and contacts only ever accumulate.

1

Unsubscribed and bounced addresses still count

You are being billed for people who have explicitly told you to stop emailing them. Managing that is a monthly chore whose only purpose is to lower an invoice.

2

The list has no idea who is a customer

Mailchimp knows an email address. It does not know they have spent four hundred pounds with you, or that they have an open support ticket, unless you pay to connect something that half-tells it.

3

Segmenting on behavior means integrating on behavior

"Everyone who bought this and not that in the last ninety days" is a connector project, not a query.

What comes across

Everything in this list is something an importer we maintain actually reads out of your Mailchimp export. It is generated from that importer, so it cannot promise you something we do not do.

Customers

The files you need from Mailchimp

Audience

Audience → All contacts → Export Audience

subscribed_members_export_....csv

A list that is the customer list.

In sparx the mailing list and the customer database are the same records. Segmenting on what someone bought, what they spent or what they returned is a filter, not an integration, because the orders are in the same database as the addresses.

What that changes

  • Only confirmed double opt-ins are imported as permission to email. Anything else lands without it, which is recoverable: the reverse is a complaint.

  • Every merge field you added comes across as a custom property.

  • Segment on orders, spend and support history without connecting anything.

What does not come across

Every migration leaves something behind. Here is ours, so it is not a surprise halfway through.

  • Campaigns, templates and automations are rebuilt here.

  • Mailchimp's Address merge field is a single cell, so it is carried whole rather than split on guesswork.

  • Open and click history stays with Mailchimp.

Before you start

Still curious? Read the platform docs, browse the API spec, or book a 20-min architecture call. We don't do high-pressure demos.

No. Everything happens on a copy. You export a file, and your Mailchimp account carries on exactly as it is. Plenty of people run both for a few weeks before switching their domain over.

Bring it over

Export the file Mailchimp already makes for you, drop it in, and look at what would happen before anything is saved. One file, minutes.