How to Migrate from Other Platforms to SureCart

This document outlines the recommended sequence of steps to migrate an existing eCommerce store from another platform to SureCart. Each step links to a detailed guide for that specific stage of the migration.

Important Note

Migrating an eCommerce platform is a technical process and may require developer expertise, especially when dealing with custom setups or non-standard configurations. The following points apply to all migrations:

Effort and expertise required. Migration involves transferring data accurately while keeping the store operational. Consulting a qualified developer is recommended for store owners who are not familiar with technical processes such as CSV preparation, database migration, or payment processor data transfer.
Scope of support. SureCart support can assist with questions about documentation and product functionality. Hands-on migration work, including data preparation and platform-specific exports, is the responsibility of the store owner or their developer.
Realistic expectations. Migration requires careful planning and execution. Time and complexity vary depending on the size of the store, the source platform, and the data being transferred.

For questions during the migration process, contact SureCart support.

Migration Overview

The migration process is divided into the following steps. Following them in order is recommended, since some steps depend on data created in earlier ones (for example, purchases cannot be imported before products and customers).

Set up the store
Configure branding and notifications
Connect payment processors
Import customers
Import products
Import purchases
Import active subscriptions
Synchronize WordPress users with SureCart

The following diagram shows the recommended order and the dependencies between data imports:

Figure 1. Migration flow showing the recommended order of steps and dependencies between data imports.

Step 1: Set Up the Store

Before any data is imported, the SureCart store must be installed and configured with the essential settings, such as store name, store logo, and selling currency. These values affect how the store appears to customers and how transactions are processed.

Required actions:

Install and activate SureCart. Refer to How to Install SureCart.
Configure store details (name, currency, address, and others). Refer to How to Update Store Details.

Step 2: Configure Branding and Notifications

Branding settings determine how the store name, logo, and colors are displayed across customer-facing areas, including invoices, email notifications, and the customer dashboard. Notification settings determine which emails are sent to customers and store administrators.

Required actions:

Configure brand colors and logo. Refer to How to Set Up Branding in SureCart.
Configure customer email notifications. Refer to How to Manage Customer Email Notifications.

Step 3: Connect Payment Processors

A payment processor must be connected before live transactions can be processed. SureCart supports the following payment processors:

Note: SureCart supports both Test Mode and Live Mode. Test Mode can be used to validate the checkout flow with simulated transactions before processing real payments.

Step 4: Import Customers

Customer data is imported via a CSV file containing fields such as first name, last name, and email address. Importing customers before products and purchases ensures that subsequent imports can be linked to existing customer records.

For the CSV format and step-by-step import process, refer to How to Import Customers in Bulk.

Note: When migrating active subscriptions that include saved payment methods from Stripe, the payment method data can be transferred so customers are not required to re-enter their card details. Refer to How to Export Stripe Data for the export process.

Step 5: Import Products

Product data is imported via a CSV file containing fields such as product name, price, type, and description. Products must be imported before purchases and subscriptions, since each purchase or subscription references a product record.

For the CSV format and step-by-step import process, refer to How to Import Products in Bulk.

Step 6: Import Purchases

Historical purchase data is imported via a CSV file containing fields such as customer email, product identifier, and purchase date. Importing past purchases is particularly relevant for stores that sell licenses, since license records depend on accurate purchase history.

For the CSV format and step-by-step import process, refer to How to Import Purchases in Bulk.

Step 7: Import Active Subscriptions

Active subscriptions are imported via a CSV file containing the subscription identifiers, customer references, product references, and billing details. Importing subscriptions ensures that recurring billing continues without interruption after the migration.

For the CSV format and step-by-step import process, refer to How to Import Subscriptions in Bulk.

Step 8: Synchronize WordPress Users with SureCart

After customer data is imported, SureCart users must be synchronized with WordPress users. This step is required when SureCart is integrated with third-party plugins (such as LearnDash or BuddyBoss) that rely on WordPress user accounts to grant access to content.

Required action:

Run the user sync from the SureCart settings. Refer to How to Sync WordPress Users with SureCart for the exact path and procedure.

Notes and Limitations

The migration order matters. Customers must be imported before purchases and subscriptions, and products must exist before purchases or subscriptions can reference them.
CSV files must follow the format specified in each bulk import guide. Imports may fail or import incomplete records if the format is not respected.
Saved payment method transfer is supported only when migrating from Stripe. Other source platforms may require customers to re-enter payment details.
Testing the migration in a staging environment before applying it to a live store is recommended. This helps identify CSV formatting issues and missing data without affecting customer-facing operations.

FAQ

Can the migration be performed without a developer?

It depends on the source platform, the volume of data, and the complexity of the store. Stores with simple catalogs and few customers can often be migrated by following the bulk import guides. Stores with custom integrations, large customer bases, or non-standard data structures typically require developer assistance to prepare CSV files and validate the imported data.

Is downtime required during migration?

No mandatory downtime is enforced by SureCart, but performing the final migration during a low-traffic period is recommended. Imports performed while the source platform is still receiving orders may result in missing records or duplicated data.

Can the migration be tested before applying it to a live store?

Yes. Performing the migration in a staging environment is recommended. CSV files can be tested in staging to identify formatting issues before the live import.

What happens if a CSV import fails partway through?

Records that were imported before the failure remain in the store. The import can be re-run after correcting the CSV file. Refer to the specific bulk import documentation for handling duplicate records on re-import.

Are saved payment methods preserved during the migration?

Saved payment methods can be transferred when migrating from Stripe by exporting the relevant data and including it in the customer import. For other source platforms, customers may need to re-enter payment details before their next recurring charge.

What should be done if active subscriptions stop renewing after the migration?

Verify that the subscriptions were imported with valid customer references, valid product references, and valid payment method data. If the payment method was not transferred, the customer must update payment details from the Customer Dashboard before the next billing cycle.

Do imported orders generate email notifications to customers?

No. Bulk imports do not trigger transactional emails. Customers do not receive duplicate order confirmations or receipts for previously completed transactions from the source platform.

Was this doc helpful?

What went wrong?

Instructions/steps are incorrect.

Information/steps are missing.

Graphics are outdated or unavailable.

The explanation is incomplete.

I need help with something else.

We don't respond to the article feedback, we use it to improve our support content.

Need help? Contact Support

Table of Contents

Docs

Getting Started

Migrating

Products

Checkout

Instant Checkout

Orders

Subscriptions

Revenue Boosters

Customer Dashboard

Online Store

Settings

Tax

Email

Affiliate Platform (for merchants)

Licensing

Payments

Integrations

Bricks Builder

Elementor

Localization

Developer Docs

Troubleshooting

Affiliates & Agencies (our partners)