---
title: "I Will move your jQuery or legacy React front end to modern React or Next.js, page by page"
url: https://zinnhub.com/zinns/i-will-move-your-jquery-or-legacy-react-front-end-to-modern-react-or-next-js-page-by-page/
description: "Your front end still runs on jQuery, old class components or an outdated Next.js setup, and every change takes longer than it should. I move it to modern React or Next.js in TypeScript one page at a time, while the product keeps working."
published: 2026-10-01T08:14:37+00:00
modified: 2026-10-01T08:14:37+00:00
language: en-GB
---

# I Will move your jQuery or legacy React front end to modern React or Next.js, page by page

Some products work and earn money, but their front end has become hard to change: jQuery spread across templates, React class components from years ago, or a Next.js app still on the Pages Router. A full rewrite freezes the product for months. I do the other thing: old and new code run side by side, and pages move over one at a time, so there is never a big switch-over day for your users.

I did exactly this on a past project under NDA: a jQuery front end moved to React page by page while the product stayed live.

Starter gives you the plan: I read the old front end, map its pages and shared pieces, list the risks, and migrate one small page as a working sample of the approach. Standard moves up to three pages or screens. Advanced moves up to eight, builds the shared components they need, and covers them with TypeScript types for their data and tests for the main flows.

What stays: your backend, your URLs and the behaviour users know. What changes: how the code is organised, so the next feature is written once, in one place. For 14 days after delivery, I fix anything that does not work as we agreed, free of charge.

The page order and the plan are agreed in the order chat, without calls. Each migrated page ships on its own, and you get a written status note every working day.

Steps for completing your project
1. Map the old front end – I go through the templates, scripts and components, and list the pages, the shared parts and anything risky, like global state or inline scripts.
2. Agree the order – You get a written plan: which page goes first, what moves with it, and how old and new code share the product while both exist.
3. Bridge – The new React or Next.js code is set up next to the old code, with routing that sends each page to whichever side owns it.
4. Move pages one by one – Each page is rebuilt, compared with the old version and switched over on its own, so a problem affects one page, not the product.
5. Handover – The migrated pages, the updated plan for what is left, and a short note on the patterns to follow for the next pages.
