Ecommerce migration guide: A blueprint for moving forward when your platform can’t

A practical guide to auditing, planning, and launching a smoother ecommerce platform migration

↑ Back to top

In the physical world, moving your business location is a complicated consideration of real estate decisions, building codes and permits, infrastructure, and interior design. 

Whether physical or digital, your storefront is a foundational element to your business. Just like moving a brick-and-mortar location, migrating your ecommerce platform is a decision that affects every aspect of your — and your customer’s — experience. 

If you’re considering WooCommerce, chances are your store is ready for the flexibility and scale that’s only available on the most popular open-source ecommerce platform. 

Along the way, you’ll be able to leverage WooCommerce’s unique advantages by lowering total cost of ownership, optimizing store performance, customizing the shopper experience, and accessing the wide-range of technical integrations that can supercharge your future growth. 

Every migration is different. A small store with ten products and a few hundred customers will face very different challenges than an established business with 10,000 SKUs, complex integrations, and subscription products. 

At its core, a migration is an exercise in evaluating every aspect of your business. This guide will give you best practices based on the many years of experience of our development experts.This isn’t going to be a step-by-step tutorial. You won’t find instructions on how to export a CSV or configure a specific plugin. Instead, we’ve provided a comprehensive framework for planning a migration to WooCommerce.

That said, some of this guide will be rather technical. If you’re unsure, consider collaborating with an experienced developer or agency, such as our recommended Woo Agency Partners.

Phase 1: Discovery and audit

↑ Back to top

The first step to any migration is figuring out exactly what it is that we’re migrating. The discovery phase focuses on four key areas: data, integrations, online presence, and custom functionality. 

Taking stock of the business will save you from unwelcome surprises later in the process, when decisions have compounded and changing course is much harder.

Let’s start with the basics: the information stored in your current platform, from public data like products and landing pages to secure and sensitive information like customer data and order history. 

Products and pages

Begin by auditing the types of products you sell, including total counts, product variations and attributes, categories, and other metadata, and any pricing complexity, like sales or tiered prices. 

Note the intricate data that can cause complications, such as custom meta fields and specific logic for inventory tracking or digital downloads. 

Finally, address any digital assets, such as product images and digital product files, including where they’re hosted; any security concerns; and if you have original, high-quality assets of everything easily accessible.

Along the way, document your current URL structure for products, categories, and pages. Ideally, you’ll be able to preserve your URLs however, the more common approach is comprehensive 301 redirects to updated URLs. 

You should also audit your metadata (titles, descriptions, alt text), structured data, and internal linking patterns. WooCommerce is built on top of WordPress, the most popular content management system that supports more than 40% of the internet. A successful migration typically means an opportunity to improve your SEO, rather than break it.

Finally, spend some time collecting performance benchmarks and metrics of your store as it exists now, so that you can monitor and evaluate everything after launch.

Customers and orders

Once you’ve made it through your products and pages, you’ll need to shift focus to your more sensitive data: customers and order history. 

Collect a high-level audit of your customer account volume, any custom customer roles, purchase history, and customer account data. Remember that privacy regulations (GDPR, CCPA) and PCI compliance mean saved payment methods might not be migrated, and you may need clear communication plans for password resets and account updates. We’ll cover payments in more depth in a later section.

Review your order volume, data completeness, and any custom metadata or fulfillment details you need for tax and analytics. 

The big decision? How much historical data you need on day one versus what you can backfill later — which is especially helpful to know if your database is large.

This is also a great opportunity to consider whether you actually need to migrate everything, or if this is a chance to clean up and archive historical data. 

Integration and custom functionality

External integrations can be a common stumbling block unless you map out everything ahead of time. We’re talking about ERPs, fulfillment and 3PL providers, CRMs, payment gateways, accounting software, ads and analytics networks, PIM systems, and more. 

For each, document the integration method, data flow direction, sync frequency, who owns the credentials, and what happens when things break (because they can). This complete map becomes the integration checklist that you’ll return to throughout the migration process.

Chances are, if you’re exploring WooCommerce, it’s because of the platform’s limitless extensibility. Review all the custom features you’ve added — product configurators, custom checkout flows, B2B logic, specialized pricing or shipping calculations, and any custom reports or dashboards. For each one, ask: why was this built, how is it implemented, does a WooCommerce equivalent exist, and is it still needed?

As you review integrations and custom functionality, you’ll start to evaluate which features can be recreated directly using one of the thousand extensions in our WooCommerce Marketplace, and which features may require additional budget for rebuilding. Determine the trade-offs ahead of time to know which off-the-shelf solutions you can use, and what functionality will be custom.

Checklist: Data audit

By the end of discovery, you should have:

• Complete data inventory (products, customers, orders)
• SEO preservation plan with redirect mapping
• Integration map with technical details
• Custom functionality documentation
• Compliance and security requirements

A proper discovery process front-loads much of the hard work, setting you up for success as you move forward in your migration journey.

Phase 2: Build your foundation: Platform and environment setup

↑ Back to top

With a high-level view of your business, the next step is deciding where to put it. Consider the mantra of “location, location, location.” 

WooCommerce offers unmatched flexibility, starting with hosting and site design. 

If you’re migrating a store from a hosted SaaS solution, the idea of choosing your own hosting infrastructure might be new, but it’s a major benefit of open-source ecommerce. 

For your storefront, the WordPress ecosystem offers a number of design solutions, from page builders to the native block editor. 

These options offer full design freedom to ensure your website fits your business needs, and not the other way around.

Hosting infrastructure: Where your store lives

Unlike SaaS platforms that handle hosting for you, WooCommerce gives you complete control over your infrastructure. That’s powerful, but it also means you’re responsible for making smart decisions about cost, performance, security, and deployment strategy.

Hosting decisions should come early because your environment can constrain or enable your entire approach. The two most common approaches are managed WordPress hosting and bespoke cloud hosting built on platforms like AWS, GCP, or DigitalOcean.

Managed hosts handle your server management, security, and optimization. They may have a higher cost, but there’s less complexity and more support available. For many agencies and businesses, the premium is worth the time saved and problems avoided. 

Cloud hosting gives you maximum flexibility and control, but you’re responsible for security, backups, server updates, and troubleshooting when challenges arise.

The right choice for your business depends on your technical resources, budget, and how much infrastructure management you want to take on. 

Similarly, your developers may have explicit requirements in tooling and workflows that will eliminate specific hosting options.  

For the best managed hosting options, explore our top hosting recommendations for WooCommerce stores.

Design and theme strategy: How your store looks and functions

Ask any experienced web agency and they’ll tell you that building out the visual design is often the most time-consuming part of a migration. Not because the work is particularly difficult, but because there are so many decisions to make. 

The good news? WooCommerce’s tight integration with WordPress gives you unprecedented control over your store’s design.

Often, new site design must balance speed and customization. For the most control, you may want to develop a custom theme that’s tailored to your exact specifications, while the fastest option is selecting a pre-built WooCommerce theme from our Marketplace. 

While some pre-built themes have limited flexibility, they’ll help you launch quickly. You’ll leverage their design, but implement your brand identity like colors, typography, and logos. Pre-built themes won’t typically match your current site’s design, but they’ll help you quickly implement industry best practices.

If customization is critical, we recommend WordPress’s modern block-based approach to customize templates and build layouts without writing code. The block editor is the best choice when you want significant control without custom development. 

Themes built with blocks are the best middle ground. Instead of rigid templates, you build layouts by combining blocks, which can be paragraphs, images, product grids, cart elements, and hundreds of other components.

For WooCommerce, this means you can design product templates, category pages, cart and checkout experiences, and account pages all through visual editing tools. 

Changes happen in real-time, patterns are reusable, and your content remains portable (no vendor lock-in, as there is with third-party editors). There is a learning curve, but that’s typically the case with any page builder or platform.

Whichever approach you choose, make sure your design process includes real product data from the beginning. Design for every scenario — including the mobile experience, accessibility, and frontend performance.

Checklist: Building your foundation

By the time you’re ready to start migrating data, you should have:

Hosting and infrastructure

• Hosting selected and provisioned (production and staging)
• Staging environment configured and accessible for testing
• Security hardening completed on both environments
• Performance optimization implemented (caching, CDN if needed)
• Backup systems in place and tested for restoration
• Monitoring and alerting configured with baseline metrics

Design and theme

• Design approach selected (pre-built theme, block theme customization, or custom)
• Theme installed and base configuration completed
• Core templates built (homepage, product pages, category pages, cart, checkout)
• Mobile responsiveness tested on actual devices
• Brand assets integrated (logo, colors, fonts, imagery)
• Empty states designed (no reviews yet, out of stock, etc.)

Phase 3: Connecting the ecosystem: Integrations and APIs

↑ Back to top

A modern ecommerce storefront doesn’t exist in isolation. Each customer journey is supported by close collaboration between payment processors, shipping providers, ERPs, marketing and analytics platforms, and the countless other tools that power your business. 

When evaluating the WooCommerce extensions that power your integrations, never assume feature parity between platforms. Features that might have worked a certain way before may require some tweaking, and you may need to compare multiple extension options for each use case. 

Start by evaluating the extensions available on the WooCommerce Marketplace. For example, you’ll find well-tested integrations for tools like QuickBooks, Netsuite, Klaviyo, ShipStation and other ERP, fulfillment and automation platforms commonly used by commerce businesses.

Building a realistic testing plan

Using the knowledge we’ve gained and decisions made in our discovery process, the next step is to determine what should be tested while integrations are built and configured. Different integrations will require different validation approaches, and payment processors will be covered in the next section. 

For fulfillment and inventory systems, focus on key customer paths like order flows and inventory syncs. Marketing integrations often include syncing customer data and segmentation, and confirming that automations are firing at the right time or action. Confirm that your analytics and tracking tools are capturing key events and providing accurate data.

One challenge of integrations is that you may not have access to staging environments or be able to set up multiple connections (e.g. to both staging and production environments). Document which integrations require you to test on production and determine how you can create a controlled testing window.

Finally, define clear success criteria for each integration and confirm your results once all integrations are running.  

Integration best practices

As you learned during discovery, some integrations will use off-the-shelf WooCommerce extensions, and some may require custom development. It is never recommended to modify core WordPress, WooCommerce, or extension code, as your changes will be overwritten when software is updated. Many solutions may not match 100% of your current functionality, but might be extensible through hooks and filters. 

Get API keys, credentials, and admin or developer access for all of your integration systems as early as possible, as chasing these down often takes time. 

Remember: sandbox and test modes are valuable, but they don’t catch everything. Before full launch, process real transactions end-to-end — actual money moving, actual products being fulfilled, actual emails being triggered. This is where you discover timing issues, subtle data mismatches, or integration quirks that don’t appear in test mode.

It’s inevitable that some integrations will fail, due to APIs going down, rate limits, or expired credentials, so be sure to continue monitoring your end-to-end process and always plan for how error states will be communicated to customers.

Checklist: Integration planning and evaluation

Before migrating, work through:

Discovery and requirements

• Document current integrations and what business processes they support
• Map data flows for each integration (what data, which direction, how often)
• Identify critical features you use in each current integration
• Assess business requirements vs. platform-specific workarounds
• Determine launch priorities (what’s needed day one vs. what can follow)

WooCommerce solution evaluation

• Research available extensions for each integration need
• Compare feature sets between your current setup and WooCommerce options
• Identify functionality gaps and plan for custom development or alternatives
• Verify data compatibility between your current system and the new extension

Planning for differences

• Document feature variations where WooCommerce works differently
• Plan data transformation needs (field mapping, format changes, structural differences)
• Identify API credentials and access requirements for each system
• Map custom logic that needs rebuilding or reconfiguring
• Note staging limitations where systems can’t connect to non-production environments

Phase 4: Migrating payments: Subscriptions, gateways, and continuity

↑ Back to top

When it comes to data migrations, payment information is likely the most important and sensitive data you’ll be dealing with. We can think of payments as having two key components: the payment gateway integration and the existing customer relationships. 

Your payment gateway is where the actual payment methods and transactions are stored. While you’ll have a record of payments in the customer and order data that we discussed earlier, it’s important to note that the payment gateway itself is an external integration that comes with its own considerations.

For stores with subscriptions and saved payment methods, the stakes multiply because you’re not just migrating the payment method, you’re migrating each customer’s payment token — the connection between the customer in your store and the payments happening through the gateway. 

Let’s start by exploring your options when integrating a payment gateway.

Setting up your payment gateway

In most cases, you can continue using the same gateway (Stripe, PayPal, Authorize.net, etc.) after migrating to WooCommerce. What changes is how your store connects to that gateway. Take a look at the WooCommerce Marketplace for payments integrations and confirm that your existing solution is supported.

For the best conversion rates at checkout, our preferred payment solution is WooPayments. WooPayments is built and supported by Woo and enables you to accept online and in-person payments, track revenue, and handle all payment activity right from your WooCommerce store’s dashboard. 

WooCommerce also offers official payments integrations for many other payment providers, which may be preferred based on your store’s target market or other functionality needs. 

Migrating saved payment methods

When a customer saves their card on your current platform, a token is created with your payment gateway. That token is tied to your current platform’s integration. 

Moving to WooCommerce means those existing tokens may not work with the new integration — even if you’re using the same gateway. This requires coordination with your gateway provider and may involve technical work to map old tokens to new ones. Ask your provider about their migration support early.

Under the hood, the WooPayments extension uses the Stripe gateway to manage transactions, so if your store is already using Stripe, the migration process is seamless. If your store is not using Stripe, you might consider migrating to Stripe on your current platform, then bringing your customers over. 

If migrating tokens isn’t possible, you’ll need to explore how you’ll have your customers update their payment information after launch. In this case, a solid communications and documentation strategy is critical.

Considerations for subscriptions

Subscriptions are often considered to be the most complex payment migration scenario. Each subscription is an interconnected relationship between the subscription record, payment method, billing schedule, payment dates, and access to specific products or memberships. 

Consider your billing cycle when planning the date of your migration. You’ll want to avoid migrating when large batches of subscriptions are renewing, as this creates risk if payment processing isn’t working smoothly. Migrating right after closing out a billing period also means cleaner financial records and fewer cross-platform transactions, like refunds.

Some recurring payments are managed by the payment gateway itself, while others are handled by your current ecommerce platform. The recommended approach here is to use WooCommerce Subscriptions and let WooCommerce handle future billing. 

Some businesses might consider a hybrid approach, where existing subscriptions run on your older ecommerce platform and new subscriptions come through WooCommerce. Each approach has its tradeoffs, so spend time reviewing your options with any project stakeholders.

Once you’ve determined a plan for payment migrations, you’ll want to test your customer flows, including new signups, renewals, plan modifications (upgrading and downgrading), and error states like failed payments and retries. We’ll cover more testing advice in the next section.

Finally, payments integrations don’t end with your payment gateway and transactions; you’ll also want to consider any related areas, such as shipping and tax calculations, that play into your store’s revenue.

Checklist: Payment migration readiness

Before going live with payments:

Gateway setup

• Payment gateway selected and WooCommerce extension installed
• Merchant account configured (existing or new)
• Gateway credentials connected and verified
• Payment methods enabled that customers expect

Subscription migration (if applicable)

• Subscription data migrated with correct dates and terms
• Token migration coordinated with gateway (or re-entry plan in place)
• Customer communication prepared for payment method updates
• Renewal timing planned to avoid migration-day processing

Testing completed

• Test transactions processed (successful and failed)
• Refund workflow verified
• Saved payment methods working (if applicable)
• Subscription renewals tested (if applicable)
• Checkout flow tested on desktop and mobile
• Error messages clear for common failure scenarios

Phase 5: Testing each phase of the migration

↑ Back to top

One major advantage of migrating your digital storefront is that you can test each segment of the migration as you go. Testing builds confidence, as long as you do it throughout the migration process and not just at the end. 

Issues can always arise, but if you focus on the critical paths in your store admin and your customer’s buying journey, you increase your chances of delivering a reliable migration experience.

Building a staging environment

Throughout the migration process, you’ll be building your new WooCommerce store in a staging environment. Staging environments are typically provided by your hosting provider and should match your production environment as closely as possible. 

That means ensuring your staging environment is running on the same server configuration with the same theme and extensions, and data to match production scale and quality as closely as possible.

A good rule of thumb is to test for peak performance, not averages. Most stores experience peak selling times around general shopping days (Black Friday Cyber Monday) or timed with marketing campaigns and product drops. 

Talk to your hosting provider about doing load testing ahead of time to ensure that all of your extensions and integrations run smoothly during peak activity. 

Note that many WordPress sites use performance optimization plugins and caching tools that might change how your site is rendered on the frontend, and you’ll want to test those scenarios as well.

Keep in mind that while you want to load your staging environment with as much real data as possible, you’ll have to ensure that there’s no leakage: no accidental email blasts or payment transactions triggered for real customers.

Testing strategies

Comprehensive testing covers different aspects of your store and utilizes different testing strategies, including: 

• Functional testing: Test core customer journeys (browsing, searching, checkout, account management, refunds) for both happy paths (ideal, straightforward user journeys) and common error scenarios like payment failures or out-of-stock items.
• Integration testing: Verify that connected systems sync data correctly in both directions, handle errors gracefully, fire webhooks properly, and update within expected timeframes.
• Data validation: Beyond record counts, confirm that product info displays correctly, prices and inventory are accurate, customer logins work, order history is accessible, and all images load properly.
• Performance and load testing: Check page load times, checkout performance under peak simulated load, database response times with full production data, and CDN/caching behavior.
• Security testing: Ensure SSL certificates are configured correctly, payment forms are secure, admin access is restricted, and no sensitive data is exposed.
• Accessibility testing: Verify screen reader compatibility, keyboard navigation, color contrast and readability, and properly labeled forms with clear error messages.
• SEO testing: Ensure that all of the proper redirects are in place and all structured content data is present and valid.

Don’t wait until the end of the migration process to test, and don’t limit tests to happy paths that ignore unexpected user experiences or failure scenarios. 

Ensure that there’s a set workflow for tracking and triaging issues along the way, and that all stakeholders have a common place to share their testing feedback.

Checklist: Testing readiness

Before declaring testing complete:

Core functionality

• Product browsing works across categories and search
• Cart functionality handles add, remove, update, and edge cases
• Checkout process completes successfully (guest and registered)
• Payment processing works with real transactions
• Customer accounts can register, log in, and access order history

Integrations

• Payment gateway processes transactions correctly
• Shipping calculations return accurate rates
• Tax calculations match expected amounts
• Inventory sync reflects correct stock levels
• Email notifications send and display properly

Data validation

• Product data displays correctly (prices, descriptions, images)
• Customer data migrated accurately
• Order history accessible and correct
• URLs and redirects working properly

Cross-platform experience

• Mobile experience tested on real devices
• Major browsers verified
• Performance acceptable under peak load

Phase 6: Launch day: Validation and go-live strategy

↑ Back to top

Now that you’ve planned, prepared, built, and tested your new store, it’s time to launch. For the unprepared, launch day might mean stress and anxiety, but if you’ve been following this migration blueprint, you can feel confident that you’ve covered all of your bases. 

That said, even the most successful launches might hit a few bumps in the road, so plan your launch day as strategically as your entire migration.

Launch strategies

Your launch strategy will be determined by a few factors, including the complexity of your store and the level of risk management that’s appropriate for your business. 

You’ll need to find the approach that best matches your overall migration strategy. In either case, ensure that you have a rollback plan, or build flexibility into your launch strategy and address issues as they arise.

A hard cutover means flipping the switch all at once — the old platform goes dark, and the new one goes live. This is the most common approach and is generally recommended for smaller to mid-sized businesses. You’ll want to consider the timing of the cutover, focusing on low-traffic periods and avoiding holidays, weekends, and major sales or promotions.

Alternatively, you may want to run your old and new store simultaneously in a parallel approach. This could look like a soft launch where you direct some segment of customers to your new site, letting them know that they’re testing a new platform. Be aware that parallel approaches require significantly more work because you’ll eventually have to reconcile both platforms.

The launch sequence

A prepared team will have a series of checklists for pre- and post-launch. The launch window should be an agreed-upon time where all stakeholders are online and ready to respond at a moment’s notice.

You’ll perform your final data sync, either by migrating all of your data at once, or by performing a delta migration of any new data generated since the last migration. 

Next, you’ll implement a data freeze on your old platform and make the necessary DNS changes to route traffic to your new site. Depending on your domain management tools, DNS propagation can take time and there may be a gap where visitors see both sites. This can usually be optimized with a CDN provider that includes DNS proxy tools for faster propagation.

Once DNS propagates, it’s time to start your post-launch testing and monitoring. Make sure you’re able to test a handful of real transactions to make sure everything loads correctly and all of your integrations trigger their necessary workflows. Continue monitoring all channels for issues, from server logs to customer support queues, for the first few days after launch.

Checklist: Launch day

Pre-launch (day before)

• Final testing complete on staging
• Production environment verified
• DNS changes prepared
• Team roles assigned
• Rollback plan documented

Launch sequence

• Final data sync complete (if applicable)
• Old platform frozen
• DNS updated
• Core functions verified post-cutover
• Monitoring active

Post-launch verification

• Checkout working with real transactions
• Orders flowing to fulfillment systems
• Email notifications sending
• Analytics tracking data
• No critical errors in logs

Phase 7: Post-launch monitoring, optimization, and course correction

↑ Back to top

You have successfully launched your store on WooCommerce, but the work doesn’t end here. The first few days and weeks after a big migration are a critical stabilization period where you’ll want to continue monitoring all aspects of your store. 

Set your expectations early of who monitors what, where critical issues are tracked, and who is responsible for triaging and escalating any issues that come up. 

Keep your communication channels open between stakeholders, including your developers, store managers, and whoever is responsible for your hosting platform. 

The critical first days

The first few days after a launch require the highest levels of attention and care. Keep an eye on critical systems, like server and error logs, conversion rates, and performance metrics. 

You’ll want to make sure that orders are still coming in correctly and that all of your integrations are working properly. Finally, keep track of SEO and marketing automation, ensuring that your site is still receiving organic traffic and tracking user activity.

This type of monitoring is a collaborative effort across your entire organization, including your customers. Make sure that customer support requests and social media chatter aren’t lost in the shuffle of your new launch. Keep an eye out for repeated feedback on the same topic that could be a symptom of a larger issue.

Long-term monitoring

As your new site begins to feel more stable, you’ll be able to step back and take a wider view. This is a good time to compare your new site’s performance to any baselines you collected before the migration. Continue testing for performance, security, accessibility, and critical metrics like conversion rates.

In many cases, you’ll not only be looking at matching metrics, but you’ll see improvements thanks to the unique customizations possible with WooCommerce. 

As you’re settling into your new workflows, you can begin to explore all of the new possibilities available now that you’re in control of your ecommerce platform and environment.

Checklist: Post-launch health

First 24 to 72 hours

• Error monitoring active with alerts configured
• Order flow verified through fulfillment
• Payment processing confirmed working
• Key integrations healthy
• Team monitoring assigned

First week

• Performance baseline established
• SEO monitoring configured (Search Console, rankings)
• Customer feedback reviewed
• Known issues tracked and prioritized

First month

• Performance optimizations implemented as needed
• Redirect coverage verified (404 monitoring)
• Conversion rates compared to pre-migration
• Stabilization period completed

---

Get your free migration checklist

↑ Back to top

This interactive, step-by-step checklist will help ensure you get your replatforming right.

With your migration completed, it’s time to look ahead

↑ Back to top

Congratulations! You’ve made it through the full migration journey: from initial questions and discovery, through building your foundation, connecting integrations, migrating data, handling payments, testing thoroughly, launching successfully, monitoring post-launch, and training your team.

Every migration is different, but the principles remain constant: plan thoroughly, test relentlessly, communicate clearly, and support the people who use the platform every day.

Now that you’re successfully operating on the most customizable ecommerce platform in the world, you’re ready to scale, innovate, and grow without limits.

Welcome to WooCommerce.