eCommerce migration and replatforming
Moving a store to another platform with the catalog, the customers, the orders and the rankings intact.

A replatform goes wrong in one of two places: the data, or the addresses. The data, because a product on one platform is not the same shape as a product on another. The addresses, because a store that changes every URL without redirecting starts again from nothing in search - months of traffic gone in a week, and it is the part nobody budgets for.
Neither is difficult. Both are unforgiving if they are left to the end.
Every URL that exists today either exists on the new platform or redirects to the page that replaced it. Not to the home page - to the page that replaced it. A redirect to the home page tells a search engine the page is gone, which is exactly what you were trying to avoid.
A rehearsal on a copy first, with the real data, timed. Then the switch, in a window you choose, with the old store still standing and a way back that has been tested rather than assumed.
Not if the redirects are done properly, which is the single largest reason to take a migration seriously. Expect a wobble of a few weeks while the new addresses are recrawled; expect a collapse only if the old addresses were left to 404.
We give you a number rather than a promise, and it comes from the rehearsal: we run the real migration against a copy and time it. For most stores the freeze is hours, not days.
Sometimes. If both platforms use a hashing scheme we can carry across, yes. Where they do not, we plan a reset campaign as part of the launch rather than letting people discover it at checkout.
That question comes before this service, and we will answer it honestly - including when the answer is that your current platform is fine and the real problem is the theme, the hosting or an integration.
Even a rough answer - the platform, roughly how many products, whether the order history has to come with it - is enough for a realistic first estimate of the freeze and the redirect work.
Projekt starten