Email lifecycle after a re-platform.

A re-platform is where companies pretend to start over. They do not. They bring the list, the complaint history, the forgotten journeys, and the habit of sending at 9 a.m. because that is when the proof cleared. Salesforce Marketing Cloud, Braze, Iterable, HubSpot, Klaviyo — the names change. The week does not, unless someone holds it.

This playbook is how MBX diagnoses, builds, and runs a lifecycle after the migration. It is not a certified-partner costume. It is not a dollar menu. It is the operating sequence: map, kill, install, send, hand back.

Diagnose

Start with placement, not with a celebration send. Authentication: SPF, DKIM, DMARC, alignment, a return path that is watched. If marketing can mint a subdomain “just for a blast,” they will. Lock that in writing.

Then the file. What survived. What is a ghost from the old ESP. Which identities collide with sales-assisted mail. A list is not an asset because it is large. It is an asset because it is recent, permissioned, and still in a relationship.

Then the journeys. Most migrations copy artefacts. Welcome that still uses a test record. Winback that hammers three-year-old addresses. A product launch stream that doubles volume overnight. Draw the send graph: how much mail, from which domains, to which cohorts. The graph is the programme. The journeys are decoration until the graph is true.

Kill theatre. If a journey cannot be explained in one sentence to the VP who already owns the commercial number, it does not ship in month one. Diet first. Volume comes back when the relationship comes back.

Build

Welcome, activate, expand, revive. Those four, living, instrumented, with a stop so sales mail does not collide. Commercial sends on a calendar the business can trust. Templates legal will actually approve so time-to-launch is a number, not a complaint.

The legal path is a person. Five people touching a proof is a deliverability event: the send happens late, to the wrong overlap, in a scramble. Install the path. Then the lifecycle can move on a Tuesday.

Run

The weekly is an operating room, not a readout. What is locked. What is slipping. Which stream is poisoning the domain. Placement, complaint, unsub, time-to-launch, and the commercial number you picked on day one — SQL, booking, RPR. Opens are a rumour.

Throttle is not timidity. After a merge or a re-platform, the domain needs a diet. A launch that doubles volume is a reputation event. Grown programmes survive quarters because someone can say no.

Seed tests are a flashlight. Use them. Do not manage the programme to them. Hold a basket: placement on the domains that matter to your file, complaint, unsub, and the number the business already believes. When they move together, you know something.

Hand back

If the PMM cannot hold the calendar when the principal is quiet, you rented a specialist. Independence is a metric from month one. Who shipped a week unassisted. Which templates legal already trusts. Which stop rules are written.

The stack stays yours. Fluency in Salesforce Marketing Cloud or Braze is transferable if it was documented as configuration, not folklore. MBX does not keep a shadow copy of the calendar as leverage. The operating system you leave is the company’s.

Write when the re-platform is already serious. Team, stack, constraint, 90-day outcome. What “held” looks like might be launch email in thirty-six hours and placement that is no longer weather. Start a mission lists what to send. The form is on Contact.

A note on sales-assisted mail, because it is where lifecycles die. SDR sequences, product-led triggers, and brand journeys sharing a domain without a stop. The contact receives three truths in a day. Placement pays for that. Split the streams or accept the tax. There is no journey that repairs a collision you refuse to name.

Reporting the VP will actually open: one page. Placement on the domains that matter. Complaint. Unsub. Time-to-launch. The commercial number from the brief. If a metric needs a TED talk, it does not belong in the weekly. Finance can see the monthly. They should not need a guide to the weekly.

What to stop after a re-platform: buying lists to “fill the new ESP.” Winback that is harassment. Every PMM minting a journey. Dedicated IPs as a personality. A celebration send in week one. Opens as revenue. A partner scorecard instead of a send graph.

What to start: a diet. A map. Authentication that marketing cannot casually break. Four living sequences. A legal path. A clock on launch mail. A person who can kill a stream on a Tuesday. That person is the programme. The ESP is a tool.

Multi-brand files make this slower. Three flags, one stack, guests who are members of more than one property. Identity is the work. If the merge lied, the journey will lie. Hospitality and retail learn this expensively. SaaS learns it when trial and expansion share a from-name with a newsletter nobody asked for.

Compliance sits here when counsel already owns the claims — health-system member mail, bank marketing, anyone with a preference center. Field locks. Claims lists. Fundraising that cannot borrow a member from-name. The playbook does not change shape. The stop rules get sharper. See the healthcare sector and the compliance note. Counsel in the week, not a lecture.

A diagnostic mission uses this playbook in four to eight weeks: map, kill, architecture, 90-day plan, instrumented stack. A retainer stays to run. Embedded stays until the PMM is unassisted. Pretending one is the other is how programmes rot. Method has the models. This page has the week.

Tuesday, in practice: the send plan is locked or it is not. If it is not, the weekly names why — legal, product, a collision with sales. If the reason is “we were busy,” the programme is still a queue. Busy is not a constraint. A missing legal path is. Install the path once.

Wednesday: QA. The version that still sounds like the company. Preview text. The link that does not dump a guest into a dead property ID. The suppression that still matches the preference center. This is unglamorous. It is also deliverability, revenue, and counsel in the same hour.

Thursday: the commercial send or the journey change ships. Time-to-launch is recorded. Not as a complaint. As the number. Friday: the page. Placement, complaint, unsub, the commercial metric. What dies next week. Who owns it. Then the week can end. Most teams never end the week. They overflow it into Monday.

Re-platforms fail in month two when someone “just needs a blast for the event.” The event is not the exception. The exception is the programme. Write the rule: events enter the calendar or they do not ship. Product launches throttle or they wait. The ESP will not enforce this. A person will.

If you are reading this because the last migration was a museum, send the constraint and the stack. Do not send a brand book as a substitute. The lifecycle does not care about the brand book until the graph is true. Then the brand book can live in the templates. Not before.

Related: the B2B SaaS case is lifecycle after re-platform, anonymized. The deliverability note is the operating system underneath. The missions catalog lists ESP migration and lifecycle rebuild as shapes. Neither is a named client. Neither is a rate card.