How to migrate a WooCommerce store to Tradly

1. 1

   Step 1 · Inventory

   Audit products, variations and extensions

   List simple and variable products, attributes, categories, images, downloads and plugin-added fields. Note which extensions affect checkout, subscriptions, shipping or product presentation. Decide which information is essential for the new store and which WordPress pages can be retired or rewritten.

   Tradly: Tradly supports WooCommerce data imports; identify the records and fields supported by the import before planning the remaining work.

   ↓
2. 2

   Step 2 · Map

   Create a field map for WooCommerce data

   Map product names, SKUs, variation attributes, prices, stock status, images and categories to the destination fields. Include an example product with multiple variations and one with an extension-added attribute. Mark fields that require manual cleanup rather than assuming every plugin value has a destination.

   Tradly: Tradly’s WooCommerce import can bring supported store data into Tradly; a field map helps surface unsupported extension fields before cutover.

   ↓
3. 3

   Step 3 · Import

   Test and reconcile a representative batch

   Choose products that cover the catalog’s edge cases and run a small import. Compare source and destination product counts, option values, images, prices and availability. Track import errors in a simple table and retry after fixing the source or mapping. Keep an export of the original data for reference.

   Tradly: Tradly supports WooCommerce data imports; reconcile each test record and confirm the import scope before migrating the full catalog.

   ↓
4. 4

   Step 4 · Rebuild

   Review pages, URLs and store settings

   Recreate the navigation, policies and essential landing pages. List the most visited product and category URLs and plan redirects where possible. Reconfigure payment and shipping settings for the new storefront, and decide how orders or customer records that are outside import scope will be handled.

   Tradly: Tradly’s visual editor supports pages, layouts and checkout presentation; configure the new store’s settings and routes separately from the data import.

   ↓
5. 5

   Step 5 · AI

   Help customers through the transition

   Prepare a concise migration notice and updated answers for delivery, returns and account questions. Train an agent on current store policies and the new product pages. Ask staff to review answers that mention old URLs or checkout instructions, then update the source content before launch.

   Tradly: Tradly Agent Builder can use business pages, files and notes to answer customer questions and help with daily tasks.

   ↓
6. 6

   Step 6 · Cutover

   Run a launch checklist and retain a fallback

   Test product links, variation selection, checkout, order confirmation, mobile layout and domain behavior. Check redirects and analytics after the change. Keep the old store data and a documented fallback plan until the new site has completed a stable period of real orders.

   Tradly: Tradly supplies the new storefront and commerce workflows; verify the buyer journey and preserve your original store export for your own contingency plan.

Plus 50+ integrations, full REST API & JS SDK, and the Marketplace Kit for ready-made multi-vendor flows.