Across the communities we follow, the same shock keeps landing in different forms. A host or reseller changes how they package and price a popular events plugin, and agencies start asking whether they can still recommend it to clients. Another agency's LearnDash clients refuse to renew under a forced four-plugin bundle and start looking for a competitor. Site owners whose past-events views broke on the default upcoming template ask for alternatives in the same breath as donations-plugin replacements. Creators who left a course marketplace to own their checkout discover the next pain is renewals, quiz retakes and certificates. Organisers still put meetups on a ticket marketplace while building a local collective. Plugin makers keep wiring the same LMS stacks into automation tooling — a reminder the stack is not vanishing overnight.
The common thread is dependency. Something you didn't choose piece by piece — a host bundle, a mega-suite, a reseller deal — suddenly stops being the deal you signed up for. The disagreements are real: stay and buy direct, migrate, build a custom calendar, hand clients to a page builder plus a ticket marketplace, or start clean rather than fork a bloated stack. What goes wrong is cutting over before you've checked what actually has to move.
We've sat through enough of these to know the staging copy is where the truth lives. Here's the checklist before anyone touches production.
The idea: treat the staging copy as the decision, not the rehearsal
A migration is a business decision dressed as a technical one. Licence cost and feature lists matter, but the deciding evidence is usually what breaks when you move quiz attempts, drip schedules, RSVPs or past events. Find that out on a staging copy you can throw away, not on the live site at midnight.
The checklist
1. Write down what the site does, not only what it holds
Lessons, events and pages usually export. Group enrolment codes, certificate templates, coupon rules, waitlists, past-event archives and check-in history often don't. One agency whose clients only needed events — not LMS, donations or a theme — realised the mega-bundle carried weight they never used. Another team moving LearnDash clients found a migration plugin that handled courses but needed a separate plan for attempts and certificates.
Test: list every workflow a staff member or student runs in a normal week. Anything that isn't on that list is optional. Anything that is, and that an importer skips, becomes your real cost.
2. Confirm whether buying direct is still an option
When a host or reseller drops a plugin, the vendor often still sells it on their own site. Several agencies were weighing "stay and buy direct" against "migrate everything". Direct can be cheaper than a forced bundle and less risky than a cutover, but you may lose the "one bill, one support line" convenience the host was selling.
Test: price one year of direct licences against one year of the new bundle and against a migration quote. Include support hours. The cheapest sticker price is rarely the cheapest year.
3. Check what breaks on the default templates before you blame the whole product
Past-events views failing on the upcoming template is a different problem from "the plugin is unusable". Template issues can be fixed without a migration; bundle and pricing pain usually can't. Mixing the two leads people to rip out a working calendar because one view is wrong, or to stay on a painful licence because the homepage still looks fine.
Test: on staging, reproduce the broken view with a stock theme and no custom CSS. If it still fails, it's a product issue. If it doesn't, it's your theme or a conflict.
4. Measure migration risk on the things that don't re-import cleanly
For LMS sites: quiz attempts, drip schedules, certificates, course progress, groups, coupons. For events sites: past events, RSVPs, ticket orders, check-in history, recurring series, waiting lists. Creators who already left a marketplace and got past checkout often hit renewals and retakes next — those edge cases are what a weekend migration forgets.
Test: pick five real users or five real events and walk their history on the staging copy after import. If any of the five is wrong, stop and decide whether wrong history is acceptable.
5. Decide whether "start clean" beats "fork the mess"
Agencies whose clients refused a bloated mega-bundle often preferred starting clean over carrying unused LMS and donations pieces into a new setup. Forking a heavy stack into a custom build sounds tidy until you're the one maintaining the CPT, the RSVP emails and the calendar UI. Handing clients to a page builder plus a ticket marketplace is cheaper for them and removes you from the stack — which some agencies said out loud means "we are not in a good place" when those options win on price alone.
Test: ask the client what they will still need you for after the move. If the answer is "almost nothing", you are exiting a product category, not migrating a site.
6. Run the cutover plan once on staging, including renewals and support handoff
A green import is not a cutover. Have someone buy a renewal, retake a quiz, download a certificate, RSVP to a past-and-future event pair, and file a fake support request. Note who owns the new licences and which support channel the client will use on day one. Plugin makers still shipping LearnDash and Tutor integrations are a signal those ecosystems keep moving — but your client's renewals still need a named human.
Test: the staging walkthrough is done when a non-developer on the team can complete the five actions above without asking you.
7. Keep a reversible window
DNS cuts and licence removals are hard to undo. Staging success plus a fixed rollback window — old plugin left installed but inactive, exports kept, host asked not to purge yet — turns a bad cutover into an inconvenience. Skipping that window is how "we migrated" becomes "we rebuilt under pressure".
Mistakes we see over and over
- Migrating because the reseller changed, not because the tool failed. Different problems, different fixes.
- Counting pages moved instead of workflows preserved. Progress bars and RSVP history are the quiet killers.
- Building a custom calendar or LMS over a weekend and discovering renewals, refunds and certificates in month two.
- Handing clients to the cheapest hosted combo without saying you may leave that stack.
- No staging walkthrough with a real user journey. Importers look fine until a certificate name is wrong.
Where to start if the deal just changed
If a host or reseller changed the deal, do these three things before you shortlist replacements: export everything you can; spin up a staging copy; write the workflow list from checklist item 1. Only then compare direct purchase, a lighter WordPress events or LMS setup, a custom post type, or a hosted ticket tool. The order matters more than the brand names.
Your turn
- When a host or reseller dropped a plugin you relied on, did you buy direct, migrate, or hand the client to a hosted combo — and what would you do differently?
- Which workflow failed on your last LMS or events migration: quiz attempts, certificates, drip, RSVPs, past events, or something else?
- For clients who only need events (not LMS or donations), do you still start with a big suite, a lighter plugin, or a custom CPT?
- How long do you keep the old stack reversible after cutover, and has that window ever saved you?
We read every comment. Stories from people who stayed and bought direct are as useful as the migration postmortems.
Top comments (0)