← Back to Blog
Mautic Migration Marketing Automation

Marketo to Mautic migration: what transfers and what you have to rebuild

Marketo to Mautic migration in practice: what you can export by API, what maps one to one, and what you rebuild. Lessons from moving 95,000 contacts.

M Mautomic Team
7 min read

A Marketo to Mautic migration is not an export and an import. Contacts, fields and forms move almost one to one. Engagement programs, tokens, webhooks and Marketo’s housekeeping automations do not. You rebuild them with Mautic’s own building blocks. Here is the split we saw while moving about 95,000 contacts for Meesenburg, a German building hardware distributor.

What can you export from Marketo?

Start with what Marketo lets you take out. It decides how much of the migration you can script and how much someone has to copy by hand.

What the Marketo API gives you

The REST API and the bulk extract jobs cover most of the data:

  • Leads with their fields. A bulk extract job pulls all contacts with the fields you choose, including consent and unsubscribe fields.
  • The field list. Field Management exports every field with its REST API name, label and type. In our project that was 213 fields.
  • Static list membership, which you need to rebuild segments.
  • Part of the configuration: smart list rules for some lists, and a part of the email templates.

What you copy from the Marketo interface

Some assets are not available through the API, or come back incomplete. In our project that meant some email and landing page templates, and the filter logic of some smart lists. Our developer opened them in Marketo and copied the content into plain files, so the rest of the process could work on them.

We plan time for this in the estimate. It is manual work, and it is easy to leave out.

Program member fields need their own path

Program member fields do not come out with the lead export. They have no REST API name on the person record, because they belong to a program membership, not to the person. In our case they held event data, such as the number of people accompanying a registered guest. Decide early: do you migrate them through a separate export, or leave the history in Marketo’s archive?

What moves from Marketo to Mautic almost one to one?

A good part of the setup has a direct counterpart in Mautic. You still map it, but you do not redesign it.

MarketoMauticNotes
Person fieldsContact fields (core and custom)Create custom fields by script through the Mautic API
Static listsSegmentsMembership comes from the import
Unsubscribed, bounced, blocklistedDo Not ContactKeep the reason
Double opt-in flag and dateCustom fieldsProof of consent, required in Germany
FormsFormsRebuild fields and consent checkboxes
Landing pagesLanding pagesRebuild in the Mautic builder
Email templates and snippetsEmail builder blocksRebuild the template as reusable blocks

Two remarks from the project.

Clean the field list before you map it. Out of 213 Marketo fields, around 30 were dead weight: Marketo social fields, inferred location fields and placeholders. Check how many contacts actually have a value in each field. Then decide.

Rebuild the template, do not paste the HTML. The client’s Marketo template was one long email with every possible section, and the team deleted what it did not need each week. We moved it into the Mautic email builder as a set of blocks. The team now drags sections in from the side panel. The working habit stayed the same.

What do you have to rebuild in Mautic?

This is where the hours go. Marketo and Mautic reach the same business goal in different ways, so a one-to-one copy is not possible.

Engagement programs become campaigns and segments

The brief mentioned “two automated flows”. Our audit found one engagement program with several streams and about 22 emails across five lifecycle tracks. Mautic has no engagement program. We rebuilt it as several campaigns and segments: a campaign adds a contact to the next segment, and the next campaign takes over from there.

Get the hand-offs right. Otherwise a contact sits in two segments at once and gets two emails that overlap.

Some conditions need custom work

One exit rule said: the contact leaves the flow after the second purchase. The data had a first order date and a last order date. If they differ, the customer bought twice. Mautic segment filters cannot compare two fields with each other, so we built that check ourselves.

Expect a few rules like this in every Marketo account. Write them down during discovery, not during the build.

Tokens, scripts and webhooks

  • My Tokens and Velocity scripts. The client used a Velocity script for German salutations. We rewrote that logic for Mautic.
  • Webhooks. A Marketo webhook fetched voucher codes for the welcome email. In Mautic we wrote a small plugin with a campaign action that gets the code at sending time.
  • Location-based content. Footers changed with the contact’s sales office. We rebuilt them as dynamic content keyed to that field.

Marketo’s housekeeping automations

Many Marketo accounts run background programs that nobody mentions in the first call. Ours had “Bounce House” for bounce categories, “Activity Dates” for last activity fields, and an inactivity flow. Some of these you drop, because Mautic or your sending service already does the job. Bounces are one example: Amazon SES sends bounce and complaint notifications to a Mautic webhook, and Mautic marks the address as Do Not Contact. Others you rebuild. Decide for each one.

Scoring

Do not port Marketo scores. The algorithm differs, so the numbers mean nothing in Mautic. Rebuild scoring with Mautic points if you need it, and treat it as a separate task.

Where do people and companies differ?

The data model deserves a discovery session of its own.

A flat setup is the fastest start: all business data on the contact, and the company record with just its name. It works until an integration team wants to write company data through Mautic’s Companies API. Then moving fields from contacts to companies is not a simple switch:

  • Conflicting values collapse. If 14 contacts from one company have different values in a field that moves to the company, a plain migration keeps the last value written. The others are gone.
  • Segments behave differently. A contact in Mautic can belong to more than one company. A segment filter on a company field picks up the contact if any of its companies matches. Marketers who expect “the company’s value” are surprised.

Settle it in discovery. For every group of fields, agree whether it lives on the person or on the company, and which system is the source of truth.

How do we use AI coding agents in a migration?

Every marketing automation platform has its own data model, API limits and naming. We move clients to Mautic from different platforms, so each project starts with mapping the source platform in detail. Our developers use an AI coding agent to do that mapping faster and to keep the migration repeatable. The developer runs the migration: decides what maps where, reviews every script and approves every run.

The workflow:

  1. Export everything the Marketo API returns: fields, lists, templates, smart list rules.
  2. Have the agent analyse the exports and list what is missing.
  3. Copy the missing pieces from the Marketo interface into files.
  4. Have the agent draft scripts that create fields, segments and emails in Mautic, then review each one.
  5. Run the same scripts on the test environment, check the results, fix, and run them on production.

The agent helps most with large exports, template and landing page conversion, and scripts that behave the same on every environment. Every result goes through a developer’s review. The agent speeds up the work, and the decisions stay with the team.

A transfer matrix you can reuse

Use this table in your own discovery. Fill in the last column for every item you find in Marketo.

Marketo itemTypical decisionEffort driver
Leads and person fieldsMigrateField cleanup, consent mapping
Static listsMigrate as segmentsNumber of lists
Smart listsRebuild as segment filtersRules not available by API
Engagement programsRebuild as campaigns and segmentsNumber of streams and emails
Smart campaignsRebuild as campaign triggers and actionsConditions Mautic lacks
Email templates, snippetsRebuild as builder blocksBrands, variants, locations
Forms, landing pagesRebuildDomains, consent text
My Tokens, VelocityRewriteScript complexity
WebhooksRewrite as plugin or integrationExternal service docs
Program member fieldsSeparate export or archiveEvent history needed?
Housekeeping programsDrop or rebuildWhat the sending service already covers
ScoringRebuild laterSeparate project
Send history, old newslettersArchive in Marketo exportUsually not migrated

FAQ

Can I migrate Marketo send history to Mautic? You can export activities, but they will not become Mautic email statistics. Most teams keep a Marketo export as an archive and start fresh reporting in Mautic. Our client chose not to migrate historical newsletters and send history.

How long does a Marketo to Mautic migration take? Our project took two months from contract to go-live, under a fixed deadline. The size of the automation setup drives the time far more than the number of contacts.

Do I lose unsubscribes and consent? Not if you map them on purpose. Unsubscribes, bounces and blocked addresses become Do Not Contact entries in Mautic. Keep double opt-in flags and dates as fields.

Does my CRM integration keep working? Only after someone re-points it to the Mautic API. In our case the client’s Mulesoft team did that, with our API documentation and a Postman collection.

Planning to leave Marketo before your contract ends?

We moved Meesenburg, a German building hardware distributor, from Marketo to Mautic before its Marketo contract ran out. About 95,000 contacts with consent, the weekly newsletter, shop automation flows and the Mulesoft link to SAP moved to the new platform. Read the full Marketo to Mautic migration case study.

Tell us your contract end date and what runs in your Marketo account. We will tell you what moves, what needs a rebuild, and how long it will take. Talk to us about a Mautic migration.

Tags

#Mautic#Marketo#Migration#Marketing automation#Open Source
M

Written by

Mautomic Team

Mautic experts sharing insights on marketing automation, custom development, and open-source technology.

Need help with Mautic?

Our team of experts is ready to help you implement and optimize your marketing automation.

We'll get back within 24h. Privacy Policy