How can we help you?

If Cart2Cart cannot validate your BigCommerce admin email and password, skip automatic credential creation and connect with a store-level API account instead.

Common causes

1. Incorrect admin email or password.

2. Staff account disabled or missing store-owner / API permissions.

3. Temporary BigCommerce control-panel or API outage.

4. Account settings that block automatic API account creation from third-party tools.

Fix: provide API Path and Access Token manually

1. In BigCommerce, create a Store-level API account (V2/V3 API token) with modify scopes for products, customers, orders, and related resources.

2. Copy the API path, Client ID, and Access token.

3. Enter those values in the Cart2Cart Migration Wizard instead of relying on admin password validation.

Step-by-step: Where can I get BigCommerce API Path and API Token?

If validation still fails after a correct API account, contact Cart2Cart support with your store URL and the exact wizard error text.

Start your free demo.

BigCommerce API Call Limits and Data Migration

During your data migration to BigCommerce, you might encounter API call limits. These limits are imposed by BigCommerce to ensure platform stability and performance. Here's what you need to know:

• BigCommerce Standard and Plus plans have a limit of 20,000 API calls per hour.
• BigCommerce Pro plans have a limit of 60,000 API calls per hour.
• BigCommerce Enterprise plans offer unlimited API calls.

If your data migration exceeds these limits, don't worry! Your migration is still in progress. All your product variants and other data will be transferred accurately and securely, but the process may take a bit longer. These limits are set by BigCommerce, and Cart2Cart cannot bypass them. Please be patient, and the replatforming process will be completed as soon as possible.

What can you do to expedite your BigCommerce data migration?

1. Pre-Migration Audit: Before starting your migration, conduct a thorough audit of your existing store. Remove any unnecessary or outdated products, categories, or customer data. This reduces the amount of data that needs to be migrated, potentially lowering the number of API calls required.
2. Migration Scheduling: Consider scheduling your data migration during off-peak hours. This might help avoid potential slowdowns caused by high traffic on the BigCommerce platform.
3. Upgrade Your BigCommerce Plan: If you anticipate needing more API calls, consider upgrading to a BigCommerce Pro or Enterprise plan. These plans offer higher API call limits or even unlimited access, which can significantly speed up the data migration process.

For more information on BigCommerce API limits, please refer to the BigCommerce FAQ.

Next Steps:

• Start your free demo: https://newapp.shopping-cart-migration.com/
• Contact Cart2Cart support via Live Chat.
• Schedule a call with a Migration Expert: https://meet.shopping-cart-migration.com/team/csm

You may need a BigCommerce product ID when troubleshooting a Cart2Cart migration.

From the control panel (preferred)

1. Log in to BigCommerce.

2. Go to Products → View (or All Products).

3. Open the product. The browser URL typically contains the numeric ID (for example .../products/123/... or an id= parameter).

From a product image URL

1. On the storefront product page, open the main image in a new tab.

2. In the image URL, find the /products/ segment; the number that follows is often the product ID.

API credentials for migration: Where can I get BigCommerce API Path and API Token?

Start your free demo.

Why Were My 301 Redirects Not Migrated?

301 redirects are essential for maintaining SEO rankings and ensuring a smooth user experience during and after a store migration. If your 301 redirects weren't migrated, there are a few potential reasons why.

First, ensure that your source platform supports 301 redirect migration and that you've selected the option to migrate them during your data migration setup with Cart2Cart. Not all platforms store redirects in the same way, and some may require specific permissions or configurations to access this data.

Another common reason is related to the target platform's capabilities or limitations. For example:

In BigCommerce, 301 redirects are available only within a paid store plan. Therefore, to migrate 301 redirects to or from BigCommerce, upgrading to a paid plan is necessary. This ensures the platform supports the functionality required for the migration. Cart2Cart can migrate your 301 redirects seamlessly once you have a paid BigCommerce plan. This is a critical step in preserving your SEO and customer experience during your BigCommerce migration.

Here are a few other things to consider:

• Check your Cart2Cart migration settings: Double-check that you selected the "Migrate 301 redirects" option during the migration setup.
• Verify platform compatibility: Ensure both your source and target platforms fully support 301 redirect functionality.
• Review your data: Confirm that the 301 redirects are correctly configured in your source store.

If you've checked these points and are still experiencing issues, please contact our support team via Live Chat for assistance. We're here to help ensure a smooth and complete data migration.

Next Steps:

• Start your free demo: https://newapp.shopping-cart-migration.com/
• Contact support via Live Chat on the Cart2Cart website.
• Schedule a Call with a Migration Expert: https://meet.shopping-cart-migration.com/team/csm

Looking for a seamless data migration to BigCommerce? If you wish to replatform to BigCommerce using the "Migration for BigCommerce" app, the following instructions will guide you through the process. Start your free demo now and experience effortless data transfer!

Note: Some screenshots in this guide may show an older Cart2Cart wizard UI; the migration steps and data entities remain the same.

Set Up Source and Target Carts for BigCommerce Data Migration

Begin by selecting your current platform from the list of supported carts on the Cart2Cart website. Provide the necessary store credentials: either your store's URL (for open-source carts) or API details (for hosted solutions). Next, click the "Install Plugin" button to add the "Migration for BigCommerce" app, enabling the connection with your BigCommerce store. Once installed, click the Choose Entities button to proceed.

Note: These access details are essential for establishing an automated connection between your stores. Rest assured, the information you provide is securely protected in accordance with the Cart2Cart Privacy Policy.

Choose Data for Your BigCommerce Migration

Specify the store entities you want to import to BigCommerce. Select the corresponding checkboxes or activate the Select All option to migrate all your store data. Additionally, explore the additional migration options to enhance your BigCommerce data migration.

Map Data Fields During BigCommerce Migration

Match your current shopping cart's Order Statuses and Customer Groups to the corresponding ones in your BigCommerce store. This data mapping ensures accurate data transfer according to the relationships you define.

Launch a Demo Migration to BigCommerce

Take advantage of the demo migration feature to transfer a limited number of store entities from your current store to BigCommerce. This process takes approximately 15-30 minutes and allows you to observe the Cart2Cart service in action and preview your BigCommerce store with migrated data.

Start the Full Data Migration to BigCommerce

Once you're satisfied with the demo, activate the Start Full Migration button to initiate the complete data migration from your current store to BigCommerce in a fully automated manner. Begin your full migration today!

BigCommerce Category Structure Issues After Migration: Why Did It Happen?

It's possible that your original store had a category structure exceeding BigCommerce's limitations. BigCommerce has a category depth limit of 8 levels. Therefore, if your source store contained categories nested deeper than 8 levels, Cart2Cart will automatically adjust these categories, placing any categories beyond the 8th level as root categories during the data migration process to ensure data integrity and compatibility with the BigCommerce platform.

To avoid this situation, carefully review your category structure before migration and restructure any categories exceeding the 8-level limit. Alternatively, consider adjusting your category structure after the migration within your BigCommerce admin panel.

Need help planning your data migration? Schedule a call with a Migration Expert to discuss your specific needs.

BigCommerce users are staff accounts that access the control panel (not storefront customers). Invite a teammate with administrator rights before or after a Cart2Cart migration to BigCommerce. Control-panel users are not migrated by Cart2Cart for security reasons—recreate them on the target store.

1. Log in as the store owner (or a user with Add/Manage Users permission).

2. Go to Account Settings → Users (path may appear as Settings → Users depending on control-panel layout).

3. Click Create a User Account.

4. Enter the invitee’s email, set status to active, and choose language if prompted.

5. Select role Store Administrator (or Custom and enable the admin permissions you need). Only the store owner can grant certain high-risk permissions.

6. Save. The user receives an email to set a password and sign in.

Official: BigCommerce — Users · User roles and permissions.

Start your free demo.

To connect BigCommerce in the Cart2Cart Migration Wizard, create a store-level API account and copy the API path, Client ID, and Access token.

1. Log in to your BigCommerce control panel.

2. Go to Settings → Store-level API accounts.

3. Click + Create API Account.

4. Choose token type V2/V3 API token.

5. Enter a name (for example Cart2Cart Migration).

6. Note the API path shown on the form (you will need it in the wizard).

7. Under OAuth scopes, set modify (or the highest write access available) for the resources Cart2Cart needs—typically products, customers, orders, and related entities. For a full migration, grant modify where listed.

8. Click Save.

9. In the confirmation dialog, copy the Client ID and Access token immediately (and keep the downloaded .txt file). BigCommerce will not show the token again.

10. Paste the API path, Client ID, and Access token into the corresponding Cart2Cart Migration Wizard fields.

Official reference: BigCommerce — Store API Accounts.

If admin login validation fails instead of API fields, see BigCommerce Admin Access Validation Error.

Start your free demo.

Troubleshooting: "The cart type is invalid or you entered invalid auth data" Error During Data Migration

Encountering the error message "The cart type is invalid or you entered invalid auth data" during your data migration process with Cart2Cart? This usually indicates a problem with the connection details you've provided for either your source or target store. Here's a comprehensive guide to troubleshoot and resolve this issue:

1. Verify Your Shopping Cart Type and Store URL

Double-check that you have selected the correct shopping cart platform from the dropdown menu. An incorrect selection here will prevent Cart2Cart from establishing a connection. Also, ensure that the store URL you entered is accurate and accessible.

2. Validate Your API Credentials

The most common cause of this error is incorrect API credentials. Each e-commerce platform uses a different method for authentication, such as API keys, usernames, passwords, or specific API paths. Carefully review the API documentation for your specific platform (e.g., BigCommerce, Shopify, Magento, and other platforms) and confirm you've entered all the required information correctly.

For example, if you are migrating to or from BigCommerce, you'll need to verify your Account, API Path, and API Token. Consult our detailed guide on how to obtain your BigCommerce API Path and API Token.

3. Check Permissions and Access Rights

Ensure that the user account associated with the API credentials has the necessary permissions to access and retrieve data from your store. Insufficient permissions can lead to authentication failures.

4. Firewall and Security Settings

Your store's firewall or security settings might be blocking Cart2Cart's access. Whitelisting Cart2Cart's IP addresses in your firewall settings might be necessary. Contact your hosting provider or system administrator for assistance with this.

5. Platform-Specific Requirements

Some platforms require specific modules or extensions to be installed and enabled for data migration to work correctly. Refer to Cart2Cart's documentation or the platform's documentation for any platform-specific requirements.

6. Contact Support

If you've checked all of the above and are still encountering the error, don't hesitate to contact Cart2Cart's support team via Live Chat. Provide them with details about your source and target carts, the steps you've taken, and any relevant error messages. They can assist you in diagnosing and resolving the issue.

Cart2Cart simplifies the data migration process, but ensuring correct credentials and configurations is crucial for a successful transfer.

Ready to start your seamless shopping cart data migration? Start your free demo now!

A 301 redirect is a permanent redirect, a crucial aspect of eCommerce data migration, that permanently forwards one URL to another.

Can I Migrate 301 Redirects to BigCommerce?

Yes, Cart2Cart offers the ability to migrate 301 redirects to BigCommerce. However, this is only possible if your Source Cart supports the migration of categories and products SEO URLs. Supported Source Carts include:

• Magento
• OpenCart
• CS-Cart
• PrestaShop
• VirtueMart
• WooCommerce
• osCommerce

Furthermore, the migration of 301 redirects to BigCommerce is only available if you select the option to migrate categories and products SEO URLs during your eCommerce data migration setup.

Note: If you choose the "Clear current data on Target Store before Migration" option, all existing 301 redirects on your BigCommerce store will be cleared.

Ready to migrate your store to BigCommerce and preserve your SEO? Start your free demo now or schedule a call with a migration expert to discuss your specific needs.

Will my SKUs be migrated during BigCommerce data migration?

Yes, Cart2Cart provides the capability to migrate SKUs (Stock Keeping Units) to your BigCommerce store during the data migration process. This ensures that your product identification and inventory management remain consistent after the transfer.

SKU Handling for BigCommerce Data Migration with Cart2Cart

While Cart2Cart migrates SKUs to BigCommerce, it's important to be aware of how duplicate SKUs are handled. If the same SKU exists in both your source store and your BigCommerce target store, BigCommerce will not allow duplicate SKUs. To resolve this conflict, Cart2Cart automatically modifies the SKUs during migration to ensure uniqueness.

For example, if you have a product with SKU "#153" in both your source and target stores, the migrated SKU in BigCommerce will be adjusted to something like "#153-1" to avoid conflicts. This ensures all your products are migrated without data loss, although you might need to review and adjust these modified SKUs in BigCommerce after the migration is complete.

This approach ensures a seamless BigCommerce data migration without losing any of your valuable product data.

Ready to migrate your store to BigCommerce? Start your free demo now to see how Cart2Cart can simplify your migration process.

Need personalized assistance? Schedule a call with our migration expert to discuss your specific requirements.

Yes, you will be able to migrate product SKUs along with their prices from Bigcommerce. All you have to do is to select additional option “Migrate product SKUs”.

Please note: If you do not choose additional option “Migrate product SKUs”, only product options will be migrated to the Target store.