Book a Call
MIGRATIONS

Get off the platform you have outgrown.

Every platform eventually tells you no. A page it won't let you build, a feature it doesn't support, a load time it can't reach. Moving to code you own means nothing is deciding that for you.

Book a Strategy Call Find your platform
THE PART YOU ARE WORRIED ABOUT

You keep the rankings.

That's the real question behind every migration enquiry, so here's the answer first: a move only costs you traffic when the redirects are an afterthought. We map every URL before anything gets built.

What comes with you

  • Your rankings. Every URL is mapped old to new and redirected before launch, so the search equity you have built follows you.
  • Your content. Posts, case studies, pages and images all come across, along with the metadata that makes them rank.
  • Your analytics history. Same property, same data, no reset to zero on launch day.
  • Your design, if you want it. We can rebuild what you have faithfully, or improve it while we are in there.
  • Your forms and integrations. The CRM, the email tool, the booking link all keep working.

What you leave behind

  • The monthly platform fee, and the price rises you don't get a vote on.
  • Plugin roulette. No more updates that break the site at the worst moment.
  • The editor ceiling. No more "the platform won't let us do that".
  • Lock-in. You own the code and every account, so leaving us is as easy as leaving them.
WHAT WE MOVE

The platforms we move people off.

An overview of each one: what comes across, what has to be rebuilt, and where the work actually is. If yours isn't here, ask. It's usually a variation on one of these.

Platforms Genten Studio migrates from, what each one moves to, whether it is a site or an app migration, and what the move involves.
From Moves to Type What it involves
Webflow Astro Site The design is rebuilt in code. Collections export to CSV, but images come out as links to Webflow's servers, so every asset has to be pulled down before you cancel. Read the Webflow guide
WordPress Astro Site The design is rebuilt in code. Content comes out through the REST API, and the real work is replacing whatever the plugins were doing.
Framer Astro Site The design is rebuilt in code. Layouts translate cleanly, but CMS content and interactions get rewritten.
Bubble Next.js and Supabase App No clean export. The data model and the logic get rebuilt from what the app actually does.
Wized Next.js App The logic lives inside Wized's editor, so it gets rewritten as code you own. Read the Wized guide
Xano Supabase App The schema translates fairly directly. Auth and access rules are where the real work is. Read the Xano guide
Firebase Supabase App Documents become tables, and security rules become row level security.
Airtable Supabase App Fine as a database. The automations and views built on top of it need replacing.
An AI-built prototype Next.js and Supabase App The prototype proved the idea. The work is the architecture under it: real permissions, customer data kept separate, and a structure that holds at scale.
WE HAVE DONE THIS

Three platforms, replaced by one stack.

Sezonski Rad is a two-sided hiring marketplace we moved off Webflow, Wized and Xano onto Next.js and Supabase. It's live, so you can check the result yourself rather than take our word for it.

Three platforms became one stack

None of the three were built for this kind of product, so every feature meant working around the tools. Now it's Next.js and Supabase, and there is one place to change anything.

10x faster to ship features

The difference isn't typing speed, it's that features get built the way they are supposed to work instead of being bent around what the platform allowed.

Under 0.5s server response

Measured on the live site. Fast isn't a nice-to-have on a job board that people open on their phones on a building site.

No workarounds left in the product

Every feature that used to need a hack now works natively. That's the part that compounds, because the next feature starts from something solid.

Read the case study See it live
HOW IT WORKS

We map before we build.

Most migrations lose traffic for one reason: the site got rebuilt first, and the old URLs became somebody's problem afterwards. We do it the other way round.

  1. Audit what you have

    Every page, every URL, every integration, and what your analytics say people actually visit. Some of it is worth moving. Some of it has had no visitors in two years, and we tell you so instead of charging you to rebuild it.

  2. Map the URLs first

    Old address to new address, every one, agreed before a single page gets built. This is the step that gets skipped on cheap migrations, and it's the reason those migrations lose traffic.

  3. Rebuild on the new stack

    Astro for sites, Next.js and Supabase for apps. Your content comes across, the design is rebuilt faithfully or improved, and you see it on a staging URL long before anything changes publicly.

  4. Cut over and watch

    Redirects go live with the site, not after. Then we watch search console and analytics through the first weeks, because that's when a missed redirect shows up, and fixing it then costs nothing.

FAQ

Straight answers.

Will we lose our Google rankings?

Not if the redirects are done properly, and doing them properly is most of the job. We map every existing URL to its new address before anything is rebuilt, and the redirects go live at the same moment the site does, not days later. Rankings move when pages return errors for weeks, and that's a planning failure rather than something migrations do inherently.

What does a migration cost?

Less than building the same site from scratch, in most cases. Your design and your content already exist, so we are rebuilding rather than inventing, and that's the expensive part of a normal project. For reference, a new website of up to 10 unique pages is $3,500. We scope each migration on a short call and quote it fixed before anything starts.

How long does it take?

Usually less than a new build of the same size, for the same reason it costs less. The variable isn't page count, it's how much your current platform will let you export. A Webflow or WordPress site comes across quickly. A Bubble or Wized project has no clean export, so more of it gets rebuilt by hand and the timeline stretches.

Can we keep our current design?

Yes, and plenty of people do. We can rebuild what you have faithfully, so the only thing that changes is what it's running on. We'll also tell you honestly if the design is the thing holding the site back, but that's your call to make, not ours to make for you.

What if our platform has no proper export?

Then we rebuild rather than transfer, and we say so upfront in the quote. Bubble and Wized both fall into this category: the logic lives inside the platform's own editor, so it gets rewritten as code you own. It costs more than a clean export would, still usually less than starting from nothing, and it's the honest reason those platforms are hard to leave.

Do we have to move everything at once?

No. A common approach is to move the marketing site first and leave the app or the blog where it is for a while, then bring it over later. We'll tell you which order makes sense for your setup, because doing it in the wrong order means running two redirect maps instead of one.

What do we own when it's finished?

Everything. The code, the content, the hosting, the domain, the analytics, all in accounts in your name. That's the whole point of leaving a platform you have outgrown, and it would be strange to move you off one form of lock-in and into another.

Tell us what you're stuck on.

Book a 30-minute call. We'll look at your current setup, tell you what moving actually involves, and quote it fixed. If you're better off staying where you are, we'll say so.