How to migrate from Shopify to Tradly

1. 1

   Step 1 · Inventory

   List what must move and what can be rebuilt

   Export or document products, variants, images, categories, pages, policies, URLs, payment settings and integrations. Separate active catalog data from historical orders, customer records and app-specific fields. Make a migration checklist with an owner for each item instead of assuming every record moves automatically.

   Tradly: Tradly supports Shopify data imports; confirm the exact supported records and fields with the current import workflow before scheduling the move.

   ↓
2. 2

   Step 2 · Map

   Match Shopify fields to the new catalog

   Create a mapping sheet for product titles, descriptions, identifiers, options, prices, images and categories. Decide how unavailable fields will be represented and identify duplicate or incomplete records. Test products with multiple variants and different image arrangements, not just a simple item.

   Tradly: Tradly’s Shopify import can bring supported store data into the new catalog; use a field map to find records that need cleanup or manual work.

   ↓
3. 3

   Step 3 · Import

   Run a test batch and reconcile it

   Import a small, representative set first. Compare source and destination counts, prices, option names, images and product URLs. Record any rejected or transformed fields and correct the source or mapping before importing the full catalog. Keep a dated export so you can compare after each iteration.

   Tradly: Tradly supports Shopify data imports; review the imported batch and confirm its limits before proceeding with the full catalog.

   ↓
4. 4

   Step 4 · Rebuild

   Prepare pages, payments and customer paths

   Recreate the navigation, policies, checkout settings and essential landing pages in the new storefront. Set up the domain and decide how old URLs should redirect where supported. Check payment gateway configuration separately because saved payment methods and provider settings may not transfer with product data.

   Tradly: Tradly includes a visual editor for pages, layouts and checkout; payment settings and URL changes should be configured and tested for the new store.

   ↓
5. 5

   Step 5 · AI

   Use AI to review catalog and support gaps

   Ask an agent to answer product questions from your updated listings and policies. Use an AI assistant to summarize repeated pre-migration support issues or flag product descriptions that still mention the old process. Review every suggested change against the source data before publishing it.

   Tradly: Tradly Agent Builder can use your business files and pages to answer customers and help with daily tasks.

   ↓
6. 6

   Step 6 · Cutover

   Test orders, redirects and rollback steps

   Before switching traffic, test product pages, variants, checkout, order notifications, mobile layout, domain and any redirects. Write down how to pause the change and restore the previous storefront if a critical issue appears. After cutover, monitor orders and customer messages closely.

   Tradly: Tradly provides storefront and commerce workflows for the new site; test the complete buyer journey and keep a source backup for your own rollback plan.

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