[ WORDPRESS → NUXT ]
Leave WordPress. Keep what it earned you.
The hard part was never the framework. It's moving without freezing the content or getting stuck halfway.
- every indexed URL mapped
- old site live as fallback
- no editorial freeze
- rollback is one click
- fixed price after the audit
- EU data residency
Upkeep
The cost you feel is the interruptions, not the invoice
A WordPress site does not get expensive in one go. It gets expensive because somebody has to stop what they are doing, roughly once a month, to update things nobody chose — and because every one of those rounds can break the site of a client who is waiting on something else.
WordPress
12rounds of updates a year
- Plugins release on their own schedule, not on yours
- Tested in production, or on a staging somebody has to maintain
- Rollback means restoring a database
- A PHP bump can strand a plugin the site depends on
Nuxt or Elysia + JAMflow
2–4rounds of updates a year
- Fewer moving parts, and no plugin you didn't choose
- Tested on a branch with its own preview URL, before anything ships
- Rollback is the previous deploy, and you press it
- The upgrade plugin patches what is mechanical and flags the rest
These are our numbers, not a study. A WordPress site with a dozen plugins asks for attention roughly monthly, because every plugin ships on its own schedule. A Nuxt or Elysia project on this stack asks every three to six months, and the upgrade plugin does the mechanical part of each round. Yours will differ — the audit says by how much.
Three steps, and you can stop after the first
The audit is a deliverable, not a sales call. You get a written plan with cost and time, and it's yours whether the rest happens or not — which is also what makes a fixed price possible afterwards.
Audit
We read the site end to end — plugins, content model, integrations, indexed URLs, what actually breaks in production. Out comes a written plan with an estimate of cost and time, and a scope precise enough to price.
- one site, no commitment
- plugin, content and URL inventory
- written plan + fixed-price scope
Traffic
No URL gets dropped in the move
This is the objection that stops most WordPress migrations, and it deserves a real answer rather than reassurance. Everything the search engines know about the site is inventoried before a single page ships, and we prove it with a crawl of the new site against the old one.
- The map comes first, not last
- Every indexed address gets a destination before anything is built. Redirects ship with the code, so they are reviewable, testable and revertible like everything else.
- A crawl diff you can forward to the client
- The new site is crawled and compared to the old one — status codes, canonicals, titles, structured data. If something moved that shouldn't have, it shows up in a document, not in next month's analytics.
- The old site stays up until the curve is flat
- WordPress keeps serving behind the proxy after go-live. If the traffic curve dips where it shouldn't, going back is a configuration change, not a rebuild.
What you end up with
A standard Nuxt project, not a thing only we can run
The point of the move isn't the framework — it's that afterwards the site is readable, testable and revertible, and nobody has to negotiate with a plugin they didn't write.
- Nothing proprietary in the way
- Plain Nuxt on Nitro. Any Nuxt developer can take it over, and it deploys anywhere Nitro deploys — including somewhere that isn't us.
- Content in git, editing where it belongs
- Text and media are versioned with the code, and the people who publish keep an editor. Which editor depends on who publishes — that's a decision per project, not a decision for life.
- Rollback is one click, and it's yours
- Deploys are atomic. Going back means re-pointing at the previous build, not restoring a database at two in the morning.
- Fast because there's less of it
- No plugin stack executing on every request. Pages are rendered ahead of time where they can be, and the ones that can't run on infrastructure you can see the bill for.
What it costs
The audit is free. The project is a fixed price. The hosting is on the price list.
You shouldn't have to book a call to find out what something costs. The audit costs nothing and the plan is yours to keep. The project is quoted as a fixed price once the audit says what's actually in the site — that's the whole reason the audit exists.
See the price list →- Audit — free
- One site, read end to end. You get a written plan with an estimate of cost and time, and you keep it whether we work together or not.
- Migration — fixed price, quoted after the audit
- Not an hourly estimate that drifts. The audit is what makes a fixed price possible, because by then we know how many templates, how many integrations and how much content actually move.
- Hosting — metered, CHF 0.01 per RU-hour
- Compute is billed per Resource Unit per hour, storage per GB, egress per GB by zone. Published rates, the same ones on the pricing page. A site that gets less traffic in August costs less in August.
- Not in it
- Third-party licences the project needs, your domains and mailboxes, and content writing. We say so up front so nothing arrives as a surprise line.
Frequently asked questions
The ones that come up in the first call, answered here so the first call can be about your site instead.
Ask us something else →How long does it take?
For a marketing site of roughly 40 pages, five templates and a couple of forms: five to seven weeks from kickoff to go-live, redirects included. Add a shop, a private area or a custom integration and you're at three to five months. The audit says which one you are before you commit to anything.
How much downtime is there?
None that a visitor sees. WordPress serves until the switch and stays reachable behind the proxy afterwards, so the change is a routing change rather than a window with the lights off.
What replaces the WordPress admin for the people who publish?
It depends on who publishes. A marketing team that wants to edit pages visually gets Nuxt Studio; a project where the data model and the approval flow are the hard part gets Payload; content that is really structured data can live in Postgres directly. The Nuxt frontend is the same behind all three, so this is a per-project decision and not a permanent one.
Can we keep WordPress for part of the site?
Yes, and it's a common first step for cautious clients. WordPress can stay as a headless content source for one section — usually the blog — while everything else runs on Nuxt. Nothing about that decision has to be permanent either.
What do we have to do while it happens?
Answer questions about the parts of the site nobody documented, and decide the things that are yours to decide. You don't need a developer: if all you have is a design, hand us the Figma and we build it. If you do have developers and want them in the repository, they're welcome from day one — that's how the knowledge stays with you.
Who actually does the work?
We do, and we're also the cloud it runs on afterwards — there's no third party to coordinate when something needs fixing. If you came here through an agency, they keep the project and the relationship and we sit behind them.
If you're an agency
You have a fleet, not a site
The economics change once there's more than one. One shared base instead of ten codebases, one patch instead of ten afternoons, and a way of working together that leaves the client relationship where it is.
How we work with agencies →If it's your own site
Send us the one that hurts
You don't need an agency in between. We read the site, write the plan, do the move and run the hosting afterwards — and the plan is yours to take elsewhere if you'd rather.
Tell us about the site →Send us one WordPress site.
Pick the one that costs you the most time. We read it end to end and send back a migration plan with an estimate of cost and time — free, and yours to keep whether you work with us or not.