Insight / Software development
Published
Migrating away from PHP: choosing the right parts of a new stack
A practical comparison of Supabase, Netlify and Cloudflare for teams planning a move from a PHP application.
A PHP application may still be doing its job well. The reason to change is usually more specific: slow releases, difficult hosting, growing maintenance costs, or a product that needs different ways to handle data and traffic. Start with that reason. It will tell you which parts of the system need to move and whether a full rewrite is justified.
Supabase, Netlify and Cloudflare often appear on the same shortlist. They solve different problems, and they can work together. None is a drop-in home for a conventional PHP application. If your current site renders pages and runs business rules in PHP, plan how those responsibilities will be rebuilt or retained during the transition.
Three providers, three different roles
Supabase is a backend platform. Each project has a PostgreSQL database, with authentication, file storage, realtime features and TypeScript Edge Functions available around it. It suits teams that want a managed data layer and standard SQL access. The trade-off is migration work: a MySQL schema and its queries may need conversion to PostgreSQL, while PHP endpoints still need a new home or replacement. Supabase provides a MySQL migration guide and platform documentation to help scope that work.
Netlify is a deployment and web application platform. It can build and deliver a frontend through a global CDN, give reviewers deploy previews, and run serverless, edge, background and scheduled functions. Its current platform also includes a managed database and blob storage. That is useful when a team wants the website and its smaller backend tasks to move together. A PHP application with long-running processes, complicated sessions or substantial server-side rendering needs its execution model reviewed carefully before choosing this route. See Netlify’s platform primitives and Functions documentation.
Cloudflare offers compute and data services at the network edge. Workers can serve static assets and APIs; D1, KV, R2 and Durable Objects address different data and state needs. It is a flexible fit for globally distributed applications, but choosing between those stores takes design work. D1 uses SQLite semantics, for example, so moving a MySQL application there calls for more than copying tables. Read the Workers overview and storage options guide before treating it as a single replacement for a PHP host.
Support commitments differ by plan. Supabase pricing lists community support on Free, email support on Pro, an email response SLA on Team, and an uptime SLA on Enterprise. Netlify pricing lists priority email support on Personal, while Enterprise advertises a 99.99% uptime SLA and dedicated 24/7 support. Cloudflare’s Workers SLA sets a 99.99% monthly objective for covered enterprise customers, with exclusions and a service-credit process. Compare the contract for the workload you intend to run, including dependencies such as databases and storage, before putting an SLA in a project plan.
Make the move in stages
First, map what the existing application actually does: page rendering, authentication, sessions, database queries, file uploads, email, scheduled jobs, payments and integrations. Record where each responsibility will live in the proposed stack. This often reveals that the database and frontend can move at different times.
Next, choose a representative workflow and build it end to end. Test permissions, data validation, error handling and performance with real shapes of data. If the database engine changes, rehearse the migration on a copy, then check record counts, constraints and important reports. Keep a backup and a clear cutover plan.
Finally, release in slices where possible. Preserve working URLs or set redirects, monitor failures and maintain a route back while the new system proves itself. Our software development process describes how we turn those decisions into reviewable steps.
The useful question is which parts of the current system need a new shape. Choose the services after you can answer that.