CommerceHQ to BigCommerce Migration - Step-by-Step Guide & Expert Services

Seamlessly Transition Your E-commerce Store from CommerceHQ to BigCommerce

As your e-commerce business evolves, so do its needs. Migrating your online store to a more robust, scalable, and feature-rich platform like BigCommerce can be a strategic move to unlock new growth opportunities. While CommerceHQ offers a straightforward solution for getting started, BigCommerce provides advanced customization, powerful marketing tools, and extensive integration capabilities that can elevate your merchant experience and improve your customer journey.

This comprehensive guide will walk you through the entire process of moving your store data from CommerceHQ to BigCommerce, focusing on data integrity, minimizing downtime, and preserving your valuable SEO rankings. Given that CommerceHQ typically requires data export via CSV, we'll detail the steps for a smooth CSV-based transfer to BigCommerce's powerful API framework.

Prerequisites for a Successful Migration

Before initiating your store transfer, a few crucial preparations are necessary to ensure a seamless process and prevent any data loss or disruption.

• BigCommerce Store Setup: Ensure you have an active BigCommerce store. If not, set one up and familiarize yourself with its administration panel.
• Data Backup: Always perform a complete backup of your CommerceHQ store data. This is your safety net in case any unforeseen issues arise during the migration.
• CommerceHQ Data Export: Prepare to export your CommerceHQ data, such as products, categories, customers, and orders, into CSV (Comma Separated Values) files. This is the primary method for moving data from platforms like CommerceHQ to migration tools. For more details on this specific service, refer to our CSV.File Data Migration guide.
• BigCommerce API Credentials: BigCommerce uses an API (Application Programming Interface) for secure data transfer. You'll need to generate specific API credentials within your BigCommerce admin panel:
  • Client ID (Username)
  • Access Token (API Token)
  • API Path

  To do this, navigate to Settings > API Accounts in your BigCommerce dashboard. Create a new API account, making sure to grant the necessary OAuth scopes (permissions) for data access (e.g., read/write permissions for Products, Customers, Orders, etc.). Remember that HTTPS is required for BigCommerce API connections, and the platform has API rate limits, which reputable migration services manage automatically. Custom app development with required scopes is often involved in setting up the connection effectively.

• Review Your Data: Take stock of all the entities you wish to move, including products (SKUs, variants, images), customer records, order history, CMS pages, and blog posts. This helps in planning your migration scope.
• Prepare Your Target Store: For more detailed guidance, consult our How to prepare Target store for migration? and How to prepare Source store for migration? articles.

Performing the Migration: A Step-by-Step Guide

Follow these steps to successfully replatform your store from CommerceHQ to BigCommerce.

Step 1: Get Started

Begin your migration journey by accessing a reliable migration wizard. The initial screen will prompt you to choose your migration path.

Step 2: Configure Your Source Store (CommerceHQ via CSV)

Since CommerceHQ typically doesn't offer direct API integration for third-party migration tools, you'll transfer your data using CSV files. First, export all relevant data (products, customers, orders, etc.) from your CommerceHQ store. Then, within the migration wizard:

1. Select “CSV File to Cart” as your Source Cart.
2. Upload the exported CSV files containing your CommerceHQ data.

The system will then process these files to prepare your data for transfer.

Step 3: Set Up Your Target Store (BigCommerce)

Next, you'll connect your new BigCommerce store, which will serve as the destination for all your data.

1. Select “BigCommerce” as your Target Cart.
2. Enter your BigCommerce Store URL.
3. Provide the Client ID, Access Token, and API Path you generated earlier in your BigCommerce admin panel.

These credentials allow the migration tool to securely access and transfer data to your BigCommerce store. Remember BigCommerce's API rate limits, especially for large datasets; a professional migration service is designed to manage these. The connection requires HTTPS to ensure data security.

Step 4: Select Data Entities for Migration

This critical step allows you to choose exactly which types of data you want to move from your CommerceHQ CSV files to BigCommerce. You can select all entities or pick specific ones based on your needs.

• Products: This includes product details, SKUs, images, descriptions, variants, and product categories.
• Customers: Transfer customer accounts, shipping addresses, and associated data.
• Orders: Move order history, order statuses, and related customer information.
• Coupons: Migrate your existing discount codes and promotions.
• Blogs & CMS Pages: Carry over your blog posts and static content pages.

Make sure to review the list carefully to ensure all vital information is selected for transfer, maintaining data integrity.

Step 5: Configure Additional Options & Data Mapping

Refine your migration with a range of additional options and ensure proper data mapping.

Additional Migration Options

These options help tailor the data transfer to your specific requirements:

• Preserve IDs: Select options like “Preserve Product IDs,” “Preserve Category IDs,” “Preserve Customers IDs,” and “Preserve Orders IDs” to maintain original identifiers. This is highly recommended for preserving historical data and internal record-keeping. Learn more about How Preserve IDs options can be used?.
• SEO URLs & 301 Redirects: Choose to “Create 301 SEO URLs” to automatically redirect old CommerceHQ URLs to their new BigCommerce counterparts. This is crucial for preserving your search engine rankings and link equity.
• Clear Target Data: The “Clear Target” option allows you to remove existing data from your BigCommerce store before migration, ensuring a clean slate. Read about Clear current data on Target store before migration option.
• Create Variants from Attributes: If your CommerceHQ products use attributes (like size, color), this option can help BigCommerce correctly create product variants.
• Migrate Images in Description: Ensure product images embedded in descriptions are transferred.

Data Mapping Setup

This step ensures that disparate fields between CommerceHQ (via CSV) and BigCommerce are correctly aligned. You'll typically map:

• Customer Groups: Match customer roles (e.g., “Guest,” “Wholesale”) from your source to appropriate BigCommerce customer groups.
• Order Statuses: Align your CommerceHQ order statuses (e.g., “Pending,” “Shipped”) with their equivalents in BigCommerce.

Accurate data mapping is vital for maintaining consistent reporting and streamlined operations on your new platform.

Step 6: Review & Launch Full Migration

Before the final data transfer, you'll be presented with a summary of your selected entities, additional options, and the total cost. It's highly recommended to perform a free demo migration first to test the process and verify data integrity with a limited set of items.

You may also consider purchasing Migration Insurance Service, which allows for multiple re-migrations within a specific period, providing peace of mind. Learn more about How Migration Insurance works?.

Once satisfied, proceed with the full migration. The system will then handle the complex process of moving all your CommerceHQ data (from CSV) to your BigCommerce store.

Post-Migration Steps

After your data has been successfully transferred to BigCommerce, a few crucial steps remain to ensure your new store is fully operational and optimized.

• Thorough Data Verification: Systematically check all migrated entities in your BigCommerce admin. Verify product details (SKUs, pricing, images, descriptions, variants), customer accounts, order history, blog posts, and CMS pages. Ensure all links work correctly and images display as intended.
• Configure Store Settings: Set up essential configurations specific to BigCommerce, including:
  • Payment gateways
  • Shipping methods and zones
  • Tax settings
  • Store currency and localization
  • Email notifications
• Theme Customization: Personalize your BigCommerce store's design and user experience. Explore the BigCommerce Theme Store and customize your chosen theme to reflect your brand identity.
• SEO Optimization: If you opted for 301 redirects, verify their functionality. Update your sitemap in Google Search Console and monitor for any crawl errors. Re-evaluate your product and category metadata for optimal SEO performance, crucial for maintaining your SEO rankings and link equity.
• Install Apps/Plugins: Browse the BigCommerce App Marketplace for integrations to enhance functionality, such as marketing automation, analytics, customer service, or inventory management tools.
• Comprehensive Testing: Conduct thorough testing of your entire store. Perform test purchases, try different payment methods, check shipping calculations, and test all forms and interactive elements to ensure a smooth user experience. Test on various devices and browsers.
• Update DNS Records: Once you are completely satisfied with your new BigCommerce store, update your domain's DNS records to point to BigCommerce. This will officially make your new store live. Plan this carefully to minimize downtime.
• Notify Customers: Inform your customers about the transition and any new features or improvements they can expect.

Should you require any assistance with these post-migration tasks or encounter any challenges, don't hesitate to Contact Us for expert support.