Live in two months, right as the Marketo contract ended.
Marketo to Mautic migration for Meesenburg
We moved Meesenburg's email marketing from Adobe Marketo to a self-hosted Mautic in two months. About 95,000 contacts with their full consent history, the weekly newsletter, the online shop automation flows and the Mulesoft link to SAP went live right as the Marketo contract ended.
- ~95,000
- Contacts migrated
- Two months
- From Marketo to Mautic
- 213
- Custom fields audited
About Meesenburg
Meesenburg is a German building hardware distributor headquartered in Flensburg. It sells to business customers through its branches and an online shop. All of its email marketing ran on Adobe Marketo, fed with customer data from SAP ERP and the itmX CRM through a Mulesoft middleware layer.
Meesenburg decided to move from Marketo to Mautic, the open source marketing automation platform. The end of the Marketo contract set the timeline for the whole project.
- Client
- Building hardware distributor
- Sales
- Branches and an online shop
- Data
- SAP ERP and itmX CRM via Mulesoft
Migration at a glance
Contacts migrated
~95,000
Timeline
Two months
Custom fields audited
213
Sender authentication
SPF, DKIM, DMARC
Lifecycle tracks
Five
Emails in those tracks
~22
Brands on one setup
Meesenburg and STROXX Energy
Sending
Amazon SES, dedicated IP
The Challenge
Meesenburg wanted to switch platforms without stopping its email marketing for a single week. Discovery showed that the Marketo setup was larger than the initial brief: five automations instead of two, a double opt-in process with voucher codes, location-based content and a second brand.
Hard deadline: the new Mautic setup had to go live before the Marketo contract ended.
- 01
Carry over ~95,000 contacts with every consent, double opt-in and unsubscribe state intact
- 02
Rebuild the weekly newsletter and the shop flows: ~22 emails across five lifecycle tracks
- 03
Keep the SAP ERP and itmX CRM data flow through Mulesoft, now pointing at Mautic
- 04
Keep the voucher codes new subscribers receive in their welcome email
- 05
Send from Meesenburg’s own domain through a dedicated IP address
- 06
Keep the team’s routine: clone last week’s newsletter, drop in blocks, send
The Solution
We started with a technical audit of Marketo, built the new platform on Mautic, migrated by script instead of by hand, and kept a rollback path for the cutover.
- 01
Technical audit of Marketo
We exported all 213 custom fields, checked which of them held data, and read Meesenburg’s own documentation of its programs. Together with the client we split the work into what had to run on day one and what could follow after go-live.
- 02
New platform on Mautic
We built the new platform on Mautic, hosted on a server in the EU that we manage. Emails go out through Amazon SES in Frankfurt.
- 03
Migration by script, not by hand
An AI coding agent read the Marketo exports and wrote scripts that create fields, segments and emails in Mautic. Assets not available through the Marketo API were copied by our developer into files the agent could work with. Every script ran the same way on test and production, so dry runs were cheap and the final import predictable.
- 04
Cutover with a rollback path
Marketo kept running until the Mautic sends were validated. A delta import moved the contacts that changed in Marketo after the main import.
- Platform
- Self-hosted Mautic, EU server
- Sending
- Amazon SES in Frankfurt
- Migration
- Scripted, same on test and prod
Features delivered
What we built in the Marketo to Mautic migration, and what each piece changed for Meesenburg.
01 Contact and consent migration
We moved about 95,000 contacts from Marketo to Mautic. Unsubscribes, bounces and blocked addresses became Mautic Do Not Contact entries. Double opt-in status and consent dates stayed on the contact as proof of consent. Where the same person existed twice, the stricter consent state won.
The result: Unsubscribes and the consent trail moved with the contacts, so Mautic respects the choices people made in Marketo.
02 Shop activation flows rebuilt as Mautic campaigns
In Marketo this was one engagement program with several streams. In Mautic we rebuilt it as a set of campaigns and segments that hand a contact from one track to the next: from registration to first order, then on to the next purchase. A contact leaves the flow after the second order. Mautic cannot compare two fields out of the box, so we added that check ourselves: first order date different from last order date means a repeat customer.
The result: Each shop customer gets the emails for their stage, and the hand-offs between tracks prevent overlapping emails.
03 Newsletter template built from reusable blocks
We moved Meesenburg’s Marketo template into the Mautic email builder as a set of blocks. The team drags sections in from the side panel and deletes what it does not need. STROXX Energy got its own header and footer on the same base. Footers change with the contact’s branch, so a customer of the Flensburg or Oldenburg branch sees local details.
The result: The weekly newsletter routine stayed the same for the marketing team.
04 Double opt-in with voucher codes
New subscribers confirm their address, get up to two reminders if they do not, and then receive a welcome email. That email contains a personal voucher code. We wrote a Mautic plugin that fetches the code from Meesenburg’s voucher service at the moment of sending.
The result: The welcome offer works as it did in Marketo, with double opt-in in front of it.
05 Mulesoft integration with SAP and itmX
Meesenburg’s own Mulesoft team owns the middleware. We gave them what they needed to re-point it: API and data model documentation and a Postman collection for testing calls against Mautic. Our developer supported them during their mapping work.
The result: Customer data from SAP ERP and itmX CRM flows into Mautic, and the middleware stayed in the hands of the client’s own team.
06 Sending infrastructure on Amazon SES
We set up Amazon SES in Frankfurt with a dedicated IP address and configured SPF, DKIM and DMARC for Meesenburg’s sending domain. Bounces and complaints flow back from SES into Mautic through a webhook, and Mautic stops sending to those addresses. The first newsletters went out in growing waves to build the IP’s reputation.
The result: Meesenburg sends from its own domain and IP, and bounce handling runs without manual work.
07 Forms and landing pages on Meesenburg’s domains
Newsletter sign-up, account preferences, thank-you pages and event landing pages run on Meesenburg’s own subdomain, as they did with Marketo. The Mautic admin panel has a separate subdomain.
The result: Customers see the same addresses as before. Only the platform behind them changed.
- ~95,000
- Contacts with consent history
- 2 months
- From Marketo to Mautic
- 213
- Custom fields audited
- 5
- Customer lifecycle tracks
The Result
Mautic is now Meesenburg’s marketing automation platform. The weekly newsletter, the shop activation flows, double opt-in and the Mulesoft sync all run from the new setup.
The marketing team works with the same templates and blocks it used in Marketo.
Mautic is open source, so there is no licence fee per contact.
Contact data sits on a server in the EU.
Hosting, monitoring, security updates and monthly consulting hours under a maintenance plan.
A reusable event mailing pattern: invitation email, landing page, registration form and thank-you page.
Tech Stack
Marketing automation
Sending
Integration
Custom code
Email builder
Migration
Meesenburg’s opinion about the project
We asked Droptica to migrate our marketing automation platform from Adobe Marketo to Mautic. Droptica prepared a complete migration plan and delivered the migration end to end.
The timeline was very tight. Even so, the team delivered all core functionality on schedule, so our marketing activities continued without interruption.
Like this project? Migrate to Mautic with us!
Book a free meeting to talk about your Marketo, HubSpot or Pardot setup and your contract end date. We'll contact you to see how we can help with your migration.