Redirects
A valid page is not enough. Preserve valuable URLs and test the real redirect response.
Check your URL map ↗WEBFLOW → NEXT.JS / BY EVERBASE
Move your site.
Keep what matters.
A practical migration system for developers using Claude Code or Codex. Start with free tools that surface the work your agent might miss.
Free to plan. Your own tools. No account required.
START HERE / FREE FIT CHECK
Is DIY the right move?
Answer eight questions about your site. This is a self-assessment, not a crawl: nothing is fetched, scanned or sent to a server.
CHECKS OVER PROMISES
Your agent can write Next.js.
The migration still needs a finish line.
CMS relationships
References, ordered lists and rich text need explicit mapping and editorial review.
Forms & scripts
Inventory platform services, load order, consent and integrations. Verify the receiving system.
Search metadata
Compare canonicals, titles, schema and sitemaps against a saved baseline.
01 / FREE PLANNING TOOL
Size the work.
See the assumptions.
This is an illustrative effort model, not a quote or market-price claim. Change the rate to yours. Nothing you enter is sent to a server.
ILLUSTRATIVE PLANNING RANGE
Calculate to begin
Discuss this scope with Everbase ↗
Includes a 15% low-end and 30% high-end contingency. Calendar time can be longer because of reviews, content work and dependencies.
Outside this model: bespoke application logic, commerce checkout, memberships, localization, manual content rewrites, asset licensing, hosting and CMS fees.
Inspect the formula and effort breakdown
These are adjustable planning assumptions, not observed delivery averages. Discovery: 16–32 hours. Templates: 6–14 hours each. Content: 8–16 hours plus 0.04–0.12 hours per page. Collections: 4–12 hours each. Integrations: 3–10 hours each. QA and launch preparation: 16–32 hours. Redesign: 4–12 additional hours per template. Add contingency, round effort up, multiply by your hourly rate, then divide by weekly capacity and round weeks up.
Very large inventories and deeply related CMS schemas do not scale linearly. Use this model to identify questions for a technical discovery, not to promise a deadline.
02 / FREE URL MAP CHECKER
Catch the wrong turns
before launch.
Paste two columns from a spreadsheet: old path, then new path. This checks your map locally, not your website. No URLs are fetched or sent anywhere.
What this catches, and what still needs a real check
The checker flags duplicate sources, conflicting destinations, self-redirects, chains and loops. Exports use 301 as a planning default for permanent page moves; the CSV is not a deployment configuration. Next.js permanent redirects use 308 by default. For static export, configure redirects on your host rather than in next.config.js.
Keep unchanged URLs out of this map. Redirect removed pages only to a genuinely relevant replacement; use intentional 404/410 responses where there is no replacement. Test each destination and the real redirect response on your chosen hosting platform. This tool cannot verify destination content, HTTP status, query handling, encoded-path normalization, regex rules or SEO outcomes.
ARCHITECTURE / MAKE THE TRADEOFF EXPLICIT
Choose how each page runs.
Build-time content.
Use static export for content that can be generated at build time. Every dynamic path needs a build-time inventory. Content changes need a new build; server features do not run in an exported site.
Request-time behavior.
Personalized pages, secure server actions, draft previews and on-demand updates need a compatible runtime. Choose the deployment adapter before committing to server-dependent features.
Small interactive boundaries.
App Router components are Server Components by default. Use Client Components for state, event handlers and browser APIs. Keep credentials and privileged data on the server.
03 / FIELD NOTES
Make the move with your eyes open.
Read the Webflow-to-Next.js field guide ↗
Choose the CMS before rebuilding the pages.
Next.js is an application framework, not an editorial workflow. List who edits each content type, what preview and approval they need, and which fields reference other records. Then choose a CMS or repository-based content workflow that supports those requirements.
Prototype one representative page with real data, including rich text, images and references. Confirm draft preview and a publish-to-live cycle before migrating all records. An export file is evidence of extractable content, not proof that relationships or editor behavior will transfer.
Read Next.js draft preview guidance ↗Protect the URL, not just the page design.
Combine a current crawl with sitemaps, analytics, Search Console and existing redirect rules. Include valuable addresses that are no longer linked in the navigation. Give each URL a destination: unchanged page, one-hop permanent redirect to a relevant replacement, or an intentional 404/410.
Check status codes, canonicals, internal links, robots rules, sitemap URLs and structured data on the new build. Keep staging out of search. After launch, monitor indexing and traffic against a baseline. Good URL handling reduces risk; no migration can guarantee unchanged rankings.
Google's site-move guidance ↗Inventory what an HTML export leaves behind.
For every form, search box, animation, CRM handoff, consent control and gated page, record what it does and how you will verify it. Vendor scripts may transfer; platform-owned services often need replacements.
Start with Server Components and add Client Components where state or browser APIs are needed. A client boundary also includes its imported modules, so keep it focused. Test keyboard access, error states, repeat submissions, mobile layouts and loading failures. A form is not finished when its success message appears: verify the receiving system gets the right record.
Understand server and client components ↗04 / TAKE IT WITH YOU
Your launch checklist.
Check items as you work. Progress lasts only in this open page; print or save to PDF to keep a copy. Refreshing resets it.
0 of 12 complete
BEFORE YOU START
A few honest answers.
Does this migrate my site automatically?
No. The working tools help you assess scope and inspect a URL map. You or your developer implement and verify the migration.
Will my SEO survive?
No tool can guarantee rankings. Build a URL inventory, preserve metadata, test redirects and compare indexing and traffic after launch.
Does the fit check scan my URL?
No. It uses only the answers you enter, processed in this page. An automated crawler is not part of this prototype.
Is Next.js the right choice for every website?
No. A content-only site may not need its application features. Compare editorial needs, interactions, hosting and maintenance before choosing. The Astro companion offers another route for content-led sites.
Will a static export keep forms and redirects?
Not by itself. Forms need a receiving service and static hosting needs its own redirect rules. Next.js server features, including Server Actions, do not run in static export. Verify your deployment plan before rebuilding.
DO IT YOURSELF, OR GET A HAND
The guide is free.
The next step is yours.
Use these resources with your own team or any migration partner. If you want help with the move, Everbase offers done-for-you migrations.
Everbase ↗Optional paid help. The guides and tools are yours to use either way.