0
Revenue gap
A 900,000-subscriber retail program moved between platforms with zero measurable dip in email revenue across the cutover week.
ESP migrations & deliverability
Email that changes shape with your business.
We move email programs between platforms without losing deliverability, and engineer the sending infrastructure underneath them. Quiet, technical work that stops your domain becoming somebody else's problem.
RotterdamFounded 201831 migrations completed
Services
Three kinds of work, all of them unglamorous.
No brand strategy, no creative retainer. We move email programs between platforms, keep them authenticated and deliverable, and monitor the infrastructure that carries them.
Platform migrations
Moving a live program between ESPs without a revenue gap. We map every flow, rebuild it in the new platform, run both in parallel, then cut over on a date you pick.
- Audit and flow mapping
- Parallel-run period
- Domain and IP transition
- Cutover and rollback plan
Deliverability engineering
Authentication, reputation and list health treated as infrastructure rather than a checklist. SPF/DKIM/DMARC configured properly, sending domains warmed, complaints monitored.
- SPF/DKIM/DMARC and BIMI
- Domain warm-up
- Suppression and hygiene
- Reputation monitoring
Infrastructure & monitoring
The plumbing underneath: sending domains, subdomain strategy, webhook pipelines into your warehouse, and alerts that reach a human before a blocklist does.
- Subdomain architecture
- Webhook and event pipelines
- Warehouse sync
- Alerting and on-call
Migrations
One program, four states, no revenue gap.
Scroll through the four stages every migration passes through, in the order we run them.
Step 01
Audit
We read a year of sending history, map every automation, and write down what the new platform must reproduce. Nothing moves until that document is agreed.
Step 02
Rebuild
Flows, segments and templates rebuilt in the target platform. Rebuilt, not exported — an export carries the old platform's assumptions with it.
Step 03
Parallel run
Both platforms send for two to three weeks, split by segment, so we can compare deliverability and revenue on live traffic rather than in a spreadsheet.
Step 04
Cutover
Sending domains transition on a date you choose, with a rollback path that stays open for thirty days. Then we monitor reputation daily for a month.
Method
Seven weeks, on a rail you can see.
A migration runs on a fixed cadence: read the account, model the rebuild, move traffic gradually, then watch what happens after cutover.
01
Week 1
Read
We pull a year of sending history and account configuration and read it end to end — every automation, every suppression rule, every integration touching the account.
02
Weeks 2–4
Model
The target platform's data model rarely matches the source one-to-one. We design the mapping first, then build to it, so nothing is improvised mid-migration.
03
Weeks 5–7
Move
Traffic shifts by segment on a schedule agreed in advance, not all at once. Each shift is measured against the old platform before the next one starts.
04
30 days
Watch
Reputation, placement and complaint rate are checked daily for a month after cutover, with the rollback path left open the entire time.
Results
What a migration should look like, afterwards.
Inbox placement recovering after a clean authentication rebuild, tracked over the eight weeks around a cutover.
Every migration is different, but the shape of a healthy one repeats: a dip or plateau while authentication and warm-up settle, then a climb past the pre-migration baseline once reputation transfers.
We report placement, complaint rate and revenue against baseline weekly through the parallel-run period and for thirty days after cutover.
+18%
Inbox placement
A subscription publisher's placement rate recovered after a full authentication rebuild replaced a misconfigured legacy setup.
−94%
Complaint rate
A publisher's complaint rate fell after list hygiene, suppression logic and send cadence were rebuilt around engagement data.
Results vary by list size, industry and starting authentication state; these figures describe the specific engagements above, not a guaranteed outcome.
31
Migrations completed
0
Revenue gaps at cutover
7 yrs
Average client tenure
11
Platforms worked in
About
A small studio in Rotterdam, doing one thing.
Morphic Digital was founded in 2018 to do the part of email marketing that most agencies subcontract or skip: the platform and infrastructure work underneath the campaigns. We stayed narrow on purpose.
We work with a small number of clients at a time, mostly on migrations and the deliverability engineering that keeps a program healthy afterwards.
We write the plan down
Every migration starts with a document naming what moves, when, and what "done" means. It gets agreed before any account is touched.
We keep a rollback open
Cutover is never a one-way door. The old platform stays reachable for thirty days, so a bad signal can be reversed rather than ridden out.
We hand it back better documented than we found it
Every account we touch leaves with clearer documentation than it had, so the next person — on your team or ours — isn't starting from zero.
FAQ
The questions we actually get asked.
If you want more detail than this, ask on the call — nothing here is the polished version.
How long does a migration take?
Seven to nine weeks for a typical program: a week of audit, two to three rebuilding, two to three running both platforms in parallel, then cutover and a month of monitoring. A program with heavy custom integrations runs longer, and we say so before starting rather than halfway through.
Will we lose revenue during the switch?
That is the thing we are paid to prevent, and it is why we run both platforms in parallel rather than cutting over in one night. Across thirty-one migrations we have not had a revenue gap at cutover. We also keep a rollback path open for thirty days afterwards.
Which platforms do you work in?
Klaviyo, Braze, Iterable, Customer.io, HubSpot, Salesforce Marketing Cloud, and raw providers such as SendGrid, Postmark and Amazon SES. Eleven in production so far. If you are moving to something we have not touched, we will tell you that too.
What does it cost?
Migrations are fixed-fee, quoted after the audit, and typically fall between €12,000 and €40,000 depending on the number of flows and integrations. The audit itself is €2,500 and is credited against the migration if you proceed.
Who owns the accounts and the documentation?
You do. We work in accounts you own under our own named logins, and the migration document, flow specifications and monitoring runbook are yours — written so an in-house team can take over without us.
Do you do ongoing work after a migration?
Only if you want it. Some clients keep us on a monthly deliverability retainer; most take the runbook and run it themselves, which is the outcome we design for.
Contact
Tell us what you are moving.
Send a few lines about your current platform and what is prompting the move. We reply with next steps, not a sales deck.