Migration
Your website on Next.js, your store on Shopify. With all rankings.
WordPresstoNext.js
View this migrationYour website sits on a platform that hardly anyone on the team can change. We move it from Webflow, Framer, WordPress or Wix to React and Next.js, a modern, AI-native stack. Online stores move to Shopify. Before anything moves, we map every old URL to a new one. That way your rankings are preserved. Afterwards the website is code that belongs to you. Your team and AI tools like Claude, Codex or Cursor work on it directly.
Where it usually gets stuck
- Every small change becomes a ticket
- A new landing page should take an hour. In the site builder it takes days, because only one person understands the structure. Campaigns start later than planned. And platform costs rise with every page.
- Your team's AI tools cannot reach the website
- Your team has long been writing text and code with Claude, Codex or Cursor. That stops at the website. A visual site builder has no code that an agent can read, test and ship. What takes minutes elsewhere stays manual work here.
- A move seems too risky for your rankings
- Your website brings inquiries through Google, so a move feels dangerous. Rightly so: without complete redirects, pages that built their positions over years get lost. So everything stays as it is, even though the platform holds you back.
Tools change faster than the rules
We use the tools that fit the task and your systems. We stay independent of any single model. When a better one comes along, we switch. Process, review and responsibility stay the same. That way your solution does not go stale with the next model.
What you get
We capture every address of your old website and map it to a new one. Pages without a successor get a deliberate target. That way no ranking is lost because a page was forgotten.
Your pages are rebuilt in React and Next.js, with fixed building blocks and automated tests. Design and content stay, the platform limits fall away. The pages load fast, on mobile too.
Text, images, blog posts, titles and descriptions all move along. We set up structured data and the sitemap anew. What was found before is found afterwards.
We move your store from WooCommerce, Wix or another system to Shopify. Products, categories and customer data move along. Every product URL gets its target, so your rankings stay.
Your marketing team maintains pages in a content management system that suits your team. Every change gets a preview before it goes live. Nobody needs a ticket for a new page.
Claude, Codex and Cursor write code, not clicks in a site builder. We set up your project so an agent can safely prepare landing pages and fixes. Tests and preview links check every change before a person approves it.
On the day of the move we switch the domain and redirects and submit the new sitemap. In the weeks after, we watch indexing, rankings and inquiries. We fix errors before they cost reach.
What stays the same in every project
- Cause first
- Problems rarely arise in one area alone, but where areas touch. We keep looking until it is clear where it comes from. Fixing a symptom is cheaper, but it comes back.
- Technology involved from the start
- We plan tracking, page structure and interfaces while the strategy takes shape. That way you do not find out only during implementation what is not possible.
- You hear the why too
- For every proposal you learn what it is based on and which path we rejected. That way you can take part in the decision and explain it to others.
A good fit if
- Your website runs on Webflow, Framer, WordPress or Wix and holds your team back
- Your online store should move to Shopify
- Your team and AI agents should publish pages themselves
- Your website brings inquiries through Google that you cannot afford to lose
Not a good fit if
- You only want a new design on the existing platform
- Your website has few pages and hardly changes
- You do not want to touch the website again after the move
What you probably want to know
That depends on the number of pages, templates and integrations. After the URL inventory we know what moves. Then you get a fixed quote. If something comes up along the way, we talk about it first.
That depends on scope. We set the schedule after the inventory, with a fixed day for the switch. Until then, your old website keeps running unchanged.
Before the move we map every old URL to a new one and set up 301 redirects. Titles, descriptions and structured data move along. After the switch we watch indexing and positions. Fluctuations in the first weeks are normal, and we check them page by page.
Yes. You maintain text, images and new pages in a content management system, or have an AI agent prepare them. Every change gets a preview link before it goes live.
You do. Code, hosting account, domain and data are in your name. You can continue with another team at any time.
Related offers
- Website relaunchNew structure and design for an existing website. Rankings and content stay.
- Next.jsWebsites and web apps with Next.js. Fast to load, easy to find, in your own code.
- SanitySanity CMS with its own studio, preview and languages. Set up for your editorial team.
- Headless CMSWhen a headless CMS makes sense, which one fits and what it costs.
- ShopifyPlan, build and connect shops. From the first theme to Plus, B2B and headless.
- Shopify integrationsConnect ERP, PIM, CRM and accounting to Shopify, with clear data ownership.
6 min read
Framer Alternative: Which Path Fits Your Website
Webflow, WordPress, custom code or Wix and Squarespace: who maintains the site, what happens to your rankings and what do you own? The comparison by what counts in daily work.
1 min read
When moving from WordPress to Next.js makes sense
Judge a migration by maintenance, editing and business requirements, rather than the age or popularity of the platform.
1 min read
Slow pages create friction before the first enquiry
Find the performance problems that interrupt your buyer's journey, then fix the causes rather than chasing a score in isolation.