Free 20-point conversion & SEO audit for export stores — Free website audit — claim yours

hello@woo.one Mon–Fri · 9:00–18:00 (UTC+8)

A Pre-Launch Checklist for WooCommerce Migrations

Data integrity, redirects, checkout tested as a matrix rather than a sample, email deliverability, and the one check almost everyone skips: buying from another country.

Most store migrations are tested the same way: click through a few pages, place one order with a test card, and go live. Then the first real customer finds the bug.

This is the checklist we run before switching traffic on a migrated store. It is ordered by what breaks first, and each item is something that has actually caused a launch-day problem on a real project.

Data integrity

Product and variation counts match the pre-migration inventory. Not approximately — exactly, with a written baseline taken before export. A difference of 12 products out of 800 is not noise; it is 12 products with no page.

No duplicate SKUs, and every variation has one. WooCommerce will accept an import with missing variation SKUs without complaining, and you will discover it at the first warehouse reconciliation.

Prices are absolute, not deltas. If the old platform stored option price modifiers, confirm the new variation prices are final prices. A 40 product with a +5 large size must be 45, not 5.

Stock is tracked at the right level. Per-variation if the old system tracked per option combination; at parent level if it did not. Inventing per-variation stock creates oversells.

Ten random products compared field by field against the old site: title, price, sale price, stock, images, description, attributes, categories.

URLs and indexation

Every old URL returns 301 to the closest equivalent page — not to the homepage. Test 30 random samples plus the top 20 by traffic.

No redirect chains. One hop, no loops, no 500s.

Canonicals point at the new live URLs, not staging, not old paths.

Sitemap contains only live URLs, and the old platform’s sitemap file is gone.

No noindex tags left on templates. Search every template used by products, categories and blog posts. Staging noindex tags survive deployment more often than anyone expects.

robots.txt does not block the new paths and does not reference the old sitemap.

The redirect discipline is the same one described in the OpenCart migration guide, and it is the item most often done partially.

Checkout, tested properly

One completed order per payment method, per currency, per shipping zone. Not one order total — the matrix. This is where variation-heavy products, tax rules and shipping calculations collide.

3-D Secure authentication completes for at least one card per gateway. The authentication step behaves differently by country and is a common silent failure.

Tax amounts are consistent between cart, checkout, order confirmation and invoice. Compare line by line, not totals.

Refund path works. Refund one test order end to end, including the gateway side. Refunds are rarely tested and frequently broken.

Guest checkout and account checkout both work, and the password reset flow sends a working email — customers arriving from the old platform all need it.

Coupons and discounts apply as expected, including the ones with minimum spend, category restrictions and usage limits.

Email and notifications

Order confirmation arrives, from your domain, not in spam. Verify SPF, DKIM and DMARC before launch. This single item causes more launch-week support tickets than any other.

Password reset, new account, shipping confirmation and refund emails all send and render correctly on mobile.

The “from” address matches a monitored mailbox. A noreply address that nobody reads means customer replies disappear.

Performance, measured not assumed

A product page, a category page and the cart load in under three seconds on a throttled connection. Test from a location near your customers, not from your office.

Image sizes are regenerated, and the page is not serving original uploads. Migrations routinely import full-size images and serve them at thumbnail dimensions.

Caching works for anonymous visitors and is bypassed for logged-in users and carts. A cached cart page is a data leak; no cache at all is a slow store.

If the old store was slow, do not expect the new one to be faster by default — see the notes on planning a performance pass after launch, when you have real traffic to optimise against.

Tracking and operations

Analytics records a test order as a conversion, in the new property, before launch.

Search Console is verified for every language and subdirectory, and the sitemap is submitted.

Backups run and have been restored once. An untested backup is a hope.

Error logging is on and someone knows where to look. Migration bugs surface as PHP notices long before they surface as complaints.

Admin accounts are cleaned up — no leftover staging logins, no default admin username.

The one item people skip

Place an order as a customer in a country you do not live in. Use a VPN, a real address format, and that country’s payment preference. Half the launch-day checkout failures only appear when the buyer is not you: address fields that do not fit, states that do not exist, postal code validation that rejects, tax that fails to apply.

If you would rather have this run as a formal pre-launch review on your own store, that is part of what we do under WooCommerce development — usually two days, and it catches things that take two weeks to fix after launch.

S

Infrastructure and security engineer at woo.one, based in Foshan, China. Works on WordPress, WooCommerce and OpenCart systems, self-hosted mail, and the operational side of running stores for exporters.

More about the team

No pressure · No sales script

Ready for a store that sells while you sleep?

Send us your current site or product list. You will receive a fixed-scope proposal, a 20-point audit and a realistic timeline within two business days.

Reply within 1 business day NDA on request 100% code ownership
Chat with us
WhatsApp Get a quote