To help your internal operations up-and-running on SHOPLINE in the fastest way and also ensure a smooth transition for your customers, SHOPLINE simplifies this process with the user-friendly application, Multi-platform Store Migration, which is designed to migrate data from your current platform with ease. This one-click store migration tool currently supports migration from Shopify, LightSpeed, WooCommerce, and Shoplazza to SHOPLINE.

This article will walk you through the migration process for Shopify and Lightspeed. For the migration of your WooCommerce or Shoplazza store, refer to Migrating Your WooCommerce Store to SHOPLINE and Migrating Your Shoplazza Store to SHOPLINE, respectively.

 

In This Article

• Migrating Your Shopify Store to SHOPLINE
• Considerations and FAQs for the Migration of Shopify Stores
• Migrating Your Lightspeed Store to SHOPLINE

 

---

 

Migrating Your Shopify Store to SHOPLINE

The Multi-platform Store Migration app is an auxiliary tool that helps you quickly migrate your Shopify store to SHOPLINE. You can migrate data of multiple modules, including products, customers, blogs, custom pages, logistics and delivery settings, orders, 301 redirects, and store files. It also supports retaining the product Feeds of and data reporting to the Google platform, ensuring your original advertising effect and minimizing the risk of data damage of placed ads.

Please refer to the next section for important considerations before you proceed to migrate from the Shopify platform. Then follow the steps below for migration:

Obtaining Relevant Permissions from Your Shopify Store

1. You need to create a private Shopify app in order to query and obtain the data of your Shopify store. Go to Settings, click Apps and Sales Channels > Develop apps.
   
   
   
2. Click Create an App in the upper right corner, specify an App name for your identification in the pop-up window, and then click Create app.
   
   
   
3. In the Overview tab of the app creation page, and click the Configure Admin API scopes button. Alternatively, go to the Configuration tab of the app creation page, and click the Configure button next to Admin API integration.
   
   
   
4. Select the API scopes that you want to assign to the app and click Save.
   
   
   
5. On the same page, click Install app in the upper right corner. Alternatively, go to the API credentials tab page and click Install app.
   
   
   
6. Copy the API token from the Admin API access token section. And copy the API key from the API key and secret key section. Now, you’ve obtained the API key and password. Go back to your SHOPLINE admin panel to finish the migration.
   

 

Using the Multi-platform Store Migration App

1. After creating your SHOPLINE store, don’t set up the store yet. Go to the App Store in the SHOPLINE admin panel to install the Multi-platform Store Migration app.
2. The app opens in a new tab after successful installation. Now we are going to authorize your Shopify store. Select the Shopify option and click the Start migration button.
   
3. Enter the domains of your Shopify store (e.g., [sample].myshopify.com), paste the API key (Shopify-API key) and password (corresponding to Shopify-Admin API access token) you obtain into the migration tool app in your SHOPLINE admin panel, and click Next step.
   
   
   

   Note: Assuming your store domain is “https://xxxx.myshopify.com/”, “xxx” is your store handle. You can choose to enter “sample”、“sample.myshopify.com”、“admin.shopify.com/store/sample” in the text box.

4. Select which module(s) you want to migrate.
   • For basic module migration, you can choose to migrate data from different modules, such as customers, products, logistics, custom pages, blog posts, orders, and 301 redirects.
     
     
     
     • To migrate data of orders, you need to migrate the customer and product modules at the same time to ensure data alignment. You also need to make sure that the currencies used in your Shopify store are consistent with those used in your SHOPLINE store. After the orders module is migrated, you can view and manage the orders and perform data analysis from your admin panel.
     • You can migrate metafield data corresponding to customers and products. Before the migration, you need to define metafields from your admin panel so that they can be viewed and managed post-migration. If you haven’t defined metafields before migration, the data can’t be viewed from your admin panel later.
     • You can migrate the 301 redirect settings to ensure that the corresponding link jumps normally after migration.
   • For merchants on Google Shopping Ads, SHOPLINE provides the one-click migration of GMC Feed to ensure that the product data synchronized to GMC before and after migration is consistent, and does not affect the effect of ads already placed before migration. You need to follow your configurations on Shopify. Make sure to migrate the product module for your Google Feed to work as expected.
     
     
     
     • Before the Google Feed migration, you should switch your GMC account language to English and download product Feed for backup so that you can compare the data and evaluate the migration results afterwards.
     • Currently, SHOPLINE supports two Feed synchronization methods of Shopify. The first is Google's official synchronization method, which uses product ID in a fixed format for synchronization and requires the information of the corresponding sales region to be filled in. The second is the feed synchronization plug-in, Simprosys Google Shopping Feed in the Shopify App Store, which offers three options for product ID synchronization. You can choose any of the options according to your actual use. If you choose the standard format, the sales region code is required to be filled in. You can view the Feed ID format on GMC to view the previously synchronized item ID style.
5. After making your selections for migration, click Start Migration to migrate the store.
6. Once migrated, you can further optimize the store website configurations, including basic store template configuration, payment configuration, advertising pixel settings, Meta verification, sitemap submission, and Facebook Feed synchronization. The advertising Pixel settings need to remain consistent with the original platform ID.
7. If you have connected custom domain names to your Shopify store, you can connect them to your SHOPLINE store.

 

---

 

Considerations and FAQs for the Migration of Shopify Stores

Issues Related to Migration of the Orders Module

• The data of migrated orders will be displayed 24 to 48 hours after your migration is completed.
• The migrated Shopify orders and the amount will be created in a customized payment method by default. Although you can refund these orders, no actual refunds will be generated. You need to complete the refund operations offline or on the Shopify platform.
• In the event that migration of the products or customer in an order fails, the order will still be migrated and created, but with a custom customer and custom products. This may lead to order shipping or refund failures because there are no matched products related to the shipment or refund.
• At present, migration of the logistics method field is not supported, but that of the logistics status is supported.
• At present, migration of the order return status is not supported, because Shopify doesn’t provide the interface for inquiring order returns.
• How many Shopify locations can be migrated is based on the number of locations included in the plan you have purchased for your SHOPLINE store. If the number of locations for your SHOPLINE store is less than that of your Shopify store, location migration will fail.
• At present, product images are not displayed on the order details page for POS channel orders.
• Please turn off the order-related email notifications in Settings > Notifications in your SHOPLINE admin panel before the order migration.
• When products in a Shopify order are removed, the migrated order retains the activated/listed status in SHOPLINE, because the Shopify interface doesn’t provide product status information. This may result in a partially paid or partially shipped status of the order after the migration, because a removed product doesn’t have payment or shipping information.
• In Shopify, orders are displayed in the same currency as they are paid in. However, migrated orders will be displayed in the currency configured for your SHOPLINE store, which may result in inconsistencies with your Shopify order currency. 
• The migration of multi-currency orders is supported. However, cancellations and refunds for these orders are not yet supported (this feature will be available starting July 31, 2024), which may result in inconsistencies with your Shopify order statuses.

 

Other Issues

• When synchronizing Feed, the ID synchronization rules on Shopify must be used. Incorrect and inconsistent rules may affect the effect of placed ads. If the product ID rule setting fails and has already been synchronized to Google Merchant Center, you can delete or keep the data and then set the correct rule again for re-migration. New data will overwrite the current data.
  
• Before GMC Feed synchronization, you can download a feed copy from GMC for backup. After the migration and synchronization are completed, you can complete the information by supplementing the feeds, hence minimizing the impact of migration. For example, you can synchronize fields that aren’t currently supported by automatic feed synchronization (such as product types and custom tags) by supplementing feeds.
• Repeated migration will overwrite data. For example, product A is migrated to SHOPLINE, and you  modified it in SHOPLINE. If you migrate product A from Shopify again, the product A modified in SHOPLINE will be overwritten with new data. If other migration tools were used previously, such as spreadsheet import and Shopify one-click migration feature of the Products module, the Feed ID rule for previously migrated items will not take effect.
• After migrating the customer data from the Shoplazza store, customers need to verify their email to activate their accounts by email since the data come from two different systems. You can go to Settings > Customer account > Classic customer account in the SHOPLINE admin panel, and select the Activation method option. Customers can then reactivate their account with the verification code sent via email when trying to log in your store.
  

  Note: Before the migration, please turn off all the subscription-related email notifications (Settings > Notifications), so as to avoid sending emails to customers during the migration before it is completed.

• For the migration of logistics settings, only the general plans are migrated. Custom plans configured based on products are not supported. Migration is not supported when both a general shipping plan and a custom shipping plan exist at the same time.
• Your SHOPLINE store needs to enable phone number sign-in. Otherwise, customers who registered with only phone numbers are not able to login after your store migration. You can go to Settings > Customer account to check the configuration.
• Refer to the table below for detailed sorting rules for smart collections and manual collections. You can reconfirm product sorting from your admin panel to avoid a decrease in order conversion due to incorrect migration sequence.
  
  • Sorting rules supported for migration:
    

    Sorting Rules	Smart Collection	Manual Collection
    Custom sorting	✘	✔
    Hot-selling	✔	✔
    Conversion rate	✘	✘
    Product Name	✔	✔
    Time of creation	✘	✘
    Time of update	✘	✘
    Selling price	✔	✔
    Views	✘	✘
    Add-to-carts	✘	✘

• • Classification rules of smart collection supported for migration:
    

    Classification Rules	Supported (Y/N)
    Product title	✔
    Selling price	✔
    Original price	✔
    Tag	✔
    Inventory	✔
    Brand (Vendor)	✔
    Variant weight	✔
    Variant name	✔
    Time of creation	✘
    Sales quantity	✔ (Supported after order migration)
    Views	✘
    Add-to-carts	✘
    Product type	✔ (to be supported)
    Custom product type	✔
    Metafield	✔

FAQs

Why is the displayed quantity of migrated products inconsistent with the actual number of migrated products?

The quantity of migrated products includes the quantity of products, SKUs, categories, and binding relations between products and categorization.

Why does the number of customers displayed in the admin panel differ from the number of migrated customers?

Because customer statistics are not updated in a real-time manner, there is a data delay of about 1.5 hours (for example, if 40,000 customer data is migrated, the total number displayed in the admin may be only 20,000, and it will take over an hour for the data to be updated and displayed correctly).

Why is the status of migrated customers “disabled”?

It means this customer isn’t activated in Shopify, so it is deactivated in SHOPLINE. The term for this status has been optimized “not activated” for improved customer experience. Start another migration to overwrite the obsolete status.

 

---

 

Migrating Your Lightspeed Store to SHOPLINE

Here are the steps you can take to migrate your Lightspeed store:

Generating a Token in the Lightspeed Admin Panel

1. Log in to your Lightspeed admin panel, click the gear icon (Setup) from the left navigation bar, and click through Personal tokens > Add personal token.
   
   
   
2. Name this token and click Generate personal token in the upper right corner.
   
   
   
3. In the pop-up window, copy and save the token for later use.
   

Using the Multi-platform Store Migration App

1. After creating your SHOPLINE store, don’t set up the store yet. Go to the App Store in the SHOPLINE admin panel to install the Multi-platform Store Migration app.
2. The app opens in a new tab after successful installation. Now we are going to authorize your Lightspeed store. Select the Lightspeed option and click the Start migration button.
   
3. Fill in your Lightspeed store domain, paste the token just generated, and click Next step.
   
   
   
4. You can migrate data of the customers, products, and orders modules. Once you finish your selection, click Start Migration. Please be patient as it may take a while for data to be migrated.
   
5. You can terminate an ongoing migration, for example, when the settings are incorrect or there is too much data that you don’t want to migrate at the moment.
6. The migration may fail if the request times out or the data formats are not matched. You can solve the problem by retrying. If the problem can’t be solved, you can reach out to our Merchant Success team for assistance.