Skip to content

Prosperity Club — case study

Prosperity Club

Prosperity Club — off WordPress, onto something that stays up

An ageing WordPress site rebuilt as a static site, then migrated without touching the client's email.

Visit prosperityclub
The Prosperity Club home page as it looks today

What the migration actually involved

620 MBMedia recovered from the old hostfive class recordings and two worksheets
19Dead links found and fixednone of them reported by anyone
1DNS records changed to roll backold site left untouched on its original host

The part that nearly went unnoticed

The cutover itself was uneventful — a DNS change, a certificate, mail left where it was. What mattered came after. Every class recording on the site was still linked at its old address on the previous host, so the moment the domain moved, all of them returned “not found”. Thirteen articles linked each other the same way. Nobody had reported it.

Those links survived the build's own link checker because they were written as full web addresses rather than site-relative paths, and the checker treated anything with a domain in front of it as somebody else's problem. That is the kind of gap worth fixing once, properly: the checker now verifies them too, so the same class of breakage fails a build instead of a visitor.

How it ran

  1. Take a real backup first

    The host's own backups turned out to be fifty-byte empty files. A full archive was pulled and verified before anything else happened.

  2. Rebuild as static

    No database, no plugins. Pages generate from typed content, so a fix lands everywhere at once.

  3. Move one DNS record

    Mail was deliberately left on the original host, so email was never in the blast radius.

  4. Then go looking for what broke

    Recovered the missing media, repointed nineteen links, and added redirects so old bookmarks and search results still resolve.