Moving a ticketed event list from Mailchimp to Drip
Ticket buyers are tagged in Mailchimp for the old reminder journey and recorded in Drip as an event with revenue for the new workflow. Both reminders can run until you switch the old one off.

Native integration
Mailchimp and Drip both have built-in Plandalf steps, so one checkout can fill both while you move your automations across.
No credit card required. No coding required.
Mailchimp
DripPlandalf does not sync Mailchimp with Drip, but it has native steps for both, so a single sequence can write the buyer to each. Contact Subscribed in Mailchimp and Tag Applied in Drip can each start a sequence that passes the person to the other tool.
| Event | From and to | Through | What happens |
|---|---|---|---|
| Checkout completed | Plandalf → Mailchimp | Native step | Add or Update Contact with a status for new contacts, then Add Tags to Contact. Record Event starts a Customer Journey but carries no revenue. |
| Checkout completed | Plandalf → Drip | Native step | Create or Update Subscriber, Apply Tag and Record Event in the same sequence. Give the event a value property set to {{trigger.total}}, which is already in cents, and Drip counts it as revenue. |
| Contact subscribed | Mailchimp → Drip | Native step | The trigger starts a sequence that runs Create or Update Subscriber and Apply Tag in Drip, so people who join the Mailchimp audience reach Drip without a manual export. |
| Tag applied | Drip → Mailchimp | Native step | Pick a Tag on the Drip trigger to fire for one tag only. The sequence then runs Add Tags to Contact in Mailchimp for the subscriber's email. |
| Invoice refunded | Plandalf → Mailchimp | Native step | Remove access on refund adds Remove Tags from Contact for Mailchimp and Remove Tag for Drip into one sequence, each already pointed at {{trigger.customer_email}}. |
Connect both accounts first: a Mailchimp API key with its suffix, and a Drip API token plus the numeric Account ID.
In Automation, then Marketplace, connect Mailchimp and Drip. For Drip, paste the token from User Settings and the Account ID from Account settings, then wait for Drip connected.
Under My Sequences, choose Plandalf and Checkout Completed, pick the offer, and select a recent checkout as the sample on the Test tab.
Add Mailchimp, Add or Update Contact, and a tag step with the product name. Leave Status for New Contacts on Subscribed only if your checkout asks for marketing consent.
Add Drip, Create or Update Subscriber, then Record Event named exactly as your Drip workflow expects. Add product and value event properties.
Add the Remove access on refund template for the same checkout and pick the Mailchimp tags and the Drip tag. Keep Full refunds only on so a goodwill partial refund leaves both tags alone.
Once the Drip workflows send what the Customer Journeys did, delete the Mailchimp steps from the sequence. Nothing else in the sequence changes.
Ticket buyers are tagged in Mailchimp for the old reminder journey and recorded in Drip as an event with revenue for the new workflow. Both reminders can run until you switch the old one off.
Some sellers never fully leave Mailchimp. Tagging there keeps the newsletter segments honest, while Drip carries the revenue events and purchase workflows.
value event property, in cents. Mailchimp events carry none, so the order total has to travel as an event property or a merge field.value event property in cents. In Mailchimp, which does not accept revenue on events, put it in an event property or a merge field.Checked October 26, 2026 against Plandalf's own setup guides.