Access and inventory
Confirm access to the current site, hosting, domain and connected tools. List the pages, templates, files and forms before anything is planned.
Migrate your website to Next.js without losing what works.
A scoped move from your current platform. Inventory the site, map its URLs and integrations, then launch with redirects, checks and a rollback plan.
Source-site inventory / Redirects / Rollback
The scope
A scoped migration.
Not a conversion.
Moving platforms means rebuilding the site in code and moving what matters. Nothing converts automatically.
Map pages before you move themA migration starts with access and an inventory of the current site. We map its content, assets, URLs, metadata, forms, CMS behaviour and integrations, then rebuild in Next.js and move what should be kept. Useful parts of the current site, such as pages that already answer buyer questions, are preserved where appropriate.
A business with a working website on a platform that holds it back, and a reason to move that can be stated plainly. Every source platform is qualified first. Some content exports cleanly. Some behaviour has to be rebuilt.
Content and asset mapping
Decide what moves, what is merged and what is retired. Record where each page and file goes, and who approves the change.
URLs and redirects
Keep useful URLs where possible. Map each changed URL to its new destination and test the redirects where they will actually run.
Metadata and structured data
Carry over titles, descriptions, canonical tags and structured data that still describe the visible page. Review each one rather than copying it blindly.
Forms, CMS and integrations
Rebuild forms and editing behaviour, then reconnect analytics, a CRM and other agreed tools. Test each submission path end to end.
Staging, launch and rollback
Review the rebuilt site on staging, agree the acceptance checks and keep a way back to the previous site until launch checks pass.
The inventory
Map everything
before it moves.
Each part of the current site gets a record, a destination and a check at launch.
See the migration stepsContent
What we record: Pages, posts and reusable blocks, with owners and whether each one moves, merges or retires
How it is checked at launch: Every kept page exists on staging with approved copy
Assets
What we record: Images, documents and downloads, and where each one is linked from
How it is checked at launch: Linked files open and images display at the intended size
URLs
What we record: Current URLs, including pages with backlinks or search traffic where that data is available
How it is checked at launch: Each changed URL redirects once to its agreed destination
Metadata
What we record: Titles, descriptions, canonical tags and structured data for each kept page
How it is checked at launch: Values match the visible page and canonical tags point to the right URL
Forms
What we record: Fields, validation, consent text and where each submission goes
How it is checked at launch: A labelled test submission reaches the agreed destination
CMS behaviour
What we record: Who edits what, with drafts, previews, scheduled content and roles
How it is checked at launch: Editors can complete their usual tasks on the new setup
Integrations
What we record: Analytics, consent rules, CRM and other connected tools
How it is checked at launch: Each tool receives the expected data in a controlled test
Deliverables and inputs
What you receive.
What we need from you.
The migration is scoped around both lists. Access and approvals come first.
How delivery worksWhat you receive
- A source-site inventory and content map
- A URL map with agreed redirects and canonical destinations
- The rebuilt site on staging, with forms and integrations connected
- Launch acceptance checks agreed in advance
- A rollback plan and a schedule of post-launch checks
- A handover covering hosting, editing and maintenance
What we need from you
- Admin access to the current site, hosting, domain and DNS
- Content, media and form exports where the platform allows them
- Analytics and Search Console access, if available
- A list of connected tools and the people who own them
- Someone who can approve what moves, merges or retires
The process
Six stages.
One controlled launch.
Nothing switches over until the rebuilt site passes the checks agreed at the start.
How engagements workAccess and audit
Confirm access and qualify the source platform. Note what can be exported and what has to be rebuilt.
Inventory and map
Record content, assets, URLs, metadata, forms, CMS behaviour and integrations, each with a destination.
Rebuild on staging
Build templates and components in Next.js, move approved content and reconnect the agreed integrations.
Acceptance checks
Test redirects, forms, metadata, links and priority journeys on phone and desktop against the agreed list.
Launch with a way back
Switch over at an agreed time, with the previous site kept restorable until the launch checks pass.
Post-launch checks
Recheck redirects, forms, analytics and crawl errors after launch. Compare available search data over meaningful periods.
An example
One page,
checked end to end.
A service page with backlinks moves to a new URL. It needs a redirect, a canonical tag that matches the new address and updated internal links. Checking that one page end to end shows whether the redirect map works before every page moves.
Scope and availability
A migration is a scoped rebuild, not an automatic conversion. Source platforms, exports, integrations and hosting are qualified per project. Redirects are tested where they will actually run, which depends on the hosting setup. Rankings, traffic and enquiries are not guaranteed after any migration.
How SEO work is scopedCan you convert our site to Next.js automatically?
No. A migration rebuilds the site in Next.js and moves the content and behaviour worth keeping. Some content can be exported. Templates, forms and integrations are rebuilt and tested.
Which platforms can you migrate from?
We qualify each source platform during discovery, based on access, export options and how the current site is built. We do not assume every platform can be moved the same way.
Will we lose search traffic?
Any migration carries risk to search visibility. URL mapping, redirects and metadata checks are planned so useful pages are not dropped. Rankings and traffic are not guaranteed after a move.
What happens if something goes wrong at launch?
The rollback plan is agreed before launch. It names what triggers a rollback, who decides and how the previous site is restored.
Will moving to Next.js improve our rankings?
Not by itself. A framework does not decide rankings. A migration is justified by what the current platform prevents, such as editing, integrations or page structure.
Tell us what you are
moving away from.
Share the current platform, the site and the tools it connects to. We qualify the migration and agree the scope before any work starts.