Moving a Marketo engagement program to Mautic campaigns is the part of a migration that no import tool covers. Mautic has no engagement program, no streams and no casts. You rebuild the same customer journey from campaigns, segments, tags and delays. Here is how we read an engagement program, map it and rebuild it, using a shop activation program we moved for a German B2B distributor.
Why can’t you import an engagement program into Mautic?
The two platforms model a nurture journey in different ways.
A Marketo engagement program is a container. It holds streams, and each stream holds an ordered list of emails or child programs. A cadence (the cast schedule) decides when the program sends. At each cast, every member gets the next piece of content they have not seen yet. Transition rules move people between streams. When a member has received everything in a stream, Marketo marks them as exhausted. Around all this sit smart campaigns with triggers, filters and flow steps that do the real work: add people to the program, change their stream, send alerts, set program statuses.
A Mautic campaign is a workflow per contact. A contact enters from a segment or a form, then moves through events on a canvas: actions, decisions and conditions. Every event can carry a delay that counts from the previous event. There is no shared send schedule and no idea of “next unseen content”. The order is the path on the canvas.
So you rebuild the business logic. Contacts, fields and templates move with scripts. The journey needs design.
How do Marketo concepts map to Mautic?
We start every engagement program rebuild with this table. It tells the client’s marketing team where each familiar Marketo idea will live in Mautic.
| Marketo concept | What it does | Mautic equivalent |
|---|---|---|
| Engagement program | Container for a nurture journey | One or more campaigns, plus segments and tags that connect them |
| Stream | Ordered content for one audience | A drip campaign: Send Email actions in a chain |
| Cast and cadence | Shared send schedule for the program | Delays on each event, relative to the previous one, optionally limited to set days and hours |
| Transition rules | Move members between streams | A gate campaign with conditions, plus the Change Campaigns action |
| Exhaustion | Member has received all content | End of the campaign path, usually marked with a tag |
| Content on/off | Pause one email in a stream | Remove the event, or route around it with a condition |
| Smart campaign trigger | Starts a flow when something happens | Campaign source (segment or form) or a decision such as Submits Form or Opens Email |
| Smart campaign filters | Limit who qualifies | Segment filters, or conditions on field value, segment or tag |
| Flow steps | Send Email, Wait, Change Data Value, Send Alert | Actions: Send Email, Update Contact, Modify Contact’s Tags, Send Email to User, with delays |
| Flow step choices | ”If X, send email A, else B” | A condition with a green and a red path |
| Program statuses | Member, Engaged, Registered | Tags, Stages or points, depending on what reports need |
| My Tokens | Program level text and values | Contact field tokens, snippets in the email builder, Twig for logic such as salutations |
| Communication limits | Cap emails per day and week | Frequency rule for marketing emails |
Transition rules and flow step choices carry most of the design work. Marketo hides them inside one program. In Mautic they become visible campaigns and conditions.
How do you read an engagement program before migrating?
Half of an engagement program is not available through the Marketo API. Plan for that before you estimate.
Export what the API gives you
The Marketo REST API returns a lot of useful structure:
- programs and smart campaigns, including an undocumented
parentProgramIdthat shows which campaign belongs to which program, - smart list rules with their full filters, and static lists,
- email HTML, both raw and with tokens resolved,
- templates, snippets and the My Tokens folder.
Our developer pulls all of this into files in the project repository. It becomes the inventory: every email, every smart list, every token, with an ID.
Document what only the UI shows
Three things you will copy from the Marketo UI by hand:
- Streams and cadence. The order of the emails in each stream, which content is switched on and the cast schedule live on the Streams tab. The API does not return them.
- Flow steps. A smart campaign returns a
flowId, but no endpoint reads it. The flow steps, with their choices and wait steps, exist only on the Flow tab. - Current counts. The member counter on smart lists in the UI can be stale. Refresh it before you compare numbers.
For each smart campaign we write one block in a plain text file: trigger, filters, then every flow step with its choices. For each stream: the emails in order, their on/off state and the cadence. This work gets its own line in the estimate, because the flow steps hold the real logic. In our project they decided which email a contact got based on double opt-in status, an A/B variant and the contact’s industry. None of that was visible from the API export.
Questions to answer for every stream
- Who enters, and what event puts them there?
- What moves them out: a transition rule, a purchase, an unsubscribe?
- Which emails are switched on today?
- Which conditions pick between email versions?
- What happens when a member reaches the end?
- Which smart campaigns outside the program touch the same people?
The last question finds the overlaps that later cause double sends.
What did the rebuild look like?
The brief said “two automated flows”. Our audit found one engagement program for shop activation with 22 active emails in three streams. One of the three streams was empty. Programs with smart campaigns sat under each email, and lists handled the segmentation.
We rebuilt it as four Mautic campaigns:
- Gate campaign for activation. Picks up new shop registrants and hands them to the activation drip.
- Activation drip. 12 emails for registered customers who have not ordered yet. Sends on days 3, 6, 10, 17, 24 and 31, with A/B and industry variants, then in months 6, 8 and 10.
- Gate campaign for first purchase. Picks up customers after their first order, takes them out of the activation track and hands them to the next drip.
- First purchase drip. 10 emails, on days 3, 7 and 14, in weeks 16 and 20, and in months 6 and 9.
A contact leaves the first purchase drip after the second order. Mautic cannot compare two fields out of the box, so we added a custom campaign condition for that check. We describe it in comparing two fields in a Mautic campaign condition.
Steps that were switched off in Marketo did not move. The empty stream did not move either.
Pattern 1: a gate campaign plus a drip
Why split one journey into gates and drips? Because each piece then has one job, and you can read it on one screen.
A gate campaign decides where a contact belongs. It does three things:
- Takes contacts from an entry segment (for example: registered in the shop, no order yet).
- Checks the conditions that matter at entry.
- Marks the contact with a tag for the track, removes them from any earlier track and adds them to the drip with the Change Campaigns action.
A drip campaign only sends. It holds the Send Email actions, the delays between them and the conditions that pick variants. It does not decide who belongs in it.
This split solves the transition rule problem. In Marketo a transition rule moved a member from one stream to the next inside the same program. In Mautic the gate for the next stage does that move: it removes the contact from the previous drip and adds them to the new one in the same step. The hand-off happens in one place, and nobody has to remember to stop the old track.
The marketing team can also add an email to a drip without touching the entry logic.
Exit on a condition
Each email in the first purchase drip sits behind a condition that asks “has this customer ordered a second time?”. The delay sits on the condition itself, so Mautic waits, then checks, then sends. On the “yes” path the contact gets a tag and leaves the campaign. On the “no” path the next email goes out. The check runs right before every send, so a customer who orders on day 13 does not get the day 14 email.
Pattern 2: A/B tests and variants by field
Marketo flow steps often hide two kinds of branching: a random split for a test and a choice based on data. Mautic handles them with different tools.
A/B test of one email. Mautic emails support A/B variants. You create a variant of the email, set the traffic weight and pick the winner criterion. The campaign keeps one Send Email action, and Mautic picks the variant for each contact. Use this when the test is about one message: subject line, layout, offer.
A persistent test group. Sometimes a test runs across several emails and the same contact must stay in group A the whole way. Then store the group in a contact field when the contact enters (the gate campaign is a good place) and branch on it with a Contact field value condition. Every later step reads the same field.
Variants by field. Industry, language or brand are data, not tests. Use a Contact field value condition and give each value its own Send Email action. If only one block of the email changes, keep one email and switch the block with dynamic content. Mautic can change content based on contact data, so you avoid duplicating the whole email.
A simple rule we use: if the versions differ in one block, use dynamic content. If they differ in structure, subject or send time, use separate emails behind a condition.
Pattern 3: turning cadence into delays
Marketo engagement programs send on a shared schedule. Mautic delays count from the previous event for each contact. So a list like “day 3, day 6, day 10” has to become gaps.
Here is the activation drip, with day 0 as the moment the gate hands the contact over:
| Send point | Delay before this email |
|---|---|
| Day 3 | 3 days |
| Day 6 | 3 days |
| Day 10 | 4 days |
| Day 17 | 7 days |
| Day 24 | 7 days |
| Day 31 | 7 days |
| Month 6 | 5 months |
| Month 8 | 2 months |
| Month 10 | 2 months |
Three details to get right:
- Units. Mautic delays come in minutes, hours, days, months and years. There is no week unit, so week 16 becomes 112 days and week 20 is 28 days after that.
- Variants and timing. Put the condition that picks a variant after the delay, or put the delay on the condition. Then both branches send at the same moment.
- Send windows. A cast in Marketo might go out on Tuesday mornings. A Mautic delay can be limited to set hours and days of the week, so the email waits for the next allowed window. Use this for B2B audiences who read email during working hours.
How do you prevent double sends?
Overlapping emails are the usual side effect of splitting one program into several campaigns. A contact sits in two segments, two drips send, and the customer gets two emails on the same morning. Our rules:
- One track per contact. Each track has a tag. The entry segment of every gate excludes contacts that carry the tag of a later track. A customer who has ordered never qualifies for activation again.
- Hand off in one step. The gate that adds a contact to the next drip removes them from the previous one in the same Change Campaigns action.
- Remember how segments drive campaigns. A segment-sourced campaign follows its segment: when a contact drops out of the segment, the next campaign update removes them. Design entry segments so a contact cannot drop out by accident, for example because of a field the integration clears for a moment.
- Removal from a dynamic segment sticks. If a campaign action removes a contact from a filter-based segment, Mautic will not add them back based on the filters. Use that on purpose, and document it.
- No restarts. Leave “Allow contacts to restart the campaign” off for drips.
- Marketing type for drip emails. Mautic sends a marketing email from a campaign to a contact only once and applies frequency rules to it.
- A frequency rule as a safety net. Set a default limit for marketing emails per day or week. It catches overlaps your design missed, including the weekly newsletter landing on the same day as a drip email.
Before go-live, list every campaign that sends to the same population and check each pair against these rules.
How do you test a drip without waiting ten months?
A ten month drip cannot be tested in real time. You test entry, branching and exits with test contacts, and you compress time.
Build a test contact for every path
Create one test contact per branch, using addresses you control:
- variant A and variant B,
- each industry value that has its own email,
- a customer with no order, with one order and with a second order,
- a contact who already carries the tag of a later track.
Shift the dates, not the calendar
Set dates on the test contacts in the past. A registration date three weeks ago puts the contact into the entry segment as an existing registrant. First order date equal to last order date simulates the first purchase. Change the last order date and the contact looks like a repeat customer, which should fire the exit on the next check.
To run through the delays, use one of two approaches on the test instance:
- Clone the drip and shorten every delay to minutes. Good for checking the path and the email content.
- Run the real campaign and move the scheduled dates of pending events forward. Good for checking the real configuration.
Then run the cron commands by hand (mautic:segments:update, mautic:campaigns:update, mautic:campaigns:trigger) and read each contact’s campaign history. Every test contact should receive exactly the emails your documentation of the Marketo flow says it should, and nothing else.
Our developer kept the migration as scripts that ran the same way on test and production, so dry runs were cheap. The client’s marketers then clicked through the flows themselves.
What should stay behind in Marketo?
A migration is a good moment to drop what no longer works. Our decision rules:
- Switched off content. If an email is off in the stream, it does not move. If the team wants it back, it goes in as a new email with a fresh review.
- Empty streams. They stay behind. A future track gets designed when there is content for it.
- Program statuses nobody reports on. Move a status only if a report or a segment uses it. Otherwise the email statistics in Mautic cover it.
- Program member fields. Mautic has no program membership, and the Lead API does not return these fields. Old event history stayed in the Marketo archive. For new events we mark registrants with a tag per event.
- Housekeeping programs. Decide one by one with the client. Bounce categorization, for example, has no job in Mautic when the sending service reports bounces and complaints by webhook and Mautic sets Do Not Contact with a reason. Activity dates and inactivity flows need a conversation about which segments still use them.
Every item gets a line in the migration notes: moved, rebuilt or dropped, with the reason. When someone later asks where an email went, the answer is in one file.
FAQ
Can I import a Marketo engagement program into Mautic? No. There is no importer for programs, streams or flow steps. Emails, templates and contacts move with scripts. The journey is rebuilt as Mautic campaigns.
How many Mautic campaigns does one engagement program need? It depends on the transitions. A practical start is one drip per stream that has content and one gate per hand-off. Our three-stream program became four campaigns.
Does Mautic have an equivalent of stream exhaustion? Not as a status. The end of a campaign path is the end of the content. Add a tag at the end if other campaigns or reports need to know who finished.
Can Mautic run A/B tests inside a campaign? Yes. Create A/B variants of the email and use it in a Send Email action. For a test group that must stay stable across several emails, store the group in a contact field and branch on it.
What if a flow step needs logic Mautic lacks? A small plugin can add a custom campaign condition, as we did for comparing two date fields.
Planning to move your Marketo programs to Mautic?
This is one of the building blocks of our Marketo to Mautic migration for Meesenburg.
Send us a list of your engagement programs and smart campaigns. We will tell you how they map to Mautic and what the rebuild involves. Talk to our Mautic team.
Tags
Written by
Mautomic Team
Mautic experts sharing insights on marketing automation, custom development, and open-source technology.