Migrating Your Shoplazza Store to SHOPLINE

SHOPLINE offers a one-click store migration tool, Multi-platform Store Migration app, that lets you quickly migrate your Shoplazza store's products, customers, orders, and other data to SHOPLINE, without manual data entry. It also keeps your Google Ads data consistent so your ad traffic isn't affected. With this tool, you can complete the entire migration process — from authorizing your Shoplazza store and selecting the modules to migrate, to handling the migration results. 

This guide walks through the overall migration process, including preparing your store before migration, getting your Shoplazza store authorization information, selecting the modules to migrate, and the follow-up setup needed after migration.

For the migration of your WooCommerce or Shoplazza store, refer to the following articles respectively:

• Migrating Your Shopify Store to SHOPLINE
• Migrating Your WooCommerce Store to SHOPLINE

Overview of the Shoplazza Migration Process

Migrating from Shoplazza to SHOPLINE consists of the following 7 stages:

Preparing Your Store for Migration

Before starting the migration, complete the following preparations to avoid disrupting your store's normal operations during the data migration:

• Turn off email notifications: Turn off email notifications in the SHOPLINE admin and any third-party apps (such as CRM or Smartpush) to avoid disturbing customers with notifications triggered by the incoming data.
• Notify your payment channels: Notify your payment channels that your store will be switching SaaS platforms, to avoid affecting payment functionality.
• Back up ad data (optional): Before migrating, back up your original ad channel Feed files and confirm your original product IDs. You can use these as a reference to verify that your ad data migrated successfully.
• Clear product data (optional): If you need to migrate your Feed, products written by apps other than the migration tool can't be matched to the Feed. Be sure to clear your SHOPLINE product data beforehand.
• Migrate your domain (optional): If your domain was purchased through or renews on Shoplazza, migrate it to a third-party provider first.

Obtaining Shoplazza Migration Credentials

Before selecting the modules to migrate, create a custom app and generate a token in the Shoplazza admin so the store migration tool can read your store data:

1. Log in to the Shoplazza admin and go to App > Manage Private Apps.
   
2. Click Create App to open the custom app creation screen.
   
3. Enter a custom Private app name and Emergency developer email.
   
4. Configure the API access permissions in the admin: set every permission to Read and write, then click Install App.
   
5. After the app is created, copy the generated Token. You'll use it to complete store authorization in SHOPLINE in the next step.
   

Authorizing Store Migration in SHOPLINE Admin

After creating the app in Shoplazza, go back to the SHOPLINE admin to complete store authorization for the migration tool:

1. Go to the SHOPLINE App Store and install Multi-Platform Store Migration.
2. On the app's page, select Shoplazza as the migration platform, then click Start Migration.
3. Enter your Shoplazza store domain (for example, if your store domain is sample.myshoplaza.com, enter just "sample").
4. Paste the Token you copied in the previous step, then click Next to move on to module selection.

Selecting Data Modules to Migrate

Once store authorization is complete, you can select the data modules you want to migrate. Dependencies exist between different modules — check the table below to confirm the migration order before selecting modules to migrate:

Recommended Module Migration Order

1. Product, Customer
2. Gift Card, Order & abandoned checkouts (order creation is irreversible — make sure the Product and Customer modules have fully migrated successfully first)

Strong Dependency Rules

Some modules have strong business data dependencies on one another:

1. Gift cards depend on customer data. If customer data hasn't been migrated, gift cards linked to those customers will fail to migrate.
2. Orders and abandoned checkouts depend on product and customer data. If product or customer data hasn't been migrated, order data will be abnormal and cannot be corrected.

When gift cards and orders are migrated in the same batch as the base modules they depend on, if the base module's migration success rate doesn't meet the threshold (below 95%), the system will not proceed to migrate gift cards, discount codes, or orders.

Example: Gift cards depend on customers — if the customer module's success rate doesn't meet the threshold, gift card migration will not run.

Gift cards and orders can be migrated separately when the following conditions are met:

1. The dependent module's most recent full migration was within the last 90 days. A full migration means no custom scope was set (migration scope is "All"); it excludes records where the migration task was interrupted or terminated.

The dependent module's most recent full migration success rate is 95% or higher. If it doesn't meet this threshold, you can use Retry on failed data to refresh the success rate.

Syncing Ad Data During Migration

If you're currently running Google or Meta ads, complete the following steps based on your chosen tool to ensure ad performance isn't interrupted after migration:

• Use the official SHOPLINE Smart Feed app (recommended): After completing your core store data migration, we recommend installing the Smart Feed app. It supports migrating your product feed from Shoplazza, and lets you complete all configuration within the app to ensure ID matching. For details, see "Smart Feed (New): Migrating Product Feeds from Shopify, WooCommerce, and Shoplazza (Limited Access)."
• Use the third-party Simprosys app: If you choose to use Simprosys to migrate Google or Meta ad data, you'll need to set feed rules in the migration plugin and complete the migration there. Be sure to clear any non-migrated products already in your SHOPLINE store before starting, to avoid feed matching failures.

Handling Migration Failures

After migration completes, some data may fail to migrate due to system errors or data that doesn't meet requirements. You can review and handle this failed data by module:

1. Once migration ends, review the details of failed migration data on the migration results page.
2. Failed data can be exported by module, with an export limit of 10,000 records per migration. If a single module's failed data exceeds this limit, we recommend analyzing and resolving some of the failures first, then clicking Retry before attempting to export again.

Secondary Migration: Migrating Incremental Data

If you've already completed a full migration but still need to migrate newly added data (for example, before switching your domain), you can initiate migration again — this is called a "secondary migration":

• Incremental data: Orders and abandoned checkouts support filtering by creation time, so you can specify a "start time" to precisely target your migration range.
• Already-migrated data: Already-migrated data is not overwritten by default, but you can choose whether to overwrite it:

For detailed steps on migrating abandoned checkouts, see "Migrating Abandoned Checkouts from Shoplazza to SHOPLINE."

Important Notes on Shoplazza Migration

• After Customer data is migrated from your Shoplazza store, customers need to activate their accounts by email, since the two systems are separate. You can send activation emails in bulk, and customize the email template under Settings > Notifications.
• If migrated customers only have a phone number and no email address, you'll need to enable phone number sign-up and login under Settings > Customers in the SHOPLINE admin — otherwise these customers won't be able to log in.
• Smart product categorization can't be migrated; product categories based on Google categories are also not supported. The migrated product count includes the number of products, SKUs, categories, and product-category associations, so the displayed migration count may not match the actual number of products.
• There's a delay in updating the customer count shown in the admin — it typically takes about 1.5 hours for the final count to appear.

Completing Migration and Binding Your Store Domain

After the data migration is complete, you can continue setting up your store, including configuring your storefront theme, setting up payments, configuring ad pixels (these must match your original channel IDs), verifying your site with meta tags, submitting your sitemap, and syncing your ad feeds.

Once your store is set up, you can connect your Shoplazza store's custom domain to SHOPLINE and officially launch.