PHP2Shell, disclosed on 21 October 2026, is the most serious PHP flaw in years, and Cloudflare has already seen attacks. Only PHP 8.2 and up get the fix, so a site on 7.x, 8.0 or 8.1 cannot be patched where it stands. Don't worry: we rebuild your public site in Next.js and move whatever PHP stays behind it to PHP 8.4, all in 7 days. Read the latest report.
Our PHP to Next.js migration services in USA and UK companies are for websites that live on search traffic: marketing sites, stores, listings, publishers and lead-gen pages. You want a fast, modern front end, but you cannot afford to lose Google rankings. Next.js renders pages on the server, so search engines still get full HTML.
We move the PHP-rendered front end to Next.js with the App Router and React Server Components. Product, blog and landing pages are pre-built or cached with incremental static regeneration, metadata and sitemaps come from Next.js itself, and images go through next/image. Your PHP code can keep running as a JSON API or headless back end, upgraded to PHP 8.4, or we can replace small bits of it with Next.js route handlers.
We are an Indian web development company with more than a decade of hands-on work. Our team works hours that meet the US East Coast and the UK, and we track rankings and Core Web Vitals with you after launch.
Why move a PHP site front end to Next.js
Plain React is great behind a login. Public pages that must rank need HTML from the server, fast load times and clean metadata, which is what Next.js is built around.
SEO kept, speed gained
Pages are rendered on the server or built ahead of time, then served from a CDN, so Google sees full content and visitors get quick first loads.
Fresh content without slow pages
Incremental static regeneration rebuilds a page in the background when prices or posts change, so pages stay fast and up to date.
One React codebase for the whole site
Public pages, account areas and small server tasks live in one Next.js project with shared components and TypeScript.
What our Next.js migration delivers
- PHP templates rebuilt as Next.js pages with the App Router
- Same URLs, titles and meta tags, 301 redirects for any that change
- Server rendering, static generation or ISR chosen page by page
- PHP back end turned into an API and upgraded to PHP 8.4
- Sitemap, robots and structured data generated by Next.js
- Image optimisation with next/image and font loading with next/font
- Forms posting to route handlers or your PHP API
- Hosting on Vercel, AWS or a Node server you control
Our 7-day Next.js rebuild plan
Day 1: SEO and page audit
We crawl your site, record every URL, title and ranking page, decide how each one renders and fix scope and price.
Days 2-4: Build the Next.js site
Layouts, components and pages in the App Router, data from your PHP API on 8.4, metadata matched to the old pages.
Days 5-6: Crawl and speed checks
We crawl staging to compare URLs and tags with the old site, test redirects and measure Core Web Vitals.
Day 7: Launch and watch rankings
DNS moves to the Next.js site, we submit the sitemap in Search Console and keep an eye on traffic and errors.
PHP site vs Next.js site
How a server-rendered PHP website compares with the same site on Next.js.
| PHP-rendered site | Next.js site | |
|---|---|---|
| Rendering | PHP builds HTML on each request | Server, static or ISR per page, with caching |
| Speed | Depends on server and database each time | Pre-built pages served from a CDN |
| SEO | Fine, but meta tags often hard-coded | Metadata API, sitemaps and full HTML |
| Interactivity | jQuery added page by page | React components where needed |
| Back end | Logic tied to templates | PHP 8.4 API or headless CMS behind it |
| Images | Served as uploaded | Resized and lazy-loaded by next/image |
Why trust us with your Next.js move
Most traffic loss after a rebuild comes from changed URLs and missing tags. We treat SEO as part of the build, not an afterthought.
Every ranking URL accounted for
We crawl the old site before we start and the new one before launch, and match each URL, title and canonical tag so nothing drops out of Google by accident.
Fixed price for front end and API work after a free audit.
NDA before we access your code, hosting or Search Console.
Next.js migration for US and UK websites
We offer this to businesses in the United States and the United Kingdom whose PHP website brings in leads or sales and feels slow next to competitors. Our hours overlap with the US Eastern day and UK office time, and every message gets a reply the same day.
Working with our offshore Next.js team costs much less than a local agency, with a fixed price, an NDA and one project lead who reports progress daily.
Official sources: PHP supported versions · Next.js
Frequently asked questions
Straight answers about our PHP to Next.js Migration service.
For most small and medium sites, 7 days from audit to launch. Large sites with thousands of templates get a phased plan, with the key sections live on Next.js within the same 7 days.
Not if the move is done carefully. We keep URLs and meta tags, render pages on the server, add 301 redirects where needed and check Search Console after launch.
No. Many clients keep PHP as an API or headless CMS behind Next.js. We upgrade it to PHP 8.4 so it is patched against PHP2Shell.
If pages must rank or load fast for visitors, Next.js. If the app sits behind a login, plain React is often enough and simpler to host.
Vercel is the easiest, but we also deploy to AWS, a VPS with Node or a Docker setup, depending on your budget and IT rules.
Yes. We work within US Eastern and UK hours, reply the same day, sign an NDA and agree a fixed price before starting.
Is your PHP app still on an old version?
Send us the URL or the repository. We check it for the PHP2Shell flaw and old code for free, and tell you what a 7-day migration looks like.
Get a free migration audit