OTHER
PLATFORM MIGRATION
- 5+ projects
- from 2 weeks
- without losing rankings
A move off Tilda, WordPress or another builder onto code of your own: no platform subscription, no template ceiling, and the code belongs to you. Content and URLs come across without losing rankings.
WHO IS IT FOR?
Three situations where the platform has become more expensive than moving off it
- .01
THE LOGIC YOU NEED CANNOT BE ADDED
Your own pricing by parameters, a non-standard order flow, an integration that is not on the list. Every time the answer is the same: the platform does not do that. Then the workarounds start: part of the process moves into spreadsheets, part gets done by hand, and the site turns from a tool into a shop window with people working around it.
- .02
THE SUBSCRIPTION GROWS AND THE SITE IS STILL NOT YOURS
You pay every month, for years, and the whole time the site does not belong to you: it lives by the platform’s rules, on its servers, in its format. Leaving means building it again. Add up the customisations and the plugins separately: at some point the total matches the cost of a site of your own, and the result is the same as before.
- .03
YOU HAVE RUN INTO SPEED AND SEARCH
Pages take a long time to load, worse on mobile, and the template drags along code nobody needs. That runs straight into two things at once: your search rankings and what an ad click costs you. Inside a builder this can be treated only as far as the builder allows — and by now it usually allows less than you need.
WHAT'S INCLUDED
We do not build below this line
- - A review of the current site and its rankings.01
- - Migration of the structure and the content.02
- - Keeping the URLs, plus redirects.03
- - Built from scratch, no template.04
- - Admin panel by LUNO.05
- - Speed and technical SEO.06
- - Launch on our servers.07
- - A rankings check after the move.08
- THIS IS THE FLOOR, NOT A PACKAGE
Everything listed ships in every project — even the simplest and cheapest one. There are no stripped-down versions.
- THE SEARCH RANKINGS ARE THE MAIN RISK
URLs, redirects and structure are worked through before the move, not after. That is what people most often lose — and it gets closed in advance.
- WE SWITCH OVER WHEN IT IS READY
The old site keeps running until the new one has been checked end to end. The move happens in a single moment, with no interval in which neither of them works.
CATEGORIES
Three levels of scope. Yours is the one you recognise yourself in
THE MOVE AS IT STANDS
WHEN IS THIS YOUR CASE?
The structure and the look of the site are fine; the problem is the platform. We build the same thing on code of our own: the structure, the content and the URLs come across, the rankings are kept, an admin panel is added and it launches on our servers. The whole base build, without the extras you do not need yet.
THE MOVE PLUS AN UPDATE
A STORE OR A SERVICE
WHEN IS THIS YOUR CASE?
What moves is not a site but a working commercial operation: a catalogue of thousands of items, orders, a customer base, purchase history, payments. Here the data migration is an engineering job in its own right, and it runs alongside the working store until the new one proves itself correct on real orders.
FAQ
Answers to the most popular questions
From $2.500 for a move that keeps the current look to $8.000 and up for a store with a catalogue, orders and a customer base. The figure depends on the number of pages, the volume of data, and whether we move the site as it stands or update it along the way.
A move as it stands takes 2–3 weeks. With the design and the structure updated, 2–4 weeks. A store or a service, from 3 weeks. The old site keeps running throughout; the switch happens at the end.
That is the main risk, and it gets closed before the move. We collect the current URLs, match them against the new structure, set up redirects and keep the pages that bring traffic. A dip of a week or two after the move is normal; the positions recover afterwards. If the site brings you enquiries from search, say so on the first call: the plan will be a different one.
Copy, images, pages, products, the customer base and the history all come across. What gets rebuilt is whatever was tied to the platform’s own features: built-in forms, widgets, plugins, some of the animation. Exactly what falls into which group we show after reviewing the current site — before the work starts.
Yes. The new site is built and checked in parallel while the old one keeps running. The switch happens once everything is ready and verified — there is never an interval in which neither of them works.
We go through them at the start: email, analytics, payments, CRM, chats, advertising pixels. Most move across directly. Anything that was a platform plugin gets implemented in code — usually closer to your process than it was. We draw the list up before we start, so that nothing quietly stops working after the move.
Not always. If the site is a landing page or a business card with nothing unusual about it, a builder is cheaper and does the job. A move pays off when the platform is in the way: it will not do the logic you need, it is slow, or the subscriptions plus customisations now match the cost of a site of your own. If it covers what you need, the honest thing is to tell you so on the first call.
Then it is a redesign rather than a migration: we update the look and the structure as far as the platform allows. That is described under its own service. If it turns out along the way that the platform’s limits are the root of the problem, we will say so.
You do. The sources, the rights and the admin panel are yours, and there is no more subscription to a platform. What remains is the server. If you ever decide to change contractor, the site leaves with you.