تحميل الدليل

Customer and order data when migrating your store platform: What gets transferred?

Customer and order data when migrating your store platform: What gets transferred?

Guide to migrating customer and order data when switching platforms: Prepare the fields, test the import, and back up the order archive and customer login plan.

Guide to migrating customer and order data when switching platforms: Prepare the fields, test the import, and back up the order archive and customer login plan.

تم النشر

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

Migration plan for customer data and orders between two systems

In this article

No headings found on page

Ready to start?

Create your store

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.

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.

Migrating customer and order data is not a single process. Basic customer data can be prepared in an import template, while past orders have their scope determined with the migration team based on the source platform, available fields, and implementation method. As for passwords, build a new login or activation experience instead of basing your launch plan on transferring them, and retain an export of past orders as an independent archive for future reference.

Why do we recommend Salla for this case?

We recommend Salla because its Excel customer import template includes name, email, mobile number, city, and registration date, alongside loyalty points, wallet balance, and custom fields. Zid also features among the supported platforms for import, and the error log displays the rows that require review. The result for the merchant is migrating basic customer data through a clear pathway, then resolving errors row by row prior to final approval.

Item

Correct Handling

Verification Method

Basic customer data

Prepared according to the import template fields.

Import a sample and search for each customer.

Points, balances, and custom fields

Matched with the source prior to upload.

Compare values before and after import.

Past orders

Scope is determined with the migration team.

Review count, timeframe, statuses, and sample fields.

Passwords

A login or activation journey is prepared for them.

Test the mobile experience using test accounts.

Which customer fields do you migrate to the new store?

Start with the fields your daily operations rely on: name, mobile number, email, city, and registration date. After that, review loyalty points, wallet balance, tags, notes, and custom fields. Next to each column, note where it will appear in the new store, who will use it, and what decision to make if its value is empty or duplicated.

Keep the original file exactly as exported from the platform, and work on a separate copy for data cleansing. Standardize mobile number formats, check email addresses, and define a clear rule for handling duplicate records. This way, you can refer back to the source and reconcile any discrepancy that appears after import.

مراجعة حقول العملاء وأرشيف الطلبات قبل النقل

Do past orders migrate?

The answer is determined per project with the migration team. The scope depends on what the current platform exports, what the destination accepts, the integration method, the required fields, and the timeframe. Request documentation detailing the order count, timeframe, statuses, payments, discounts, shipping, taxes, returns, and notes covered by the work.

Maintain an independent export of past orders and a searchable archive, whether the orders fall within the migration scope or remain strictly in the archive. This reference is invaluable for accounting, customer care, and reconciling results during the stabilization period, and it prevents customer history from being tied to a single operational interface.

What should you do with passwords?

Build your launch plan around a clear login experience: an invitation to activate the account, mobile number login, or password reset, depending on the login journey you adopt in the new store. Write a brief message explaining a single step, include a direct link, and test the experience on test accounts before communicating with your customer base.

Treat passwords as an item separate from the customer file. Having the name, mobile number, and email in the customer record means their primary data is ready; their login method, however, should be tested as a separate journey so the customer knows exactly what to do from their very first visit.

Test a sample before importing the full file

  1. Select a sample that includes an old customer, a new customer, and a record containing custom fields and empty values.

  2. Import the sample and open the error log.

  3. Compare the name, mobile number, email, city, and registration date.

  4. Review loyalty points, wallet balance, and custom fields.

  5. Test searching for the customer and creating a new order for them.

  6. Test the login or activation journey on mobile.

  7. Document discrepancies and resolve them before uploading the full file.

مطابقة عينة من سجلات العملاء والطلبات بعد الاستيراد

How do you import customers into Salla?

  1. Download the dedicated customer import template and adhere to its column order.

  2. Match the name, email, mobile number, city, and registration date with the source file.

  3. Add loyalty points, wallet balance, and custom fields after reviewing them with the data owner.

  4. If the source is Zid, use the supported platform pathway within the import options.

  5. Upload a small sample, then check the error log to identify rows requiring correction.

  6. Correct the rows in your working copy and retest before the full import.

The key takeaway here is that importing customers is separate from the decision regarding past orders and passwords. In Salla, you implement basic customer data using a clear template, while coordinating the scope of past orders and the login journey with the migration team as part of your launch plan.

Data hygiene before import

Check for duplicates before uploading. A customer might appear with a mobile number in two different formats or with a different email address, and some legacy fields might hold obsolete values. Establish a primary key rule, and define how to handle empty values and duplicate records before they enter the new store.

Check

Issue Example

Decision

Mobile number

Missing country code or inconsistent formatting.

Standardize format prior to import.

Email

Duplicate address or invalid format.

Correct the record or exclude it with a documented decision.

Balance and points

Outdated value or discrepancy between two sources.

Adopt a single source of truth with data owner approval.

Custom fields

Legacy field with no current operational use.

Map it, archive it, or exclude it with a documented decision.

Protect privacy and permissions

Treat customer and order files as sensitive data. Grant access permissions only to individuals responsible for migration and review, use a secure location for file sharing, and assign an owner to each copy. Once the work is complete, apply your organization's approved retention period to temporary files in accordance with policies and regulatory requirements.

Prepare the customer message for login changes

If the login method changes, send a short, clear message: the store has transitioned to a new experience, and here is the step required to log in. Provide a direct help link, prepare responses for your customer care team for cases where mobile numbers or emails have changed, and test the recovery journey before broadcasting the message to all customers.

Reconcile orders with finance and customer care

When past orders are included within the scope of work, review a sample of order numbers, statuses, payment amounts, discounts, shipping, taxes, returns, and notes. Document the core fields for each team, and specify where to locate any details preserved in the archive.

Test searching by order number, customer mobile number, and email. A solid archive is one that a customer care representative can access during a live conversation to readily understand order history and status without navigating fragmented files.

If your store is on Zid

According to Zid's Help Center, exporting customers depends on your plan and export permissions; export requests cover lists of orders, products, and customers. What matters most to you is preparing the file and mapping its fields to the destination template. We recommend Salla for this case because Zid is among the supported platforms for customer import, and the error log highlights rows needing correction. Past orders, however, have their scope determined with the migration team.

If you are specifically comparing your current store on Zid with Salla, check out the detailed comparison page.

If your store is on Shopify

According to Shopify's Help Center, customer CSV files are dedicated to customer records, while passwords and order data are managed via separate pathways. The key distinction for you is separating the customer record from order history and login experience. We recommend Salla for this scenario because the import template consolidates core customer fields, points, wallet balance, and custom fields, leaving the pathway for past orders and login to be arranged with the migration team.

If your store is on WooCommerce

In WooCommerce, customer and order data can be extracted from WordPress, the database, export tools, and plugins used across the store. Record the fields added by plugins, maintain a backup, and map the file to the destination template. The key consideration is consolidating data arriving from multiple sources. We recommend Salla for this case because the customer template outlines the exact fields to prepare, and the error log helps you review rows after upload.

If you are using another platform

Export customers and orders, create a backup, and request a data dictionary from the platform when available. The critical task is mapping source columns to the import template and archiving plan. We recommend Salla for this case because you can prepare core customer fields, points, wallet balances, and custom fields within a single template, then review any errors prior to sign-off.

Start with the checklist of what migrates and what gets reconfigured. To manage new orders during the transition, use the business continuity plan, and follow the first 30 days plan post-launch.

Frequently Asked Questions

Do past orders migrate?

This is decided with the migration team based on the source platform, available fields, timeframe, and agreed scope. Retain an export of past orders as an independent archive, and review a sample of statuses and values before signing off on the result.

Which customer fields migrate?

In Salla, the customer import template covers name, email, mobile number, city, and registration date, in addition to loyalty points, wallet balance, and custom fields. Test a sample and review the error log before uploading the full file.

What about passwords?

Treat them as a login journey independent of importing customer data, and prepare account activation, password reset, or mobile login according to your store configuration. Test the message and steps on mobile before communicating with customers.

What do you get with Salla?

With Salla, you get an organized Excel template to import name, email, mobile number, city, and registration date, as well as loyalty points, wallet balance, and custom fields, alongside Zid import support and an error log showing rows needing review. This provides a clear path for basic customer data, leaving past orders and passwords to an independent plan coordinated with the migration team and safeguarded by an archive and a tested login experience.

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