Database access makes records available. The real work is finding what plugins, attributes and WordPress routes are doing before the move.
WooCommerce attributes may describe variants, filters or information only. Treating every attribute the same can create wrong variants or lose useful product detail. We profile the attribute set, agree which values become Shopify options, metafields or filters, and test representative simple and variable products before the full run.
Subscriptions, bundles, add-ons, memberships, loyalty, custom checkout fields and B2B rules may live in plugin tables rather than core WooCommerce records. We review the active plugin list and sample data, then classify each item as transferable, transformable, replaceable or requiring a rebuild. Stored subscription payment methods cannot simply be moved and need a separate plan.
Products, nested categories, posts, tag archives, media pages and legacy redirects may all receive traffic. We crawl the live site, review Search Console where available, map route families deliberately and verify redirects as single hops. Pages with no useful destination are decided rather than sent to the homepage by default.
The source database changes during the build. We agree a full-migration point and a later delta for the records created or changed before cutover. The plan states how new orders are captured and checked around the switch.
From-price or scoped after source review
Data only
From £1,000From $1,300
Products, customers, orders and content mapped into a Shopify store that already exists or is priced separately. Fixed once source access and a sample migration are reviewed.
Starting price · scoped after discovery
Migration and build
From £5,000From $6,500
Moving to Shopify and building the store in one project, so the data and the storefront land together rather than in two disconnected pieces of work.
Starting price
Plus, B2B, multi-market
From £8,000From $10,500
Shopify Plus, B2B, multi-market, multi-language, custom integrations or headless work. These configurations are sized after discovery, not instant-priced.
Starting price · scoped after discovery
Third-party platform, application and migration-tool fees are separate unless listed. Estimator output is indicative and non-contractual.
Usually, but not always as a single product. Where a range has more option dimensions than Shopify’s product structure holds, it is split, combined or modelled with metafields, and that decision is made with you before the import because it changes how the range is shopped.
Yes, with the caveat that content built in a page builder exports as markup that only means something inside that plugin. Those pages are rebuilt as Shopify templates, which is usually an opportunity to reduce how many of them there are.
It does not move. Shopify handles trade pricing through different mechanisms, and which one fits depends on your plan and on how the accounts actually work. It is scoped as build work rather than treated as data.
Yes. Password hashes cannot be transferred between platforms, on any migration. Accounts move with their addresses and order history, and customers reactivate on first use. The message that goes out is planned before cutover.
It usually tells us more about the real migration than the product count.
