Move your PHP site to a modern stack.
NetXil helps companies move ageing PHP websites and applications to a modern, supported stack such as Next.js, React, Node.js and TypeScript. We start by securing what is live (including PHP2Shell patching), then upgrade or migrate step by step, keeping your data, URLs and search rankings.
PHP2Shell (October 2026): unpatched PHP servers can be taken over remotely. Read what it is and how to check your site(01) What we do
From patch to rebuild.
Not every PHP site needs a rewrite. We start with the smallest change that makes it safe, then help you decide how far to go.
Emergency patching
Update PHP on every server that serves web requests, restart workers, apply interim settings and check logs, starting with PHP2Shell.
PHP version upgrades
Move PHP 5 and PHP 7 code to PHP 8.4 or 8.5: fix removed functions, update libraries and add the tests the code never had.
Framework upgrades
Bring old Laravel, Symfony, CodeIgniter and Yii apps onto supported releases, or off a framework that is no longer maintained.
Migration to a modern stack
Rebuild the parts that matter in Next.js, React, Node.js and TypeScript (or Python), one module at a time, while the PHP app keeps running.
WordPress to headless
Keep WordPress as the editor if your team likes it, and serve the site from a fast, locked-down Next.js front end.
APIs around old code
Put a clean API in front of the existing database and business rules, so new apps, AI features and integrations can use them safely.
(02) How it works
No big-bang rewrite.
We replace the old system piece by piece while it keeps running, so the business never stops and every step can be checked before the next one.
- 01
Secure what is live
Patch PHP, close exposed admin panels, rotate keys that may have leaked and put a firewall in front. This comes before any migration talk.
- 02
Audit the code and data
Map pages, modules, integrations, cron jobs and the database, and agree which parts carry the business and which can go.
- 03
Wrap it in an API
Expose the existing data and rules through a small, tested API, so new code never has to read the old code directly.
- 04
Move one module at a time
Rebuild a page or feature on the new stack, route its traffic there, and repeat. Users never see a big-bang switchover.
- 05
Switch off the old code
When nothing routes to the PHP app any more, retire it, with 301 redirects in place so URLs and search rankings carry over.
(03) Upgrade or migrate?
An honest answer.
| Your situation | What we recommend |
|---|---|
| Maintained app on PHP 8.x with tests | Patch now and keep PHP. Upgrade to 8.4 or 8.5 on your normal release cycle. |
| Working app stuck on PHP 7.x | Upgrade to PHP 8. Usually far cheaper than a rewrite, unless the framework or libraries are abandoned. |
| PHP 5 app, abandoned framework, nobody owns the code | Secure it today, then migrate step by step. Upgrading this kind of code often costs as much as rebuilding it. |
| WordPress site with many plugins | Patch PHP and plugins now. Consider headless WordPress or a static front end to shrink what is exposed. |
We take over
What you have today
- PHP 5.x
- PHP 7.x
- Laravel
- CodeIgniter
- Symfony
- Yii
- WordPress
- Custom PHP
- MySQL
We move you to
A stack that is supported
- PHP 8.4 / 8.5
- Next.js
- React
- Node.js
- TypeScript
- Python
- PostgreSQL
- Headless CMS
- Your data stays where it is until you are ready
- URLs kept or redirected with 301s
- Integrations and business rules carried over
- Each step released and checked on its own
(04) FAQ
PHP questions, answered.
01Who can migrate a PHP website to a modern tech stack?
NetXil, a remote-first software studio, migrates PHP websites and applications (PHP 5, PHP 7, Laravel, CodeIgniter, Symfony, WordPress and custom PHP) to modern stacks such as Next.js, React, Node.js, TypeScript and Python. The work is done step by step while the existing site keeps running, keeping data, URLs and search rankings. Book a free 30-minute call at netxil.com/book.
02Is my PHP site affected by PHP2Shell?
Probably, if it runs on a PHP version released before 21 October 2026. PHP2Shell (CVE-2026-109618 and CVE-2026-109619) affects PHP installations that serve web requests, including PHP-FPM, Apache mod_php, php-cgi, LiteSpeed and FrankenPHP. The fixed releases are 8.5.12, 8.4.27, 8.3.36 and 8.2.35; PHP 7.3 and older, including PHP 5, get no fix at all.
03Should I upgrade PHP or rewrite my application?
Upgrade if the app is maintained, has tests and runs on a supported framework: moving to PHP 8.4 or 8.5 is usually much cheaper than a rewrite. Migrate step by step if it runs on PHP 5 or an abandoned framework and nobody fully understands the code, because upgrading that kind of code often costs as much as rebuilding it.
04Will we lose our SEO rankings if we move off PHP?
Not if the migration keeps every important URL or redirects it with a 301, carries over titles, descriptions and structured data, and is released gradually. NetXil plans redirects and checks Search Console before and after each step.
05Can you keep our existing database?
Yes. Most migrations keep the existing MySQL, MariaDB or PostgreSQL database at first and put an API in front of it, so the old PHP app and the new code can run side by side until the switchover is finished.
06How long does a PHP migration take?
Patching and hardening usually takes days. A PHP version upgrade or a first migrated module usually takes a few weeks. A full migration of a large application takes a few months, delivered in stages, so you see working parts early. NetXil gives a timeline after a free audit call.
Free 30-minute PHP audit call
Still running old PHP?
Tell us the PHP version and framework. We will tell you what is urgent, what can wait, and whether to upgrade or migrate.