Legacy rescue / platform migration
The Basement 416
WordPress rescue, Next.js rebuild.
thebasement416.com ↗The problem
The legacy WordPress + Divi + Amelia stack was slow, fragile on a 1GB burstable server, and required careful `wp-cli` hygiene just to stay online.
What we built
We rebuilt the booking flow as a custom Next.js module on Vercel. Stripe Checkout handles payment; Google Calendar handles availability; the existing GA4 property continues to receive events so the studio kept a year of historical data.
Outcomes
- ▸~80% reduction in hosting cost vs. AWS Lightsail WordPress
- ▸Amelia booking flow replaced with custom Stripe + Calendar flow
- ▸GA4 property 458220228 preserved — no reporting cliff
Stack
Next.js 15Tailwind v4Stripe CheckoutGoogle Calendar APIFirebase FirestoreVercel
Want something similar?
Most of our projects start from a pattern we've already shipped. Tell us what you need.
Start a project