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

Seamlessly Migrate from AspDotNetStorefront to BigCommerce

Replatforming your e-commerce store is a strategic decision that can unlock new growth opportunities, enhance user experience, and streamline operations. If you're currently running on AspDotNetStorefront and considering a transition to a more scalable, feature-rich platform, BigCommerce stands out as an excellent choice. This comprehensive guide will walk you through every critical step of migrating your online store data, ensuring a smooth and efficient transfer of your valuable business assets.

Given that AspDotNetStorefront is typically a custom-built or older platform, the most reliable and efficient method for data extraction and migration will be through a structured CSV file export. This approach ensures maximum data integrity and compatibility with modern migration tools.

By the end of this article, you will have a clear, actionable roadmap to transfer your products, customer data, orders, and more from AspDotNetStorefront to BigCommerce, minimizing downtime and preserving your search engine optimization (SEO) rankings.

For any general questions, please refer to our Frequently Asked Questions section.

Prerequisites for Migration

Before embarking on your data transfer journey, it's essential to prepare both your AspDotNetStorefront (source) and BigCommerce (target) environments. Proper preparation is key to a successful and stress-free replatforming.

For Your AspDotNetStorefront Store (Source):

• Data Backup: Always perform a full backup of your AspDotNetStorefront database and files. This is a crucial safety net before any major data operation.
• Data Export to CSV: You will need to export your store's data into structured CSV (Comma Separated Values) files. This includes data for products, categories, customers, orders, and any other relevant entities. Ensure your CSV files are well-organized and correctly formatted for optimal import. For detailed guidance, consider our CSV.File Data Migration service.
• Review Data Integrity: Before exporting, conduct an audit of your existing data to identify and clean up any inconsistencies or outdated information. This is an ideal time to streamline your product catalog or customer records.

For more details on preparing your source store, read our guide on How to prepare Source store for migration?.

For Your BigCommerce Store (Target):

• Create a BigCommerce Account: If you haven't already, sign up for a BigCommerce account and set up your new store. This involves choosing a store name and setting up basic configurations.
• Store URL and Domain: Ensure your BigCommerce store URL is ready. BigCommerce requires HTTPS for all API connections, so make sure your store is secured.
• Generate API Credentials: BigCommerce uses API keys for secure data connections. You will need to create a custom API account to obtain the necessary credentials:
  • Client ID (Username): A unique identifier for your API application.
  • Access Token (API Token): The secret key that authenticates your API requests.
  • API Path: The specific endpoint for your store's API.
  To generate these, you'll typically navigate to 'Advanced Settings' -> 'API Accounts' in your BigCommerce admin panel and create a new Stencil-CLI / WebDAV API account. Ensure you grant the required scopes for all data entities you plan to migrate (e.g., Products, Customers, Orders). Remember that custom app development might be needed for specific advanced integrations or data types beyond standard migration.
• Initial Setup: Familiarize yourself with the BigCommerce admin panel. While not strictly necessary before migration, having a basic theme applied can help visualize migrated data.

For more information on target store preparation, visit How to prepare Target store for migration?. If you have concerns about providing access details, refer to Is it safe to provide your company with my access details? and for more on credentials, see The Short & Essential Guide to Access Credentials for Cart2Cart.

Performing the Migration: A Step-by-Step Guide

With your preparations complete, you're ready to initiate the data transfer. This section outlines the typical steps involved when using an automated migration service.

Step 1: Set Up Your Source Store (AspDotNetStorefront via CSV)

The first step is to configure your current AspDotNetStorefront store as the source. Since AspDotNetStorefront is not directly integrated with many migration tools, you'll select 'CSV File to Cart' as your source platform. You will then upload the carefully prepared CSV files containing your AspDotNetStorefront data.

The data types typically supported for migration from a CSV include Products, Product Categories, Manufacturers, Product Reviews, Customers, Orders, Invoices, Taxes, Stores, Coupons, CMS Pages, Blogs, and Blog Posts. Ensure your exported CSVs cover these entities to maintain comprehensive data integrity.

As noted, CSV migration is 'Source only' and solely relies on your uploaded files. For complex CSV structures or custom mapping needs, consider leveraging specialized migration services.

Step 2: Connect Your Target Store (BigCommerce)

Next, you will configure your BigCommerce store as the target. Select 'BigCommerce' from the list of supported platforms. You'll then be prompted to enter your BigCommerce store's URL and the API credentials you generated earlier: the Client ID, Access Token, and API Path.

Remember that BigCommerce enforces API rate limits, which are managed by the migration tool to ensure a smooth transfer without hitting bottlenecks. HTTPS is strictly required for this connection, and establishing a custom app with the necessary API scopes is essential for granting the migration tool proper access. For a refresher on API credentials, refer to The Short & Essential Guide to Access Credentials for Cart2Cart.

Step 3: Select Entities for Migration

Now, choose which specific data entities you wish to transfer from your AspDotNetStorefront CSV files to BigCommerce. The migration tool typically supports a wide range of entities, including:

• Products (including variants, images, descriptions, SKUs)
• Product Categories
• Manufacturers
• Customers
• Orders
• Coupons
• Blog Posts
• CMS Pages

You can opt to migrate all available entities or meticulously select specific ones based on your replatforming strategy. This step ensures that only the relevant information is moved to your new BigCommerce store, preserving data cleanliness.

Step 4: Configure Additional Migration Options

This crucial step allows you to fine-tune your migration with a variety of powerful options to protect your SEO, enhance data consistency, and customize the transfer process. Some key options include:

• Clear Target Store Data: The option to Clear current data on Target store before migration option ensures a clean slate on your BigCommerce store, preventing duplicate entries or conflicts.
• Preserve IDs: Options like How Preserve IDs options can be used? for categories, products, customers, and orders allow you to retain original database IDs, which can be vital for external integrations or historical data matching.
• 301 SEO URLs: Implementing 301 SEO URLs is critical for maintaining your search engine rankings by redirecting old AspDotNetStorefront URLs to their new BigCommerce counterparts, preserving valuable link equity.
• Password Migration: Depending on the security protocols and hashing methods used by AspDotNetStorefront, migrating customer passwords directly may be possible, or customers might be prompted to reset them post-migration for enhanced security.
• Create Variants from Attributes: This option helps structure your product data on BigCommerce by converting product attributes (e.g., size, color) into proper product variants.
• Migrate Images in Description: Ensures all product images embedded within descriptions are transferred.

Step 5: Map Data Fields

Data mapping is where you align specific fields from your AspDotNetStorefront CSV files to the corresponding fields in BigCommerce. This step is particularly important for:

• Customer Groups Mapping: Matching customer roles or groups from your source to appropriate segments or tags in BigCommerce.
• Order Status Mapping: Ensuring that order statuses (e.g., 'Processing', 'Shipped', 'Pending Payment') are correctly translated between platforms.
• Product Attributes: Mapping custom product attributes to BigCommerce's robust product option system.

The migration wizard will provide an intuitive interface to visually map these fields, ensuring data consistency and integrity post-migration.

Step 6: Run a Free Demo Migration (Optional but Recommended)

Before committing to a full transfer, executing a free demo migration is highly recommended. This allows you to transfer a limited number of entities (e.g., 10-20 products, customers, and orders) to your BigCommerce store. The demo serves as a powerful preview, enabling you to:

• Verify data accuracy and formatting on the target platform.
• Identify any potential issues or required adjustments in mapping.
• Familiarize yourself with the migration process without any commitment.

This crucial step helps to iron out kinks and builds confidence before the main event.

Step 7: Initiate Full Migration

Once you are satisfied with the demo results and have made any necessary adjustments, you are ready to launch the full data transfer. At this stage, you'll review the final migration scope and cost. You might also consider adding a Migration Insurance Service, which offers a certain number of re-migrations or support in case of unforeseen issues, providing an extra layer of peace of mind. For more details, explore How Migration Insurance works?.

With a final confirmation, the migration process will begin. Depending on the volume of your data, this can take anywhere from a few minutes to several hours. Automated tools are designed to work in the background, minimizing any disruption to your live AspDotNetStorefront store during the process.

Post-Migration Steps

Completing the full data transfer is a significant milestone, but the journey doesn't end there. Several vital post-migration steps are necessary to ensure your new BigCommerce store is fully operational, optimized, and ready for customers.

• Thorough Testing: Dedicate time to comprehensively test every aspect of your new BigCommerce store. This includes:
  • Browsing product pages and verifying images, descriptions, and pricing.
  • Testing the checkout process with various payment methods.
  • Logging in as migrated customers to check their account history and details.
  • Confirming that all links and navigation elements are functional.
  • Checking contact forms and other interactive elements.
• Update DNS Records: Once you've thoroughly tested and are confident in your BigCommerce store, update your Domain Name System (DNS) records to point your domain to the new BigCommerce platform. This makes your BigCommerce store live to the public.
• Implement 301 Redirects: Even if you used an option to create 301 SEO URLs during migration, review and manually add any critical redirects for pages that might have changed their URL structure unexpectedly. This is paramount for maintaining your search engine rankings and preventing 404 errors.
• SEO Audit and Optimization: After your BigCommerce store is live, conduct a post-migration SEO audit. Check your Google Search Console for any crawl errors, verify sitemaps, and monitor your keyword rankings. Leverage BigCommerce's built-in SEO features to further optimize your product pages, categories, and blog content.
• Configure Integrations: Reconnect and configure any third-party apps or services you used on AspDotNetStorefront, such as payment gateways, shipping providers, CRM systems, email marketing platforms, and analytics tools, within your BigCommerce ecosystem.
• Remove Old Store: Once you are completely satisfied with your new BigCommerce store's performance and stability, and after confirming that all data and SEO considerations are handled, you can safely decommission your old AspDotNetStorefront installation.
• Continuous Monitoring: Keep a close eye on your BigCommerce store's performance, customer feedback, and sales data in the weeks following the migration. This allows you to quickly address any minor issues and further optimize the user experience.

Should you need to transfer new data added to your old store after the initial migration, our Recent Data Migration Service can help. If any issues arise that require a full reset, a Cart2Cart Remigration Service can be performed. For any specialized needs or further assistance, do not hesitate to Contact Us.