Illustrative scenarios
Different starting points. The same careful questions.
These are examples of how a creator, a small shop, or a product team might plan a move. They are not endorsements or measured outcomes.
Illustrative examples only. No customer endorsement or performance result is implied.
Begin with what you already have.
A useful migration plan starts by asking what can be read safely and what must be rebuilt with a person in the loop.
A newsletter with history
Map readers, opt-outs, tags, and past issues before deciding which journeys can carry forward.Explore migration planningA shop with customer moments
Keep orders and marketing permission distinct so a purchase changes the next message without inventing consent.Explore commerceA product team with two kinds of email
Keep essential account messages separate from campaigns while using shared, current customer context.Explore product email
What to check before a first send.
The work is not finished when records import. Review the evidence that determines who may receive the next message.
Permission and exclusions
Compare opt-in provenance, unsubscribes, bounces, and complaint states before creating an audience.Review audience principlesSending identity
Check the domain and the first sending plan before using an imported audience.Review sender checksA human review point
Keep the diff, open questions, and approval together rather than hiding uncertainty behind a success message.See the review workflow
The next step
Bring the plan, not just the file.
Explore the proposed migration sequence and the questions a dry run should answer before anything changes.