WooCommerce migration for retailers in 2026
Moving from Magento to WooCommerce? Preserve product fields and customer records through export, import, redirects and a tested checkout.
- Published
- Last updated
WooCommerce migration is possible by moving your catalogue into WordPress, transferring customer and order records through a separate import route, then rebuilding the store’s operating settings. The built-in product importer handles catalogue data. Customer accounts, purchase history and payment arrangements need their own work before you change domains.
This guide fits retailers moving an existing store into WooCommerce, including a Magento or Shopify store. Treat products, customers, orders, media and URLs as separate jobs. The main risk is a catalogue that looks complete while variation purchases or older-order enquiries fail.
Set the destination and transfer limits
WooCommerce runs on WordPress, so your destination needs hosting, a maintained WordPress installation and extensions compatible with the store you’re building. WooCommerce’s migration guide starts with that destination setup before transferring data.
Choose WooCommerce when you want control over the WordPress storefront and can assign responsibility for its maintenance. If your present platform already supports the workflow you need, compare that benefit with the work of maintaining the destination. The related WooCommerce versus Shopify guide explains the operating differences before you commit.
Transfer objects and limits
A comma-separated values (CSV) file carries tabular data. The product file is only one transfer object.
| Item | Transfer route | Retained information | Separate work |
|---|---|---|---|
| Products | Core product CSV import | Supported catalogue fields | Transform source columns and rebuild custom product behaviour |
| Customers | Customer importer extension or custom integration | Mapped account and address fields | Password resets and account matching |
| Orders | Order importer extension or custom integration | Mapped purchase records | Product/customer references and history reconciliation |
| Media | Product image import or Media Library upload | Available product images | Audit image descriptions and other content assets |
| URLs | Old-to-new URL map | Existing entry points through redirects | Configure redirect rules and test destinations |
A product CSV file is one part of the migration. It doesn’t recreate your theme, staff access or payment-provider agreement. Keep a named owner for each transfer object and each rebuilt integration.
Prepare hosting, backups and field mappings
Prepare a private destination with secure hosting, WordPress, WooCommerce, a compatible theme and the extensions needed for your actual product types. Assign an owner for updates, backups and checkout problems. Keep test emails away from customers and use the payment provider’s test environment during rehearsal.
Retain untouched source exports alongside a working copy. Back up the destination before each import stage. WooCommerce’s backup instructions cover site files and the database. A WordPress content export alone doesn’t capture the complete store. Prove that your backup can restore the private destination before depending on it.
For a Magento to WooCommerce migration, Adobe documents exporting Commerce data through System > Data Transfer > Export. Select Products and CSV, review the filters and excluded attributes, then continue the export. Customer records and addresses are separate export types. Keep the source files intact while converting a working copy into the destination format.
Hypothetical product-field map
Consider a fictional cotton shirt sold in navy, in small and medium sizes. The parent style’s stock-keeping unit (SKU) is SHIRT-01. Use this map to decide what each destination record must contain.
| Source information | WooCommerce destination | Expected result |
|---|---|---|
| Parent style SHIRT-01 | Variable product with parent SKU | One product page |
| Child SHIRT-NV-S | Variation linked to SHIRT-01 | Navy/small can be bought separately |
| Child SHIRT-NV-M | Variation linked to SHIRT-01 | Navy/medium has its own stock |
| Size, colour and fabric | Product attributes | Options and cotton detail remain available |
| Image locations | Product images | Main image and gallery remain usable |
| Clothing > Shirts | Product category hierarchy | Product appears in Shirts |
WooCommerce’s variable-product documentation explains separate variation prices, stock and images. Give each saleable variation a price. Decide whether stock belongs to the parent or individual variations before transferring quantities.
Keep hosting, domain and payment accounts under the retailer’s control. Give the migration team only the access its work needs. Record who can revoke that access after launch. Reconnect payment services through the destination’s supported gateway setup. Importing an order record doesn’t authorise future charges against its original payment method.
Import in controlled batches
Import one representative variable product before a larger catalogue batch. WooCommerce’s documented catalogue import steps define the supported file format and mapping process.
- Prepare a UTF-8 CSV using the documented schema. Set the parent type to
variableand its children tovariation, with the parent SKU in each child’sParentfield. - Open Products > All Products > Import and choose the file.
- Select Continue and review every column mapping. Unrecognised columns are ignored by default.
- Select Run the importer and wait for completion before leaving the page.
- Inspect the shirt’s size options and compare both variation records with the field map. Correct the mapping before importing larger batches.
Use reachable image files or pre-uploaded Media Library assets. Review missing images separately. When repeating an import to update products, deliberately select the update mode and match by the intended SKU or destination ID. Don’t copy source IDs into that role without a mapping.
Customers and orders need another route
WooCommerce documents the paid Customer / Coupon / Order CSV Import Suite as a separate extension. Its extension documentation supports customer fields and order history, with a dry run before records are written.
Import customers before orders and load the referenced products first. Map order lines to the destination products and link orders to the correct customer. Reusing source user or order IDs can match unrelated destination records. Keep a source-to-destination record map, and review merge settings before applying an import.
Passwords from a non-WordPress source need a reset route. Don’t ask customers to send passwords to the migration team. Review the extension’s email options so a rehearsal doesn’t send account or historic-order emails.
For custom transfer work, the WooCommerce application programming interface (API) documentation describes customer and order creation. That is a developer integration, with authentication and field transformation to implement. It isn’t a universal order-import button for every source platform. Give the integration owner responsibility for duplicate prevention, failed records and reconciliation.
Rebuild the parts an export cannot carry
Recreate shipping, tax, checkout and notifications in the destination before accepting orders. Work through your current store’s rules, including excluded postcodes, collection options, free-shipping conditions and product-specific restrictions. Record the expected basket result for each rule and use it during checkout testing.
Assign each source-specific feature to a compatible extension or a development task. Subscription renewals, loyalty balances and custom bundles need explicit treatment. Record what happens to existing commitments before retiring the source service. Catalogue import success doesn’t prove those workflows work.
Choose the destination’s URL structure before writing redirects. WordPress documents the general settings in its permalink guide. Include WooCommerce product and category paths in your design, then record every old URL beside its final destination.
For the fictional shirt, map the old /navy-cotton-shirt.html address directly to the new /product/navy-cotton-shirt/ page. Configure a permanent redirect where you control the old address. Test that it reaches the correct product without a loop or intermediate redirect. Preserve relevant category and help-page entry points too.
Restore product discovery and service context
Restore the information customers use to choose a product, then test that search and shopping assistance can use it. The shirt’s size choices, cotton attribute and variation stock must agree with its product page. Refresh connected product feeds after the final stock transfer. Replace old delivery and returns documents with the policies that apply on the new store.
shoppa is an AI shopping agent that helps customers find, compare and buy products in the chat, then get help after the sale. It uses your catalogue and store documents, with a native WooCommerce app for the destination store. After migration, ask about a specific size and a delivery restriction. The answers must agree with the new catalogue and policy documents.
Give staff a clear route to older purchases. In a hypothetical enquiry about source order M-4821, the customer supplies their order reference through your approved support process. Staff find it in the retained source archive and confirm the customer’s identity before sharing details. They use the mapped destination order when one exists, or handle the enquiry from the retained record.
A new account doesn’t prove all older purchases are visible in it. Test an imported order under its assigned customer account, and give staff a source reference when history remains outside WooCommerce. Keep archive access restricted and document who handles returns that began before the move.
Prove the store works before changing domains
Prove the full purchase and support workflow on the private destination before changing the live domain. Use the fictional navy/small shirt with variation stock set to five and backorders disabled. Keep the medium variation at a different quantity so a stock-mapping error is visible.
- Buy one small shirt through the gateway’s test environment. The order must show SHIRT-NV-S, quantity one and the expected total, including the chosen shipping and tax treatment.
- After the order reaches the configured stock-reducing status, small stock must fall from five to four. Medium stock must stay unchanged.
- Confirm the gateway test transaction matches the order amount and that the intended order email reaches the test mailbox once.
- Process a test refund through the configured gateway. The order and provider must show the same refunded amount. If you select restocking for that item, small stock must return to five.
- Open a sampled imported order and compare its customer, product references, totals and status with the retained source record. Test the customer’s account view separately.
Before cutover, agree when the source stops accepting changes. Capture the final orders and stock movements, import the remaining changes and reconcile them before opening the destination. Update feeds and integrations to the final domain, then repeat the redirect and checkout checks.
Keep the source records and a restorable destination backup through cutover. If checkout fails before launch, keep trading on the source while fixing the destination. After the new store takes orders, reconcile those orders before restoring any older backup. A restore must preserve the record of purchases accepted since that backup.
Give the store team the import error list, record mappings and recovery instructions. Escalate hosting failures to the host, importer failures to the extension maintainer and custom integration failures to its developer. Change the live domain only when the responsible owners have cleared the remaining purchase and record-access failures.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.