Order of data migration
Start with products, then customers and required historical orders. Imported orders can then link to existing records. Run a representative test import before the full migration.
WooCommerce provides a product CSV export; customers and orders may need additional tools. Map source fields to your chosen Shopify import format. Shopify’s Store Migration app currently supports WooCommerce product imports in early access for certain stores; it is not a universal complete-store migration tool.
- Products including variants, SKUs, images and stock levels
- Map categories and tags to Shopify collections
- Customer data (addresses, email, B2B/B2C tax status)
- Required historical orders without triggering new invoices or fulfilment
- URL redirects and metadata for SEO
Reconcile imported data and edge cases
Map product names, SKUs, variants, images, weight, prices and stock to Shopify fields. Translate categories into collections and navigation. Subscriptions, configurators and custom pricing are separate requirements, not simply product fields.
Use a sample with variants, discounts and a refund. Compare totals and statuses with the source. Historical orders use a suitable app or API rather than the standard product or customer CSV importer. Suppress unwanted notifications and accounting automations during test imports.
Plan customer sign-in separately
Customer records and authentication are separate concerns. Existing passwords cannot be imported through Shopify customer CSV. Current customer accounts use emailed codes; legacy account models may require a new password.
Transfer newsletter consent only with suitable evidence. Check which historical orders the import method links to customers and makes visible in their accounts. Communicate the new sign-in process after it has been verified.
What happens to your invoice history
Retain the original WooCommerce invoices with their original numbers and files in a traceable archive. Importing historical orders does not replace it. Secure the required documents, structured e-invoice data and supporting records before shutting down the old system.
For new invoices you may continue the existing series or create a clearly distinct series, for example with a new prefix. §14 UStG allows one or several numbering series. Document the cutover and prevent duplicate numbers. New Shopify order numbers do not automatically provide suitable invoice numbers.
301 redirects: save your SEO instead of losing it
The most common migration mistake is lost traffic because URL structures change. WooCommerce uses paths like /product/... or /shop/..., while Shopify uses /products/... and /collections/.... Every old URL therefore needs a permanent 301 redirect to its new target.
Build a mapping table that pairs each WooCommerce URL with its Shopify counterpart. Shopify offers native URL redirects; for large catalogs a bulk import of redirects pays off. After go-live, watch Search Console to catch 404 errors early.
Rebuilding tax logic in Shopify
Configure taxes separately in the new store. Established small businesses generally face limits of €25,000 prior-year and €100,000 current-year turnover; the first year uses a €25,000 limit. Check your actual status before launch. See small-business VAT and Shopify.
Eligible EU consumer distance sales can be taxed at destination and reported through OSS. EU B2B goods sales require checking intra-community supply rules; certain services instead use reverse charge. A valid VAT ID alone does not establish all necessary conditions.
Connect accounting instead of manual upkeep
After the migration you don't want to book every order by hand again. Connect Shopify directly to your accounting system so invoices, credit notes and cancellations flow automatically, for example via connecting Shopify to sevdesk or connecting Shopify to Lexware Office.
Check which sales and refunds the selected integration supports using actual examples. Special tax cases and partial refunds must match its capabilities. A webhook alone does not guarantee correct accounting.
Go-live checklist
Plan a fixed cutover window and test the new store thoroughly beforehand. Only once data, redirects and tax logic are in place do you switch DNS and your payment provider live.
Reconcile new orders and inventory changes just before cutover. Document a fallback plan covering orders already placed in the new store. Reversing DNS alone does not synchronise those records.
- Test order with real tax calculation completed
- All WooCommerce documents exported and archived audit-proof
- 301 redirect mapping fully imported
- Invoice numbering agreed and checked for duplicates
- Accounting connection and webhooks tested
- DNS switch and SSL verified
