The reason people stay too long on a setup they have outgrown is rarely the price. It is the fear that something breaks during the move and a customer notices.
That fear is reasonable. It is also manageable, and the way you manage it is by never switching anything until the replacement is demonstrably working next to it.
What actually moves
Contacts, with their history. Not just email addresses. Tags, custom fields, subscription status and the date each person gave consent. That last one matters: if you lose consent dates, you lose the ability to prove you were allowed to email someone.
Mailings and automations. These get rebuilt rather than copied, because no two systems model automations the same way. That is a feature, not a cost: most people discover that a third of their automations were doing nothing.
Products, orders and active subscriptions. Subscriptions are the delicate one. Done properly, existing customers do not re-enter payment details and their renewal dates do not shift.
Content and links. Pages, posts, and crucially the redirects, so the link in an email you sent two years ago still lands somewhere sensible.
Courses and members. Content, enrolments and progress, so people log in and carry on where they were.
What usually goes wrong
Sending reputation. This is the one that bites. Your domain has a reputation built with your old provider, and sending from new infrastructure resets part of that. Without SPF, DKIM and DMARC set up correctly on the new side, and without warming up the sending volume, your first mailing lands in spam and you conclude the new platform is broken. It is not. The DNS is.
Timing the switch during a campaign. Do not migrate in the middle of a launch. Obvious in hindsight, routinely ignored.
Forgetting the quiet integrations. The webhook that posts to a spreadsheet, the Zap nobody remembers setting up, the form embedded on a partner site. Make a list before you move, not after something stops arriving.
The sequence that works
- Inventory. Every tool, every connection, every automation that matters. An afternoon, and it prevents most of the surprises.
- Build alongside. The new environment goes up while the old one keeps running. Nothing points at it yet.
- Move the data. Contacts, products, content. Verify counts, not vibes: if you had 4,182 contacts, you should have 4,182.
- Rebuild the automations that earn their keep. Test each one with a real address before it goes anywhere near a customer.
- Set up sending, then warm it. DNS records first, then a small mailing to your most engaged segment, then scale.
- Switch the domain. At a quiet moment, with redirects in place.
- Keep the old system for a month. Read-only, as insurance. Cancel it when you have stopped thinking about it.
How long it takes
For a typical setup, with a few thousand contacts, a shop and a course: two to four weeks of calendar time, of which your own involvement is a handful of hours. Most of that calendar time is deliberate waiting, checking and warming, not work.
Anyone who promises you a same-day migration of a live business is either doing less than they said or skipping the warming.
See what our migration service covers, which is included with the launch offer.