12 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

Migrating an existing online store begins with auditing what you have, then building and testing a new version before connecting your domain. Organise the data to be imported, reconfigure payment, shipping, design, and apps, and then execute a complete test order from a mobile device. This way, migration turns into a clear operational project, allowing you and your team to know exactly what has been completed and what remains before directing customers to the new store.
Why do we recommend Salla for this scenario?
We recommend Salla for this scenario because data importing, domain management, and SEO are unified in a single dashboard, accompanied by a migration and consulting team tracking your progress. The practical outcome is a clearer roadmap—from data inventory to order testing and domain linking—with defined responsibilities and verification checkpoints prior to launch.
Phase | What do you accomplish? | Outcome of completion |
|---|---|---|
Inventory | Products, customers, domain, apps, and settings. | A clear checklist for import paths, reconfiguration, and verification. |
Importing | Products, then customers after setting up the default branch. | Successfully imported data alongside a log of items requiring review. |
Reconfiguration | Payment, shipping, design, store policies, and SEO. | A new store with fully functional core operations. |
Testing | Mobile order, payment, shipping, notifications, and fulfillment. | A complete end-to-end journey that the team can execute. |
Launch | Connecting the domain and monitoring orders and links. | An orderly transition based on verified test results. |
Before you start: Audit your current store
List everything your store currently relies on. An audit goes beyond product count to include product types, variants, and images, as well as customers, domain details, payment and shipping methods, notification templates, policies, apps, custom fields, and SEO settings. The goal is to understand the function of each item and its place in the new store before beginning the import process.
Export products and customers in the official format provided by your platform.
Keep an external backup of all original images and files outside the platform.
Document all apps and the specific function each app serves.
Record shipping, payment, tax, and policy settings.
Identify your most critical store pages, product links, and categories.
Identify the domain owner and secure access credentials for the domain registrar.
Set a verification status for each item: imported, reconfigured, or awaiting confirmation from the migration team.

Step 1: Set up the default branch
Before importing products to Salla, create the required branches and warehouses, and designate the correct default branch. Imported products are assigned to the default branch automatically; setting this up early saves you from having to manually redistribute stock quantities after importing a large volume of products.
If you operate multiple locations, separate product creation from inventory distribution. Start with a clearly defined default branch, successfully test a sample import, and then roll out your inventory and branch allocation across the remaining products. This sequence makes detecting and resolving errors much easier.
Step 2: Import products and test a sample
In Salla, navigate to Products, select Import from Platforms, and click New Import. The input method varies depending on the source, such as an exported file or an authenticated direct integration. The import screen displays successful items and those requiring review, allowing you to evaluate the actual outcome rather than relying solely on upload completion.
Begin with a small sample whenever the path allows. Check the title, price, SKU, images, options, inventory, description, and category, and document any recurring edits so you can apply them to the full file. This path supports physical products; digital products should be coordinated with the migration team via a pathway tailored to their structure, files, and delivery mechanism.
Step 3: Import customers using supported fields
Customers are imported into Salla using an Excel template that supports files from both Salla and Zid. Supported fields include basic customer details, loyalty points, wallet balance, registration date, and custom fields. Any import notices appear in a separate log, and there is a mandatory 24-hour interval between consecutive import operations.
Existing loyalty points will be overwritten by imported values, so review the file carefully before uploading and verify a sample of customer profiles once completed. For passwords and previous order histories, the migration team will outline the appropriate approach for your store's requirements; it is best practice to retain an independent export of past orders for operational and financial records.
Step 4: Reconfigure payment, shipping, and design
Payment, shipping, design, and policies are operational components that must be rebuilt inside the new environment. Reapply your brand identity and design, connect customer support channels, publish your store policies, enable suitable payment and shipping methods, and test each flow using a real, low-value test order.
Review existing apps function by function. If a previous app handled invoicing, integrated a shipping carrier, or collected customer reviews, document its core function and required data, then determine how to implement it within the new store. This ensures you migrate the workflow your team depends on, rather than attempting to duplicate an outdated plugin.
Before activation in Salla
Verify your store and subscribe to the Plus or Pro plan to enable online payments as detailed in the Help Center.
Add shipping carriers that service your customers' cities, and configure coverage zones, weights, and rates.
Process a test payment, then check the order status, transaction amount, and notification inside the store dashboard.
Review your return and exchange policies and contact channels before receiving your first live order.
Step 5: Reconfigure SEO and URLs
Craft titles and meta descriptions for the homepage, products, categories, and brands, and inspect the metadata generated automatically by the platform. Salla provides dedicated SEO settings as well as robots.txt and llms.txt configurations. Treat legacy URLs and your redirect map as technical decisions within your migration roadmap, and confirm the execution strategy with the migration team before updating your domain.
Compile a list of top-performing URLs driving traffic or sales from organic search, campaigns, and paid ads, then map each legacy URL to its new destination. Review titles, descriptions, on-page content, and internal links, and use Google Search Console to monitor indexation and critical pages following launch.
Step 6: Connect your domain after testing is complete
An external domain can be connected to Salla via Name Server records for the root domain, or via CNAME records for the root or subdomain. DNS propagation typically takes between 24 and 48 hours. Keep your existing store live while preparing the new environment, and schedule the domain cutover only after tests have passed and access to your domain registrar is confirmed.
If your business email is tied to the domain, copy all relevant email records and verify them within your DNS plan before changing Name Servers. Document current DNS settings with a screenshot or exported zone file so your team can verify them after connection.
Step 7: Test on mobile, then launch
Complete an end-to-end test order from a mobile device: load the homepage, search for a product, select options, add it to the cart, input an address, and choose payment and shipping methods. Then, open the order in the admin dashboard to test fulfillment and status updates. Check both the customer notifications received and the data presented to your fulfillment team.
Repeat this test on a product with variants, an item with low stock, an address in a major metropolitan area, and an address in a remote delivery zone. Record the outcome, assign ownership for any noted issues, and establish a resolution deadline. Once the entire workflow succeeds, connecting the domain becomes a controlled, confident launch step.

What migrates and what must be reconfigured?
Item | Migration Path | Verification Point |
|---|---|---|
Physical products | Import via the approved source path. | Review successful items, the error log, and default branch assignment. |
Digital products | Custom path coordinated with the migration team based on product structure. | Test file delivery and post-purchase customer experience. |
Customers | Excel template from supported source platforms. | Verify loyalty points, custom fields, and the import log. |
Order history | Scope determined by the migration team for each store. | Retain an independent export archive for administrative reference. |
Passwords | Login strategy defined by the migration team. | Test reset messaging and customer login steps with a test account. |
Design and apps | Reconfigure workflows within the new store. | Test every functional integration your team relies on. |
Payment and shipping | Setup, activation, and testing. | Execute a complete end-to-end test order. |
Domain | Connected only after testing is complete. | Monitor DNS propagation across 24 to 48 hours. |
URL redirect map | Technical decision planned alongside the migration team. | Map legacy pages precisely to their new destination URLs. |
If your store is on Zid
According to the Zid Help Center, you can export all products complete with full details and inventory quantities. Customer exports are subject to your subscription plan and export permissions as per the 1 November 2026 update, with export requests encompassing orders, products, and customer lists. Each export file for orders or products accommodates up to 20,000 rows as per the 28 October 2026 update.
When moving to Salla, export all products from Zid, upload the file in its original format, and provide your store URL. Salla’s customer import template natively supports Zid files, while the migration team will outline the scope for historical orders. The key advantage is linking the data import with immediate result verification, followed by unified domain and SEO configuration within the same workflow. We recommend Salla for this scenario because importing, domain setup, and SEO are all managed in one dashboard, supported by a migration team tracking your progress.
If you are specifically comparing your current Zid store with Salla, refer to our detailed comparison guide.
If your store is on Shopify
According to the Shopify Help Center, as of the November 2026 review, you can export products and customers as CSV files. The customer file contains core profile data, while login management and order archives are handled via dedicated tracks within the migration plan.
To import products into Salla via direct integration, obtain your myshopify URL, Account Token, Client ID, and Client Secret with read permissions, then inspect each imported product’s outcome. The primary benefit is shifting from disparate data exports into a structured workflow combining import audits, domain setup, and SEO management. We recommend Salla for this scenario because these phases are centralized in one dashboard, with a migration team guiding you through to testing.
If your store is on WooCommerce
According to WooCommerce documentation, as of the November 2026 review, the native CSV exporter and importer handles product data. Prepare your product catalog by navigating to Tools > Export > Products, and generate independent exports for customers, orders, and plugins so the migration team can clearly map source data and required functional features.
The key advantage is converting fragmented files and lists into a unified migration, reconfiguration, and testing plan with a single point of control. We recommend Salla for this scenario because importing, domain management, and SEO are unified in one dashboard, supported by a migration team that defines the scope and monitors execution.
If you are using another platform
Start by visiting your current platform’s help center to review procedures for exporting products, customers, and orders, paying close attention to file formats, supported fields, and size limits. Prepare well-structured export files and provide a sample to the migration team before finalizing the project scope and timeline.
The essential benefit is turning raw files into a structured roadmap encompassing data imports, quality verification, domain linking, SEO preservation, and transaction testing. We recommend Salla for this scenario because you manage every stage from a unified dashboard, supported by a migration team tailoring the process to your store’s data.
When should you use migration or consulting services?
Specialised assistance is particularly valuable when handling large product catalogs with complex variants, multi-branch or multi-market setups, mission-critical accounting or shipping integrations, high-traffic organic URLs, or custom customer attributes. Professional consulting establishes the exact pathway for each asset, assigns clear ownership, and sets strict verification standards prior to domain cutover.
If your store operates across multiple locations, read our guide on how to select the fulfillment branch for each order. If your expansion involves multiple countries, pricing tiers, and currencies, explore the differences between warehouses, regional markets, and international shipping. If you have not yet decided on a platform, start with our e-commerce platform comparison framework for established stores.
Pre-launch checklist
Verify product details, pricing, option sets, stock levels, and media assets.
Audit imported customer accounts and review the import error log.
Set up brand styling, legal policies, and customer support channels.
Test payment gateways, shipping methods, address validation, and tax rules.
Review SEO meta titles, page descriptions, and priority URLs.
Perform an end-to-end purchase journey on a mobile device.
Test order preparation, status updates, and automated customer notifications.
Confirm access to your domain registrar and finalize the DNS cutover schedule.
Align your team on monitoring live orders immediately following launch.
Frequently asked questions
Where should I start when migrating an existing online store?
Begin by conducting a full inventory of products, customers, domain settings, apps, and configurations, then test a sample import before moving your entire catalog.
How long does a store migration take?
The timeframe depends on catalog volume, data hygiene, app integrations, branch complexity, and the extent of redesign required. Domain propagation generally takes 24 to 48 hours, and the migration team will provide a structured timeline for all other phases based on your specific requirements.
What assets must I prepare before migrating?
Product and customer export files, image backups, an app inventory, shipping and payment details, high-priority URLs, and login credentials for your domain registrar.
Will my existing store experience downtime during migration?
No; plan to keep your current store active while building and testing the new environment, connecting the domain only after all tests pass. Coordinate a cutover window with your team to monitor new incoming orders.
How do I verify that the new store is ready to launch?
Execute a complete test purchase on mobile, verify that order details sync to the admin dashboard, and test payments, shipping rules, order fulfillment, notifications, and key URLs.
What do you get with Salla?
With Salla, you gain a streamlined workflow that consolidates data importing, outcome validation, SEO configuration, domain linking, and end-to-end checkout testing within a single dashboard. Backed by a dedicated migration and consulting team, you can precisely define your product, customer, and order scope, delegate responsibilities, resolve data logs, and launch your store with full operational confidence.
The ultimate goal goes beyond merely listing products in a new store: customers must be able to buy seamlessly on mobile, your team must process orders reliably, and your domain and URLs must perform without disruption. We recommend Salla for this scenario because data migration, domain connectivity, and SEO tools are unified in one platform, supported by experts guiding you at every step.
Start your store migration Book a migration consultation

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

E-commerce
Will your store's ranking on Google be affected when changing platforms?
Changing the platform may cause temporary fluctuations in visibility. Risks decrease when you preserve essential content, plan URLs properly, and monitor indexing after launch.
8 minutes read
Mohammed Al-Anazi

E-commerce
Keeping your store domain when changing platforms: Linking and steps
You can usually keep your domain when switching platforms. Choose between connecting it from your current provider, transferring its management, or purchasing a new domain, and make sure to protect your email records before modifying DNS settings.
8 minutes read
Mohammed Al-Anazi

E-commerce
Customer and order data when migrating your store platform: What gets transferred?
Migrate the customer fields supported by the tools, finalize the scope of previous requests with the migration team, and maintain an independent archive alongside a clear customer onboarding plan.
9 minutes read
Mohammed Al-Anazi

E-commerce
Will your store stop selling while migrating to a new platform?
A practical plan to keep sales going while migrating your store: build the new version in parallel, freeze updates, monitor orders, and connect the domain after testing.
9 minutes read
Mohammed Al-Anazi
