Intuit Retires Legacy Mailchimp for Shopify App; Syncs Must Move
Intuit has disabled the legacy Mailchimp for Shopify integration, leaving stores to migrate automations and reconnect before the sync stops.
The original Mailchimp connector for Shopify is no more. Intuit has quietly disabled the app now labeled Mailchimp for Shopify [Legacy]. Stores still running it must migrate to the current integration to keep customer and order data flowing into Mailchimp. Nothing upgrades on its own, so the work falls to whoever manages the store.
A retired connector with no automatic upgrade
Mailchimp for Shopify [Legacy] was the first-generation link between a Shopify storefront and a Mailchimp account. Intuit switched it off rather than migrating anyone in the background. The result is a manual transition, laid out as a step-by-step guide in the vendor’s help pages.
The overlap matters to our readers. Plenty of small merchants keep the books in QuickBooks and the mailing list in Mailchimp, with a Shopify storefront feeding both. A connector retirement inside that stack belongs on this desk.
How do you know you are on the legacy app?
Mailchimp keeps a list of the apps connected to your account. Scroll to the authorized applications section and open the Shopify entry. A label carrying the word Legacy means the retired connector is yours, and the migration steps apply. An entry without the tag means you are already on the current app. The check takes a moment and settles the question before you plan anything.
The order of operations matters
Intuit’s sequence is deliberate, and deviating from it invites duplicate sends. Pause your active campaigns before anything else. Then install the current Mailchimp for Shopify app and connect it to your store, which re-establishes the flow of customers and order data. Migrate your e-commerce automations across next. Disconnect the legacy integration only when the rest is done.
Running two live connectors at once is the failure mode to avoid. The same customer action could trigger the old flow and the new one, so a buyer receives two identical emails. The pause at the start and the disconnect at the end exist to close that window.
Which automations move, and which need a rebuild?
Not everything transfers cleanly. Signup-triggered automations, welcome emails being the common case, must be archived and rebuilt inside the new app. Intuit recommends saving each flow as a template first, which removes most of the rebuild effort.
The abandoned cart series is the harder gap. It does not migrate for now, and no timeline has been given. Stores that depend on cart recovery emails should plan for a period without them, since the legacy flows stop once the old connector is disconnected.
Permissions and one checkout setting
Manager-level access or above is required to change an integration. Restricted logins will find the migration blocked until someone with the right role handles the switch.
One checkout setting deserves attention during the move. If your store offers marketing signup at checkout, leave the preselect option unchecked. Checking it would subscribe every buyer by default rather than by choice. Shopify’s help center documents the store-side marketing settings in detail.
Intuit’s own help pages carry the full transition walkthrough, and any change to the abandoned cart gap would surface there.
Doing nothing is also an answer
Stores that have outgrown the sync can skip the whole exercise. The retired connector simply stays retired. Intuit’s guidance is explicit that the Mailchimp audience is unaffected either way, so contacts and campaign history stay where they are. Your Shopify store keeps running normally; only the marketing data handoff is in play.
The short version
- Check authorized applications in Mailchimp for a Shopify entry tagged Legacy.
- Pause active campaigns before touching the connection.
- Install the current Mailchimp for Shopify app and link it to the store.
- Archive signup-triggered automations, save them as templates, then rebuild them in the new app.
- Plan around the abandoned cart series, which does not migrate for now.
- Disconnect the legacy integration last, after the automations are settled.
- Do nothing at all if the sync no longer matters to your business.
The job is re-linking and rebuilding rather than rescue work. Once the current app is connected and the rebuilt flows are live, syncing resumes on the supported connector. From there, day-to-day use looks the same as it did before the retirement.