تحميل الدليل

Does your store stop selling while migrating to a new platform?

Does your store stop selling while migrating to a new platform?

A practical plan to keep selling while migrating your store: build the new version in parallel, freeze changes, monitor orders, and connect the domain once tested.

A practical plan to keep selling while migrating your store: build the new version in parallel, freeze changes, monitor orders, and connect the domain once tested.

تم النشر

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

Sales continuity plan during the relocation of an existing store

In this article

No headings found on page

Ready to start?

Create your store

A practical plan to keep selling while migrating your store: build the new version in parallel, freeze changes, monitor orders, and connect the domain once tested.

A practical plan to keep selling while migrating your store: build the new version in parallel, freeze changes, monitor orders, and connect the domain once tested.

The realistic goal when migrating your store is to keep downtime to an absolute minimum, without falsely promising zero downtime. Keep your existing store running while building the new version, establish a clear cut-off point for product edits, track orders and updates made after the initial copy, and switch the domain only after completing full testing within a monitored window with a clear rollback plan.

Why do we recommend Salla for this scenario?

We recommend Salla because it allows you to build your new store in parallel while your current store stays live: you can import products from Zid, Shopify, WooCommerce, and Magento via “Products → Import from Platforms”, then review a report detailing successfully migrated items and any failed rows. After testing, you connect the domain as the final step, supported by the migration team on launch day. For merchants, this isolates the build phase from traffic cutover and drastically minimizes zero-hour changes.

Phase

Sales Status

Action

Build

Current store continues taking orders.

Set up products, design, payments, and shipping on the new store.

Freeze

Sales continue under a monitoring plan.

Freeze product edits and record incoming orders and new changes.

Delta Sync

Monitored migration window.

Process updates that occurred since the initial export according to the agreed scope.

Launch

Traffic routed to the new store.

Connect the domain and test orders, payments, shipping, and customer notifications.

Build the new store in parallel

Use the temporary URL of the new store to configure products, design, payment gateways, shipping methods, and store policies. This allows customers to continue using the current store during preparation, turning the domain switch into a calculated launch step once all testing is verified.

Run a complete end-to-end test journey before migration day: open the store on mobile, search for an item, add it to the cart, complete payment, check the customer confirmation message, and then process fulfillment, shipping, and cancellation. Record the outcome of each test along with the designated team member responsible for fixes.

تشغيل متجرين بالتوازي خلال تجهيز النسخة الجديدة

What happens to new orders during migration?

Set a strict cut-off point for the initial data export. After this point, new orders will be placed, new customers may register, and product prices or inventory levels might change on the current store. Consolidate these deltas into a clear log detailing everything added or changed between the cut-off time and launch.

Prior to the final import, freeze all product, pricing, and variant edits on the source store as much as possible, appointing an owner to approve any critical modifications. If stock or pricing changes during this window, record it immediately to ensure it is reflected in the new build before traffic is redirected.

What is a change freeze?

A change freeze means content, inventory, and pricing teams temporarily pause creating new products or modifying options, prices, and images, while continuing to process orders according to plan. The goal is to stabilize the data set undergoing final review prior to launch, avoiding duplicate, conflicting versions of the same product.

Define clear start and end times for the freeze, document allowed exceptions, and assign someone to log any emergency adjustments. This log will serve as the single source of truth for the data lead during final reconciliation.

Use maintenance mode for short windows

When you opt for a brief cutover window to pause incoming orders during domain propagation or final validation, enable maintenance mode with a clear message for customers. In Salla, you can turn on maintenance mode and customize the title and message displayed to visitors. Pick a low-traffic period, track the window closely minute by minute, and reopen the store once acceptance gates pass.

Write direct, helpful copy: state that the store is undergoing planned maintenance, give an estimated return time, and provide a direct contact channel for urgent inquiries. Focus on guiding the customer on what to do rather than explaining technical DNS or import steps.

Zero-hour launch plan

  1. Halt product and stock edits on the source platform at the agreed cut-off time.

  2. Export new orders, customers, and delta changes based on the approved migration scope.

  3. Import the scoped delta data and review the error logs and import results.

  4. Reconcile products, pricing, stock levels, and primary variants.

  5. Test payments, shipping, and run a complete test order from mobile on the staging link.

  6. Obtain acceptance sign-off from the launch lead and operational stakeholders.

  7. Update DNS settings according to the documented routing plan.

  8. Verify the homepage, product pages, cart, checkout flow, and automated notifications.

  9. Monitor incoming live orders, logging any discrepancies, assigned owners, and resolution times.

Pre-launch checklist on Salla

  1. Initiate product import via “Products → Import from Platforms”, selecting your source platform: Zid, Shopify, WooCommerce, or Magento.

  2. Review the import report to identify successful items and failed rows, resolving each discrepancy prior to final testing.

  3. Configure payment methods, shipping rates, policies, and notifications, verifying them thoroughly on the temporary link.

  4. Enable maintenance mode with a clear title and custom message whenever a short window is required for final verification.

  5. Coordinate freeze and cutover schedules with the migration team, designating owners for decision-making, testing, and rollbacks.

  6. Point the domain only after end-to-end checkout and operations testing are verified, keeping it as the final milestone.

What is a rollback plan?

Keep your legacy platform subscription active along with its database and previous DNS records until the new store is proven stable. Define who holds the rollback authority, what critical triggers invoke the plan, and how to reconcile any orders placed on the new store before initiating the rollback.

Document the process step by step: reverting DNS records, reopening the legacy storefront, reviewing orders captured during the window, and briefing customer support teams. Having an explicit plan equips the launch lead to make confident, fast decisions if a critical failure occurs.

خطة إطلاق ورجوع لمتجر إلكتروني بعد النقل

Launch day responsibilities matrix

Role

Responsibility

Intervention Trigger

Launch Lead

Go / No-go, delay, or rollback decision.

Upon acceptance gate sign-off or if a critical bug emerges.

Data Lead

Final delta import, error handling, and reconciliation.

Immediately prior to the domain cutover.

Domain Lead

Update DNS records and back up historical configs.

Following sign-off on pre-launch tests.

Operations Lead

Testing order placement, fulfillment, payment, and shipping.

Before and immediately after domain cutover.

Customer Support

Monitoring communications and guiding customers through changes.

From minute one post-launch.

Acceptance gates before routing traffic

Connect the domain only after completing a structured test suite: standard and variant products, coupon and discount redemptions, primary and regional delivery zones, default and alternate payment gateways, customer transactional notifications, and fulfillment workflows. If a high-impact test fails, resolve the root cause or postpone cutover until the journey is fully stable.

How to track orders across both systems?

During the DNS propagation window, maintain a unified tracking sheet logging order numbers, timestamps, the receiving platform, status, and assigned owner. Once propagation completes, reconcile the spreadsheet against both backends and assign an owner to any pending orders still being fulfilled.

Place a genuine low-value test order once the new store goes live, closely auditing payment processing, messaging, fulfillment, and shipping integrations. Validate results before launching marketing campaigns or scaling paid traffic.

If your store is on Zid

Zid offers standard export tools for products, customer data, and export orders. Use official export files, fix your cut-off time, and record any new orders and changes occurring post-export. The critical factor is handling the delta transfer between source files and your new store during the cutover window. We recommend Salla for this transition because you can import products directly from Zid via the products dashboard, review the migration outcome, and connect your domain post-testing in coordination with your migration team.

If you are specifically evaluating Zid against Salla, check our detailed comparison page.

If your store is on Shopify

The Shopify Help Center launch checklist highlights capturing delta changes after the cut-off point, providing a practical framework to manage items updated after the initial sync. The critical element is logging and merging these deltas into your launch plan. We recommend Salla here because you can import products from Shopify directly within your dashboard, verify import integrity, and leave the domain cutover as the very last step after end-to-end testing.

If your store is on WooCommerce

WooCommerce allows you to create complete file and database backups and spin up staging environments for testing prior to DNS updates. The vital task is reconciling products, stock levels, and order histories between your source and new store. We recommend Salla because product imports from WooCommerce are handled smoothly via built-in platform import tools, giving you clear visibility over migration results before changing DNS records.

If you are on another platform

Determine how you will export products, customers, and orders, establish your cut-off window, maintain a delta log, and outline a DNS fallback plan. The primary factor is balancing what automated migration tools cover versus what requires tracking in your cutover checklist. We recommend Salla because our dedicated onboarding team assists with your plan, letting you build and thoroughly test before redirecting domain traffic.

Start by completing the Data & Settings Checklist, finalize your DNS rollout plan, and follow through with your 30-day post-launch stabilization roadmap.

Frequently asked questions

Should I stop selling during migration?

Keep your current store operational while configuring the new version. Choose a tight, monitored window for the final data sync or domain switch only when the rollout plan requires it. The objective is to minimize disruption through clear messaging and a dependable rollback strategy.

What happens to orders placed during cutover?

Establish a hard cut-off point, freeze product edits before the final delta import, and log all new orders, customers, and updates created afterward. Work with your migration team to define whether these are synchronized manually or archived based on your agreed scope.

What is the rollback plan?

Maintain your existing subscriptions, backups, and previous DNS records. Clearly designate rollback triggers, approval owners, and the operational procedure for managing any orders placed on the new store prior to reverting.

What do you get with Salla?

With Salla, you get a parallel build environment, direct product import from Zid, Shopify, WooCommerce, and Magento, a transparent results dashboard tracking migration status and failed items, customizable maintenance mode, and hands-on migration team support on launch day. Keep the domain update as your final milestone, manage your freeze window, delta log, and rollback plan, turning continuous business operations into the product of sound execution rather than empty promises.

Start Your Store Migration   Book a Migration Consultation

Mohammed Al-Anazi

Product Manager at Salla

80

Article

Featured author

Turn what you read into real sales

Start your store on Salla today and put what you learn into practice, step by step.

Turn what you read into real sales

Start your store on Salla today and put what you learn into practice, step by step.

Turn what you read into real sales

Start your store on Salla today and put what you learn into practice, step by step.

In this article

In this article