Gatsby to Next.js
For Gatsby sites with slow builds or plugins that no longer get updates.
From$9,500
Typical timeline6–10 weeks
- Your CMS or Markdown kept
- Trailing slashes and every route matched
- Covered by our SEO migration guarantee
Gatsby to Next.js, with every URL kept
We move your Gatsby site to Next.js, reuse your React components where we can, and keep your content in your current CMS or Markdown. We match every URL, including Gatsby’s trailing slashes, so nothing that ranks moves without a redirect.
Who this Gatsby to Next.js migration is for
A good fit
- Gatsby sites with long build times or plugins that no longer get updates
- Teams that want a React framework with frequent releases and a large ecosystem
- Sites sourcing content from Contentful, WordPress, Sanity, or Markdown
- Teams whose developers already work in Next.js elsewhere
Probably not a fit
- Small Gatsby sites that build fast and rarely change, where staying is cheaper
- Teams without a developer to own a Next.js codebase after launch
- Sites that mainly need easier editing, where a hosted builder or WordPress may fit better
Why teams move from Gatsby to Next.js
Gatsby still works and still gets releases, but far fewer than it used to. Most teams move when a plugin or build problem starts costing time.
Gatsby has been part of Netlify since 2023
Netlify acquired Gatsby in February 2023 and later wound down Gatsby Cloud. The Gatsby framework itself is still maintained.
Releases have slowed
Gatsby’s latest stable release, 5.16.1, shipped on February 10, 2026. Next.js released version 16.4.3 on October 23, 2026.
Plugins for everything
In one large migration covered by Vercel, the team found Gatsby pushed all data through GraphQL and leaned on a plugin for almost everything. Moving to Next.js cut their build times by 85%.
What moves from Gatsby to Next.js
React components carry over with changes. Gatsby’s GraphQL data layer and plugins are replaced with Next.js equivalents.
| Item | What happens | How we handle it |
|---|---|---|
| React components | Moves unchanged | Reused with the changes Next.js needs, so the site looks and behaves the same. |
| GraphQL page queries | Rebuilt | Replaced with Next.js data fetching that reads from the same content source. |
| Content source | Moves unchanged | Your CMS or Markdown and MDX files stay as they are. We connect them to Next.js directly. |
| Images | Moves, with changes | gatsby-plugin-image is replaced with the Next.js Image component, which resizes and optimizes images automatically. |
| Generated pages | Rebuilt | Pages created in gatsby-node are rebuilt as Next.js routes with the same addresses. |
| Plugins | Rebuilt | Each Gatsby plugin is replaced with a maintained package or a few lines of code. We agree on each one with you before work starts. |
Redirects and URLs
Where Gatsby to Next.js moves lose traffic
Most Gatsby URLs can stay the same in Next.js. The details below are where that’s won or lost.
Trailing slashes
Gatsby 5 adds a trailing slash to every URL by default, and Next.js removes it by default. We match your current format so every address stays the same.
Generated pages
Blog pagination, tag pages, and other pages created in gatsby-node are rebuilt with the same paths.
Image addresses
Gatsby serves processed images from its own paths. Images that other sites link to keep working or get redirects.
Old redirects
Redirects defined in Gatsby or your host’s config are moved into Next.js.
Complete pages for Google
Google gets the full HTML of every page on the first request, with no wait for JavaScript.
Keep your CMS, or change it
Most Gatsby sites already have a content source worth keeping. We change it only if it’s holding you back.
Keep your current CMS
Contentful, WordPress, Sanity, or Markdown stay as they are. The lowest-risk move, and the cheapest.
Sanity
A hosted content platform with real-time editing. Strong fit for marketing teams that reuse content across pages.
Payload
An open-source CMS that runs inside the Next.js app. Strong fit when you want one codebase and full data ownership.
How a Gatsby to Next.js migration works, step by step
01
Quote
Send your site. We review it and send a quote and timeline within one business day.
02
Build
We map every old page to its new address, rebuild your templates, and move content, images, and SEO on a private preview site you can check.
03
Launch
We compare the old and new sites page by page, point your domain to the new site, tell Google about the new pages, and test each redirect once it’s live.
04
Monitor
For 90 days we watch which pages Google indexes and how much traffic your moved pages get. Anything our work caused, we fix at no cost, with reports at 30, 60, and 90 days.
How much does a Gatsby to Next.js migration cost?
Send your site and we’ll quote it within one business day.
Every migration includes
- Content and images moved
- Your current design rebuilt on the new platform
- SEO titles and descriptions carried over
- Every ranking page mapped to its new address
- A private preview to review before launch
- Launch handled, including pointing your domain
- 90 days of search monitoring
- Our SEO migration guarantee
“From” is the starting price for the kind of site described. Prices depend on your site’s size and setup. You get a quote before any work starts, and we don’t bill by the hour.
What we guarantee, and what we can’t
No one can promise how Google will rank your site after a move, including us. What we can promise is the work that protects your rankings, done carefully and put in writing.
Ask us about the guaranteeWhat no one can promise
Google decides rankings, not us. Even a careful migration can cause some movement while Google recrawls the new site and works out what changed, and it can take a few weeks to settle.
Google also changes how it ranks sites throughout the year. If an update shifts your traffic, that isn’t something any migration team controls. Anyone who guarantees your rankings is promising something they can’t deliver.
What we do promise
We take every precaution we know of, and we stay accountable after launch.
Every page we can find gets a new home. We collect old addresses from your sitemap, Google Search Console, analytics, and links from other sites. Each one gets a destination: the matching page, the closest match, or a removal you’ve agreed to. You see the full list before launch.
Nothing is removed by accident. Pages you choose to retire are removed on purpose. If any other old link stops working after launch, we fix it.
We watch for 90 days. After launch we track which pages Google indexes, any errors it reports, and traffic to the pages we moved, and we send you a report at 30, 60, and 90 days.
If it’s our mistake, we fix it for free. If something we missed or broke causes a problem in those 90 days, we fix it at no cost.
What it doesn’t cover
The guarantee covers our work. It doesn’t cover Google algorithm updates, content you change after launch, pages removed at your request, or problems caused by your host, third-party plugins, or other vendors.
When you should stay on Gatsby
Gatsby 5 still gets releases and runs on React 19 and Node.js 24. If your site builds quickly and your plugins work, there’s no urgency to move. If only one plugin is causing trouble, replacing that plugin costs far less than a full migration.
Ask if you should stay on GatsbyGatsby to Next.js questions
Common questions about moving from Gatsby to Next.js. If yours isn’t here, send us your site and ask. You’ll hear back within one business day.
Get a migration quoteIs Gatsby dead?
No. Gatsby 5 is still maintained, with support for React 19 and Node.js 24, but releases have slowed. Teams usually move when slow builds or aging plugins get in the way.
Will our URLs change?
Not if we can help it. We match Gatsby’s trailing slashes and rebuild every generated page with the same path. Anything that does change gets a one-to-one redirect.
Do we have to change our CMS?
No. Most Gatsby sites keep Contentful, WordPress, Sanity, or Markdown. We connect it to Next.js directly.
Is there an official migration guide?
Next.js used to publish a Gatsby migration guide but no longer does, so each move is mapped from your site’s actual queries, plugins, and routes.
Why does this start at $9,500?
It covers rebuilding your data fetching, routes, and plugins, plus setting up or reconnecting your CMS with live preview. Smaller sites that keep their CMS often take less time, and your quote reflects that.
How long does it take?
Most Gatsby sites with up to 25 page templates take six to ten weeks.
Find out what your Gatsby to Next.js migration will cost
Send us your Gatsby site. We’ll review it, count the pages, and reply with a quote and timeline within one business day. It’s free, with no obligation.
Get a migration quote