Rebuilding a Legacy PHP Application as a Modern Next.js Stack: Performance and
Maintainability

The Challenge

A B2B software company had spent 12 years building a SaaS platform on a legacy PHP stack — CodeIgniter framework, MySQL monolith, and a jQuery-based frontend that had been patched and extended so many times that the term "spaghetti code" no longer felt like a metaphor. The application handled mission-critical workflows for 400+ corporate clients including inventory management, order processing, and client reporting.

The technical debt was staggering. The codebase had grown to over 1.2 million lines of PHP across 4,700 files. The average developer onboarding time was 4 months because understanding the implicit interdependencies between models, controllers, and views required tribal knowledge that existed only in the heads of three senior engineers — two of whom were planning retirement within 18 months.

From a product perspective, the situation was equally dire. Feature requests that should take days were taking weeks or months. The frontend rendered entire pages server-side, meaning even a small UI change required touching PHP logic, HTML templates, and CSS scattered across different directory layers. The mobile experience was essentially non-existent — the app was barely usable on a phone, and the CEO had lost three enterprise deals in the previous quarter because prospects demanded a modern, responsive interface.

Clients were feeling the pain too. Page load times averaged 6.8 seconds on the main dashboard, and certain complex reports took over 30 seconds to generate. A 2024 customer satisfaction survey showed "application speed" as the #1 complaint, cited by 74% of respondents. Churn was ticking upward, and the company's renewal rate had slipped from 92% to 84% in 18 months.

The VP of Engineering was blunt: "We've been living with this technical debt for years, telling ourselves we'd refactor 'next quarter.' But we finally admitted that incremental refactoring on this codebase is like trying to renovate a house by moving one brick at a time while people are living in it. We needed a complete rebuild strategy that didn't force our customers to hit pause on their operations."

Our Approach

SoniNow designed a strangler fig migration strategy that allowed the legacy PHP monolith to be incrementally replaced without ever freezing feature development or disrupting customer operations.

Phase 1: API Extraction and Standardization. Rather than rebuilding the UI first, we began by extracting the business logic layer into a clean REST API. Over 12 weeks, we identified domain boundaries, mapped entity relationships from the MySQL monolith, and built a new Node.js API layer (Express + TypeScript) that gradually absorbed responsibility from the PHP controllers. The legacy app was modified to call this new API internally, and then the new frontend could use the same API — a pattern that eliminated the need for a "big bang" cutover.

Phase 2: Next.js Frontend by Module. With the API in place, we rebuilt the frontend module by module, starting with the highest-traffic screens — the dashboard, client reporting, and order management. Each module was built as a Next.js page with React components, server-side rendering for initial load performance, and client-side transitions for subsequent navigation. The legacy PHP views continued to serve un-migrated modules, and users didn't notice the transition because both old and new frontends shared the same URL structure and authentication.

Phase 3: Data Layer Modernization. As the new API matured, we migrated from the legacy MySQL schema to PostgreSQL with a cleaner, normalized data model. The migration used database views and triggers to maintain backward compatibility with the legacy PHP code that still referenced old table structures, allowing a seamless transition over 8 weeks with zero data loss.

The Solution

The full modernization took 7 months and resulted in a completely transformed technology stack.

The Next.js frontend leveraged App Router for nested layouts, React Server Components for data-intensive pages, and incremental static regeneration for client-facing reports that didn't need real-time freshness. We implemented a design system using Tailwind CSS and shadcn/ui components, ensuring visual consistency across all rebuilt modules.

The API layer — built with Express.js and backed by PostgreSQL with Prisma ORM — served as the single source of truth for both the legacy and new frontends during the transition period. We implemented Redis caching at the API level, reducing database query load by 60% for frequently accessed data like client lists and dashboard aggregates.

Authentication and authorization were migrated from PHP session-based auth to JWT tokens with refresh token rotation, supporting the new stateless architecture while maintaining compatibility with legacy sessions through a middleware bridge.

Performance optimization was a first-class concern from day one. Images were served through a Next.js image optimization pipeline, JavaScript bundles were code-split at the route level, and we implemented streaming server-side rendering for report pages that had previously taken 30+ seconds to load.

Results

The modernization delivered transformative improvements across every dimension:

• Page load times reduced by 65% — average dashboard load dropped from 6.8s to 2.4s
• Report generation time slashed from 32 seconds to under 3 seconds — a 90% improvement
• New feature development velocity increased 3x — a feature that took 3 weeks now takes 1 week
• Developer onboarding time decreased from 4 months to 3 weeks thanks to cleaner architecture and documentation
• Mobile traffic doubled within 3 months of launch as the responsive interface unlocked mobile usage
• Customer churn reversed — renewal rate climbed back from 84% to 93% within two quarters
• Infrastructure costs decreased by 35% as the optimized Node.js/Next.js stack required fewer server resources
• Deployment frequency increased from monthly to daily with the new CI/CD pipeline and containerized architecture

"SoniNow's strangler fig approach was brilliant. We never had to freeze development, our customers never experienced downtime, and six months later we had a modern stack without the usual migration horror stories. The improvement in developer morale alone was worth the investment."
— VP of Engineering, B2B SaaS Platform

Ready for similar results?

If you're running a legacy application that's holding your business back, SoniNow's incremental modernization approach can transform your stack without stopping your operations. Contact SoniNow to discuss your application modernization strategy.