Shopify

Shopify migration

Migration to Shopify

Moving platform is a product and operations project, not just a data export. We plan what moves, what gets rebuilt, how URLs and SEO carry over, and how you run the business on day one in Shopify — apps, markets, subscriptions, and integrations included.

Based in Copenhagen; we regularly work with Danish merchants and EU brands. English and Danish.

Plan a migration

Platforms we help you leave

  • WooCommerce & WordPress commerce
  • Adobe Commerce / Magento
  • Wix, Squarespace, and other SaaS builders
  • Custom or legacy stacks (headless, in-house, older PHP/.NET)
  • Another Shopify store (restructure, merge, or clean replatform)

What we handle

Every migration is different; scope follows discovery. Typically we cover:

  • Product, variant, and metafield mapping — including SEO fields and rich content
  • Customer and order history strategy (imports, GDPR, and what stays external)
  • URL structure, redirects, and sitemap hygiene to protect rankings
  • Payment, shipping, tax, and market setup in Shopify
  • Replacing or re-implementing critical apps vs native Shopify features
  • Cutover plan: DNS, downtime window, monitoring, and rollback thinking

How we work

01.

Audit & mapping

We inventory catalog, integrations, edge cases, and success criteria — then propose a phased plan.

02.

Build the Shopify side

We stand up the theme, data model, apps, and integrations in dev/staging before touching production traffic.

03.

Migrate & launch

We run test imports, validate redirects and tracking, then execute cutover with a clear checklist.

SEO & business continuity

We treat redirects and indexable URLs as first-class. We also align with your team on what must work on launch day — POS, ERP sync, email flows — so “live” means actually operable.

Before you start

Who owns the new store?
You do. The new store, the data you choose to move, and the redirects stay in your accounts. The old platform stays yours until you close it.
How does a project start?
We start with a conversation, map the catalog and the integrations, and agree what has to work on launch day before we move anything.
What does it cost?
A migration does not have one price. It follows the catalog, the integrations, and what has to be rebuilt. The guide shows how we think about the numbers, and where a cheap quote gets expensive later. Read what a Shopify store costs

Considering Shopify?

Share your current platform and rough catalog size — we’ll suggest a sensible first step.

Get in touch

What to settle before you move to Shopify

A move to Shopify is a product and operations project. The export is the easy part. The hard part is what comes with you, what gets rebuilt, and how the business runs on day one: orders, stock, shipping, tax, markets, and the integrations the warehouse already uses. We move stores from WooCommerce, Magento, Wix, and custom stacks. The platform you leave changes the checklist. It does not change the fact that someone has to own the cutover.

The catalog should look like what you intend to sell, not like whatever the old store accumulated. Products, variants, images, collections, and the metafields the theme has to show are planned before the import. Customers and orders come along when you need that history in Shopify. They stay behind when the history should remain in the old system and Shopify should only sell from now. That choice is made early, because it changes both the import and what customer service must be able to look up.

URLs and redirects are the SEO part people underestimate. Every important address on the old store should land on a real page on the new one, not a soft 404 and not the homepage. We build that list from what actually has traffic and links, and from the pages you still want. Apps on the old store become a Shopify app, something Shopify can do itself, or something you drop. Installing the same stack again, without asking whether it is still needed, is how a store gets slow on day one.

Cutover is a date. Before it there is a dress rehearsal: checkout, shipping, tax, one real order, what the warehouse sees, and the redirects you have approved. On the day, DNS moves when that rehearsal has passed, not when the import happens to finish. Afterwards there is a short period when the old store no longer takes orders, and when we fix what the rehearsal could not see. You are told who does what that day.

The guides on this site about WooCommerce and about what to have ready before a build are written for this kind of project. They are not a substitute for the scope. Write where the store lives today, how large the catalog is, and what must not break. We will say whether the move is a few weeks or a longer project, and what you need to settle before we set the date.

Tax, shipping, and markets are part of the move, not a setting you find afterwards. A Danish store that also sells in the EU has to know which prices include tax, which rates apply, and whether Shopify Markets or another setup should carry it. We put that in the plan, because wrong tax on day one is worse than a late homepage. The same goes for payments. What you use today has to work in Shopify, or you have to have chosen the replacement before DNS moves.

After cutover the old store is not a backup you can quietly keep selling from. It is an archive until redirects and customer service are calm. We agree when it stops taking new orders, and who answers customers that land from an old email with an old link. The move is finished when those links land correctly and the warehouse can see the order where you said it would. Not when the theme looks done.

If you have it, include the URLs that actually get traffic in the first note. Not the entire sitemap as an attachment at all costs, but the pages you know are linked. We can find the rest. What you cannot afford to lose, we cannot guess. That includes a B2B price or an integration the warehouse swears by.

A move has an order that is dull and necessary. First, what must come across: products, variants, collections, customers, and the URLs that actually get traffic. Then what does not exist as the same thing on Shopify: a plugin, a B2B price, a shipping rule, a subscription. Last, a date when the old store freezes, so redirects point at pages that will not move again the next morning. We start where you know you cannot afford to lose something. The logo can wait.

Bring the important URLs in the first note if you have them, and the name of the system the warehouse uses. We can find the rest. What you cannot afford to lose, we cannot guess. Write to hello@globus-dev.com, or use the contact form and choose migration. The WooCommerce guide is the checklist if that is where you are coming from. It is not a promise about how long your catalog takes.