Why We Moved Lotus Sports Academy Off WordPress

Author: Vivek Chudasama, Founder, PurelyWeb Certifications: Meta Certified Front-End Developer, Google AI Professional Certificate, Google Cloud Generative AI Company: PurelyWeb, Junagadh, Gujarat

Lotus Sports Academy & Charitable Trust, run by founder Nitin Solanki, has been a PurelyWeb client for a year and a half — the original site was a custom WordPress build covering 33 sports programmes, admin-managed galleries, and live registration with marathon entry (5K/10K/21K) through Razorpay. As a thank-you for that year and a half, delivered free of cost, we rebuilt it from the ground up on Next.js and Firebase. Here's the actual reasoning, not just the announcement.

What Was Actually Wrong With the WordPress Build

Nothing was broken, exactly — it worked. But it was straining under the weight of what it had grown into. Thirty-three programmes, admin-managed galleries, and live registration is a lot of moving administrative state for a stack built around static pages and a plugin ecosystem never designed for real-time updates. Every new feature request meant either a new plugin (more surface area, more maintenance) or custom PHP bolted onto a theme that wasn't architected for it.

Why Next.js Instead of a Better WordPress Theme

A better theme fixes the symptom, not the cause. The underlying problem was architectural: WordPress's data model is built around posts and pages, not around the kind of structured, relational data an academy with 33 active programmes actually needs — rosters, registration state, gallery ownership, admin permissions. Next.js gave us a real application architecture instead of a content-management theme stretched into an application.

Why Firebase for the Database Layer

Firestore's real-time listeners are the actual reason this fits an academy site specifically. When an admin updates a programme, uploads to a gallery, or a registration comes in, the dashboard reflects it immediately — no page refresh, no cache-clearing plugin, no cron job. For a site with active admin-managed content and live registration flows, that real-time layer isn't a nice-to-have, it's the feature that makes the dashboard actually usable day to day.

What the Rebuild Actually Included

A new visual design system, not a reskin of the old theme
A real-time admin dashboard for managing programmes, galleries and registrations
A Firestore database replacing the WordPress data layer entirely
The same Razorpay-powered live registration and marathon entry (5K/10K/21K), rebuilt on the new stack

When This Migration Makes Sense — And When It Doesn't

This isn't a "WordPress is bad" post. WordPress is still the right choice for most brochure sites and content-driven businesses — it's why the majority of PurelyWeb's own work is built on it. The signal to actually migrate is architectural, not aesthetic: when a site's core value is administrative state that changes constantly — live registrations, real-time dashboards, structured relational data — and the CMS's data model is fighting you rather than helping.

Why We Did This Free of Cost

This wasn't a paid engagement. Nitin Solanki has been a PurelyWeb client for a year and a half, and this rebuild — new design, new dashboard, new database, new stack — was our way of saying thank you for that. No invoice attached. The best client relationships aren't purely transactional, and this felt like the right way to prove that rather than just say it.

Considering a Similar Move?

If your WordPress site has outgrown its plugin stack — not in looks, but in what it needs to do — that's the conversation worth having before reaching for another plugin.