9 min read

Mohammed Al-Anazi
Product Manager at Salla
Would you like to read a summary of the article?
Summarize with ChatGPT
Summarize it with Claude
Summarize it with Perplexity

What gets transferred when migrating a store? Data supported by the source and destination tools will be migrated, such as physical products and certain customer fields. Payment, shipping, design, applications, and policies will need to be reconfigured. The migration team will define the scope for historical orders, custom fields, digital products, reviews, and long-form content, supported by a dedicated plan for passwords, URL mapping, and the project timeline.
Why do we recommend Salla for this scenario?
We recommend Salla for this scenario because you benefit from a structured data import process, supported by a team that outlines what gets transferred and how it is verified. The outcome is a clear action item for every component: an import path, a reconfiguration step, a scope confirmed by the migration team, or a dedicated pre-launch plan.
Classification | Examples Mentioned in the Article | Correct Action |
|---|---|---|
Migrated via Import | Physical products and certain customer fields. | Test a sample, then review the results log. |
Reconfigured | Payment, shipping, design, policies, and apps. | Build the functionality in the new store and test it. |
Defined with the Migration Team | Historical orders, custom fields, digital products, reviews, and long-form content. | Approve a written scope and verification method for each item. |
Dedicated Plan | Passwords, URL mapping, and project timeline. | Define the procedure and success criteria prior to launch. |
Start with a Single Inventory List
Create a spreadsheet for every asset your store relies on: products, variants, images, customers, orders, domain, payment, shipping, design, policies, apps, notifications, reports, and SEO settings. Next to each item, document its current owner, export method, import method into the new store, who will verify it, and the fallback plan if fields do not align.
This step separates data migration from operational migration. Having products visible in the new store is only one part of the project; it must be followed by testing payments, shipping, customer login, order fulfilment, domain pointing, and URL redirects.

What Gets Migrated via Import?
Start with physical products, as they have well-defined import paths in this context. Review the title, price, SKU, variants, stock quantity, description, category, and images. Then proceed to customers according to the fields accepted by the destination template, such as name, contact details, registration date, and supported attributes.
Test a sample before uploading the complete file. Select around twenty products representing various types, such as simple products, variable products, low-stock items, and products with multiple images. This sample will uncover encoding, variant, and image issues, providing a repeatable fix that can be applied to the remainder of the file.
What Needs to Be Reconfigured?
Payment: Enable the appropriate payment gateways, review verification and settlement terms, and process a test transaction.
Shipping: Set up courier services, delivery zones/cities, shipping rates, weight tiers, and free shipping policies.
Design: Rebuild the theme, navigation menus, and pages within the new store.
Apps: Outline the core function of each app, then reimplement that functionality in the new environment.
Policies and Messaging: Review policy texts, links, notification templates, and contact information.
What Is Defined with the Migration Team?
Place historical orders, custom fields, digital products, reviews, and long-form content within a scope confirmed by the migration team. Request a written response for each item: Is it included in the scope? Which fields are supported? From what date? How will it display? And what is the verification method? Additionally, retain a searchable export as an operational archive for past orders.
This clear definition prevents assumptions from becoming broad, unmet promises. The scope for a store selling physical goods with minimal fields will naturally differ from a store with digital products, reviews, custom customer attributes, and an extensive order history.
What Requires a Dedicated Plan?
Establish dedicated plans for passwords, URL mapping, and the project timeline. The migration team will define the customer login experience, URL mapping will redirect legacy pages to their new destinations, and the project schedule will be built around data volume, file quality, and the number of configurations and apps.
Document the customer login notification, the assigned support messaging, a mapping sheet of key URLs and their targets, project milestones, and the sign-off criteria for each phase. This ensures that every item is a measurable decision rather than a vague declaration of completion.
How to Verify After Migration?
Compare product and customer counts between the source and destination, accounting for any discrepancies.
Inspect a representative sample of simple, variable, and low-stock products.
Search for an existing customer record and verify the fields that were imported.
Place a complete test order from a mobile device through to checkout, fulfilment, and notification delivery.
Review essential pages and URLs both within the storefront and via search engine results.
Log any issues along with the assigned owner, priority level, and resolution deadline.

Handover Sheet: Data Owner vs. Operations Owner
Assign an owner to each functional area. The content team checks titles, descriptions, and imagery; the operations team verifies pricing, inventory, and branch allocations; the customer service team reviews customer profiles and the approved scope for order history; and the technical team oversees domains, redirects, and integrations. Having clear ownership ensures every item is properly verified following import or setup.
Functional Area | Owner | Acceptance Criteria |
|---|---|---|
Products | Content & Merchandising | Sample verification matching title, price, variants, and images. |
Inventory | Operations | Stock count reconciliation across branches/locations. |
Customers | Customer Service | Sample search verifying successfully imported fields. |
Test Order | Operations & Finance | End-to-end order placement, invoicing, and settlement. |
Domain & URLs | Technical & Marketing | Verification of redirects, business email, and analytics tracking. |
When Is an Item Considered Fully Migrated?
An item is considered complete when it appears in the correct location, can be used by the team, matches the source data in sample tests, and functions properly within the new store. A fully migrated product incorporates the name, price, images, variants, and stock levels. For an imported customer, all template fields must be validated, and the login experience tested against the approved plan.
Keep a record of acceptable variances. You may decide to archive a legacy field that is no longer required for day-to-day operations, or retain historical orders in a searchable export file per the migration team's recommendation. The priority is that every decision is documented and agreed upon prior to go-live.
Before Launching on Salla
Prepare the physical products file and validate a sample covering all product types and variants.
Map customer fields against the import template and review a sample post-upload.
Obtain a written scope from the migration team regarding historical orders, custom fields, digital products, reviews, and long-form content.
Reconfigure payment, shipping, design, apps, and policies, then complete an end-to-end test order on a mobile device.
Approve the customer login plan, URL redirect mapping, and project timeline prior to launch.
If Your Store Is on Zid
According to the Zid Help Centre, export paths exist for products, customers, and export requests, with eligibility, permissions, and file size limits depending on your plan and export type. Export official files with their native structure, preserve an untouched master copy, and test the fields supported by the destination template. The migration team will define the scope for historical orders.
The key distinction is transitioning from raw export files to an import and verification checklist with clear ownership and acceptance criteria. We recommend Salla for this scenario because you gain a structured data import workflow alongside a team that defines what is in scope and how it is validated.
If you are specifically comparing your current Zid store with Salla, explore our detailed comparison page.
If Your Store Is on Shopify
According to the Shopify Help Centre, you can export products and customers in CSV format. Use the customer export file for contact profiles, and implement a dedicated plan for the customer login experience and historical order archives. Document installed apps and custom features within your operational inventory so the respective owners can review them.
The key distinction lies in linking CSV files to a verification plan covering sample products, customer fields, and reconfigured features. We recommend Salla for this scenario because the import process is structured, and the migration team defines the scope of each item along with criteria to confirm success.
If Your Store Is on WooCommerce
According to WooCommerce documentation, the native CSV tool handles importing, exporting, and bulk updating products. Use this path for products, record all active plugins and custom fields in your inventory sheet, and generate a full backup prior to making any updates.
The key distinction is converting your product files and plugin list into separate workflows for importing, reconfiguring, and testing. We recommend Salla for this scenario because the migration team outlines the scope, assigning each item to a responsible owner with clear acceptance criteria.
If You Are Using Another Platform
Search your platform's help centre for export, import, backup, and domain management guides. Request a sample export file, then review its schema and fields with the migration team prior to agreeing on scope or launch deadlines.
The key distinction is ensuring that sample testing precedes commitments, and that the scope for each item is established in writing before execution. We recommend Salla for this scenario because data migration follows a structured plan, supported by a team that outlines what is covered and how the results are verified.
Next Steps
Review the step-by-step store migration guide to organise your migration phases from preparation through to launch.
Frequently Asked Questions
What data gets migrated?
The imports outlined in this guide cover physical products and specific customer fields, depending on the capabilities of the source and destination tools. Test a sample, then verify the fields and outcomes before running the complete file.
Do payment, shipping, and app settings transfer over?
No. Payment, shipping, and applications must be reconfigured directly in the new store, followed by testing each integration and executing a complete test order via mobile.
What needs to be reconfigured?
You must reconfigure payment gateways, shipping methods, store design, policies, applications, automated notifications, SEO settings, and domain connections once testing is concluded.
How do I verify the migration?
Compare record counts, inspect representative product samples, place a complete mobile test order, and document any variances or observations prior to launch.
What Do You Get with Salla?
With Salla, you benefit from a structured import path for physical products and key customer fields, comprehensive audit logs, sample data testing, and an onboarding team that clarifies the scope and verification method for historical orders, custom fields, digital products, reviews, and long-form content.
We recommend Salla for this transition because every component is clearly categorised: direct import, reconfiguration, migration team scope, or a dedicated plan. This ensures success is measured through concrete sample reviews, an end-to-end test order, and clear ownership for every area.
Start Migrating Your Store Book a Migration Consultation
Multi-warehouse, multi-marketplace, and international shipping: What’s the difference?
9 minutes read
Multi-branch inventory management: How to select the fulfilling branch for each order?
11 minutes read
What gets migrated when you change your store's platform, and what do you need to set up again?
9 minutes read

Mohammed Al-Anazi
Product Manager at Salla
73
Article
Featured author

Multi-warehouse, multi-marketplace, and international shipping: What’s the difference?
A clear comparison between multi-warehouse, multi-market, and international shipping readiness—what each option solves and what it doesn't.
9 minutes read
Mohammed Al-Anazi

Multi-branch inventory management: How to select the fulfilling branch for each order?
A practical method for selecting the fulfilling branch for each order based on proximity, stock levels, or priority, as well as configuring delivery and pickup zones and multi-item shipments.
11 minutes read
Mohammed Al-Anazi

What gets migrated when you change your store's platform, and what do you need to set up again?
Categorise your store's data before migration into four tracks: import, reconfigure, confirm with the migration team, and non-viable items.
9 minutes read
Mohammed Al-Anazi

POS Software and Online Store: How to Unify In-Store Inventory and Online Orders?
A practical guide to choosing a POS system that syncs showroom and online store inventory, featuring scenarios for last-item stock, returns, offline mode, shifts, and multiple branches.
18 minutes read
Mohammed Al-Anazi
