Migrate from Shopify Plus to WooCommerce

A store where editorial content, guides and product pages drive most of the traffic usually has a modest number of products and a large number of posts and pages. In WooCommerce on WordPress, the content already lives in the same database as the catalog, so the migration centers on products, a limited set of customers and recent orders, plus preserving URLs for the content that earns search traffic. The data volume is typically small enough that the Shopify CSV exports, which are capped at 15 MB for customers, can be handled in a few passes. Images are the heavier task because Shopify's CSV does not carry them, so you re-import them from their public URLs while the original store stays live.

• Data volume: Products, a few hundred or a few thousand SKUs, and customer exports that usually fit comfortably under the 15 MB cap; confirm your own counts before planning.
• Extension count: Often a short list, such as a commerce plugin set, an SEO plugin, a subscription or newsletter tool, and a payment gateway.
• Patching responsibility: WordPress core, the WooCommerce plugin, every active plugin and the PHP and database versions remain yours to keep current.
• Content migration: Blog posts and landing pages already sit in WordPress, so the work is URL mapping and redirects rather than a second content system.
• Hosting: A small store on shared hosting may be acceptable, but confirm the host supports the PHP and MariaDB or MySQL versions WordPress recommends.

Before you commit, check the export of product images and the redirect map for your top landing pages, since these are the items that most often break search visibility after a move.

A catalog with many variants per product, tiered wholesale pricing and business customers with their own terms moves the work from content into data modeling. Each variant needs its own SKU, price, stock and image mapping, and B2B accounts often carry company hierarchies, approval flows and negotiated prices that Shopify handles through apps or Plus features. WooCommerce supports variations and customer roles, but B2B behavior usually comes from paid extensions, so the number of plugins and the testing effort grow with the complexity of your pricing rules and the number of account types.

• Data volume: Variant rows, price tiers and company records can multiply the CSV size quickly, and customer exports may need the Admin API for fields the CSV does not cover; confirm this with your own export.
• Extension count: Expect several paid extensions for wholesale pricing, quote or request-for-quote flows, purchase orders and account management, each with its own update cycle.
• Order history: Historical orders tied to company accounts must be mapped carefully so reporting and reorder functions still work.
• Testing scope: Checkout, tax, shipping and invoice flows need test cases per account type, which adds verification work before cutover.
• Patching responsibility: Every paid extension is a dependency you update, test and back up, so a larger extension list means more frequent maintenance windows.

Ask any extension vendor for its release frequency and how it handles compatibility with the WordPress and WooCommerce versions you run.

A team that already runs WordPress sites, maintains plugins and manages hosting can absorb most of the WooCommerce work internally. The main learning curve is commerce-specific: tax, shipping zones, payment gateways, order statuses and the way WooCommerce stores orders in its own tables. Ongoing responsibility is significant because you own the full stack. WordPress publishes security fixes for the latest version, and its Security Team backports critical fixes to older versions as a courtesy, but the timing of your updates is still your decision, and plugin and theme updates follow their own rules.

• Patching responsibility: Your team applies WordPress core releases, WooCommerce updates and plugin updates, and should subscribe to security advisories for every extension.
• Automatic updates: WordPress enables automatic major release updates for newly created sites since version 5.6, but plugins and themes are only updated automatically in special cases, so verify your settings.
• Hosting and PCI scope: Your team owns server hardening, backups, PHP and database versions, and the payment integration choices that determine PCI DSS scope.
• Internal cost: Staff time for upgrades, testing and incident response recurs every year, and it is the cost most often underestimated.
• Quote question: If you hire a partner later, ask what they will take over and what remains in your team's runbook.

Test whether your team can run a staging copy, apply an update and roll back within your own change process before taking production ownership.

A team without WordPress or commerce operations experience usually needs a partner for the migration and for at least part of the operating model. The partner's scope should cover data mapping, image handling, redirects, extension selection, hosting setup, backups and an upgrade process. DeployOpen plans, implements, hardens, backs up, upgrades and documents self-hosted platforms in your own cloud accounts or data centers, and most engagements are fixed-scope with deliverables and timelines agreed in writing before work starts. Ongoing support, upgrades and testing can be handled under a retainer.

• Scope definition: Write down which items are in scope, such as product and image migration, redirects, extension configuration and checkout testing, and which remain with your team.
• Operating model: Decide who receives WordPress and plugin security notices, who approves updates and who is on call for checkout incidents.
• Documentation: Require runbooks for updates, backups, restores and the payment integration, so knowledge does not sit with one vendor contact.
• Ongoing support: Ask whether support is a separate retainer and what response expectations it covers, without assuming any particular service level.
• Quote basis: Request a quote tied to the written scope and ask the partner to list assumptions about data volume and extension count.

Confirm the handover plan and the retainer terms before signing, because the costs that recur after launch are the ones that decide long-term value.