Platform move case study | Elative Solutions
← Elative Solutions
Case study · A school of healing and spiritual practice

886 of 894.Every student moved in five days.

With everything they had paid for. A school moving about 100 courses and workshops to a new platform. Weeks in, 7 percent of the access had been carried over, members were writing in about missing courses, and the new membership form was taking no money. I took over on a Sunday.

5 days
From taking over to verified complete
6,614
Course access grants, up from 578 after weeks
0
Emails sent to students by accident
0.08 s
Cached page response after the hosting move, from 1.8
Before and after

Same school. Same courses. One week apart.

Saturday 27 September
578 of 8,638
enrolments carried over after weeks of work, 7 percent. Nobody had a list of who was where.
  • Members missing 84 percent of the courses they had paid for, writing in to ask where they went
  • The membership signup form in test mode: every new payment failed, for days
  • Analytics blind since March; three conflicting email sender records on the domain
  • A 6 GB error log on a 60 GB site, the main image taking 5.4 seconds to appear
Thursday 2 October
886 of 894
people moved with every course they had paid for, 6,614 grants. 8 unclear cases held for the team to decide by hand.
  • No automated email during the move; the school wrote and sent its own relaunch message
  • Payment path proven with a real purchase on the new checkout and a real order on the old shop
  • Terms, privacy and refund pages rewritten for how the school sells today
  • Site files 60 to 21 GB, database to a quarter, 94 old addresses redirected, hosting moved

The week in between: took over on the Saturday call, read everything on the Sunday, built and tested the silent path on Monday, passed a live payment test on Tuesday, verified complete on Wednesday 1 October. The relaunch went out Thursday morning. The team kept teaching and answering students the whole time.

The scene

The instinct was to keep pushing.

Grant access by hand, answer the support emails, hope the list sorts itself out. I stopped and read everything first: the enrolment export, the payment provider, the analytics, the domain records, the server. Four layers, in this order, because a move only holds when the one below it does.

LAYER 1

The audit

Found: 578 of 8,638 enrolments moved, the membership form in test mode, analytics dead since March, three sender records, a server full of leftovers. One afternoon of reading.

Done: a reconciliation list of who has what and who is missing what, the form taken out of circulation, and a written plan with the team's decisions on it before any change.

The audit on 27 September: 578 of 8,638 enrolments carried over, the membership signup form in test mode, analytics dead since March, three SPF records, a 6 GB error log
LAYER 2

The move

Found: students with one email in the old system and another in the new one, duplicate logins, and automations that would have emailed every student the moment access was granted.

Done: one person, one record. A silent grant path, tested on our own accounts first, then members, then students, then the 243 people with no account yet. 886 of 894 verified by Wednesday.

The move: course access grants from 578 to 6,614 in five days, 886 of 894 people, zero emails sent by accident, 101 courses, a live payment test, and the day by day timeline from 27 September to 2 October
LAYER 3

The site

Found: a 60 GB site on shared hosting whose bot filter blocked Google and payment webhooks on and off, and every old course address still pointing at the old system.

Done: cleaned with a backup first, moved to hosting that caches pages, 94 redirects with every target checked live, domain under the school's control. The in-person retreats still sell on the old shop, on purpose.

The site: files from 60 to 21 GB, database from 908 to 241 MB, cached time to first byte from 1.8 to 0.08 seconds, 94 redirects, hosting and domain moved
LAYER 4

The handover

Found: no list of what was open and who decided it, which is how the first attempt stalled.

Done: a shared status document with every open item, its owner and its state; the rules written down; four dated backups; the legal pages rewritten. The team decides, the list remembers.

The handover: the shared status list with owners and states, the rules written down, four backups, and the point about students paying and not getting in
The line I would tell you straight

There is no revenue number on this page yet. Membership billing moves to the new platform in December; until then existing members stay on their old subscriptions. What I can show is that every student who paid can get in, the form takes money, and nobody got an email by accident. The platform was never the real problem.

What this means for you

The fix starts with the list.

If you are moving platforms, or you have moved and students still write in about access, the odds are nobody has a list of who has what. Students paying and not getting in is an automation problem, and it follows a school from platform to platform until somebody builds that part properly.

How this work is done. One person. I read everything before I change anything, fix what is costing money or trust right now, and the team gets a written list of what is still open and who decides it. Your team keeps teaching and talking to students.

It fits if you sell courses, trainings or retreats, have a team doing the marketing and the platform, and have nobody senior above that team.

Start here

Find out what your four layers look like.

A 45-minute funnel review. I look at your funnel from the outside before we speak and walk you through what I found.