Guides · Migration · 2 min

Website and store on one domain: architecture first, then the migration

Pascal Hippmann · updated October 2026
In short

When we got a request for a WooCommerce to Shopify migration, the existing site looked like a single installation from the outside: company pages, blog and store under one domain. But without access to the system, it wasn't clear how content, store and extensions were connected internally. So we didn't just ask about products, but about everything attached to the site. Only then can you say what migrates, what gets rebuilt and what might stay where it is.

The case

What looks like one website in the browser can be many things underneath: a content system with a store extension, two separate systems under one domain, or an organically grown mix with lots of plugins. For the migration, that makes a huge difference. Migrating products is one job. Migrating content, processes and integrations is a completely different one.

What we ask before the offer

  • Content: pages, blog articles, downloads, images.
  • Store data: products, variants, customers, orders.
  • URLs: Which URLs exist, and which need redirects?
  • SEO data: titles, descriptions, structured data.
  • Extensions: Which plugins handle which task?
  • Integrations: inventory management, product data, CRM, warehouse, shipping, payment.
  • Marketing: tracking, email tool, marketplaces.

With a simple questionnaire, even the parts nobody thought of in the first conversation become visible.

Planning a migration?
Data check first. Then a fixed price.
To migration

Migrating data or migrating processes?

Data can be exported and imported. Processes can't. If a plugin automatically creates invoices, sends vouchers or syncs stock today, that process has to be rebuilt in Shopify, with an app, a setting or an integration. This work is often bigger than the actual data migration.

Your takeaways

  • What you see in the browser isn't enough for planning. What's behind it determines the effort.
  • Plan content just like products. Blog and pages have visitors, URLs and rankings.
  • List your plugins and what they do. Each one is a question for the migration.
  • Separate data from processes. The processes are usually the bigger part.

Is there more to your website than meets the eye? We take stock before we give you a price.

Rather talk than read?

20 minutes, honest and no strings attached. Afterwards you know what your store needs.