Two platforms, one recommendation
We build on Centra and Shopify, so the recommendation can land on either. A move to the wrong destination is the most expensive kind, and we would rather lose a project than send you there.
Samsøe Samsøe, Eton and Envii all changed platforms with us. We plan the move, migrate the data, map the redirects, rebuild the integrations and design the storefront waiting on the other side, on Centra or Shopify depending on where your brand belongs. Fifteen years of building storefronts means we have moved live stores more than once.
We build on Centra and Shopify, so the recommendation can land on either. A move to the wrong destination is the most expensive kind, and we would rather lose a project than send you there.
The data scripts, the redirect map, the integrations and the new storefront are handled by the same designers and engineers, so nothing falls in the gap between a migration vendor and a design partner.
Organic traffic is the asset a move most often damages, and the protection is methodical rather than clever: a complete redirect map, held in place long after launch, and search data watched until the curves agree.
A platform move carries four workstreams at once: the data, the rankings, the integrations and the storefront itself. We run them as one engagement with one team, so they land together.
Before anything moves, we look at your catalogue, markets, wholesale plans and the team that will run the store, then recommend a destination from what we find. The audit is also where the redirect inventory and the integration list begin.
Catalogue quirks that grow over years are the real work of a data migration. We write migration scripts around your products, customers and order history, and resolve those quirks in transit so they never reach the new system.
The redirect map starts from your own traffic: every page that earns visits or links is matched to a new address before the build is finished. The redirects go live with the store, and search performance is compared against the old baseline for weeks afterwards.
Email flows, payments, delivery, search and the ERP connection are rebuilt against the new stack one at a time. Every reconnected flow is tested against live events before launch and checked again after it.
The old theme cannot follow you to a new platform, so a storefront gets designed and built either way. That makes the move a natural moment for a redesign, and our designers and engineers run the two as one build.
Launch day gets a plan of its own: a content freeze, the switch, and the redirects checked the same hour. The engagement then keeps running for weeks, until search traffic, conversion and every reconnected system have settled.
We move brands both ways, and the destination shapes the second half of the project. A move to Centra always includes a storefront build, because nothing pre-made waits on the other side. A move to Shopify starts with a choice between a Liquid theme and a custom storefront. Underneath, the migration work is the same: data, redirects and integrations.
Fashion and lifestyle brands with wholesale alongside DTC often move in this direction. We have been a Centra Pro Partner since 2015 and work as a Centra agency, and we wrote down the full anatomy of a Centra migration.
For DTC-led brands, Shopify's checkout and app ecosystem are strong arguments, and we make them when they apply. We build both custom storefronts and Liquid themes on Shopify, depending on where the brand is in its growth.
The decision deserves its own homework before any planning starts. We compared Centra and Shopify after years of building on both, including the cases where staying put was the better outcome.
The budget has two halves, the migration work and the storefront being built on the other side, and which half weighs more depends on where you are coming from. A clean catalogue and a short integration list keep the migration lean, while years of accumulated quirks push cost into the data work. We put numbers on both halves after an audit.
A full move takes months, and part of the timeline is set before an agency is even chosen. Brands that arrive with a cleaned catalogue, a list of every system connected to the store and their undocumented rules finally written down tend to move noticeably faster.
Rankings survive a move when the redirect work is treated as a core deliverable. Permanent redirects carry ranking signals to the new URLs, and a brief fluctuation while search engines recrawl is normal and recovers. Migrations go wrong when pages are missing from the redirect table, when old URLs point at the homepage instead of their real successors, or when the table is taken down before search engines have finished recrawling.
The tools stay; it is the connections between them and the store that get rebuilt. CRM, email, delivery, search and the ERP all continue on the new stack, wired to new events and APIs. We list every connection before the move, so none are discovered missing after it.
A brand should stay put when the platform is not the bottleneck. Slow pages, a dated design or a tangled app setup can often be fixed in place, and a migration costs focus even when it goes perfectly. If an audit shows your problems are solvable where you are, we recommend staying and fixing the store instead.
We take brands to Centra and Shopify, since those are the platforms we build storefronts on. The source side varies more: custom stacks, older enterprise platforms, or one of the two we build on. The source mostly shapes the export work, while the destination shapes everything else.
It can, and most of ours are. The work is planning, code and data, and none of the three needs a meeting room. We work from Gothenburg and Oslo with brands selling across Europe and beyond, and launch day runs over a shared channel wherever the team sits.