Skip to main content

AspDotNetStorefront to BigCommerce Migration

In this project, we helped our client move from AspDotNetStorefront to BigCommerce, making sure all their data stayed accurate. The biggest challenge was handling complex order numbers, but we got it done smoothly with little need for fixes. Scroll for more details.

AspDotNet to BigCommerce

Data We Successfully Migrated

4,000+

Products

42,000+

Customers

69,000+

Orders

Other

Custom Data

About Our Client

​Our client is a U.S.-based company specializing in energy and water efficiency products, as well as weatherization supplies. Since 2008, they’ve been working with homeowners, contractors, and organizations like utility companies and government agencies to make buildings more efficient.

Our client switched to BigCommerce because AspDotNetStorefront required too much manual work and custom coding. BigCommerce has built-in features, better SEO, and easier product management, so they can focus on growing their business instead of dealing with technical issues.

Our Client’s Requirements

For this migration project, our client had several key requirements to ensure a smooth transition from AspDotNetStorefront to BigCommerce:

  • Provide a CSV file that maps old data to new records for easy tracking and reference before executing the migration;
  • Migrate basic data (products, orders and order comments, customers) and any data available in their AspDotNetStoreFront store;
  • Verify that all orders from specific dates match between the source site and BigCommerce;
  • Ensure item prices and order totals are accurately migrated;
  • Include the second address line in both shipping and billing addresses;
  • Retain all promotion codes used in previous orders;
  • Ensure all order tracking numbers are properly transferred.

The Challenges

One of the main challenges in this migration was handling the large and complex order numbers from AspDotNetStorefront. Due to the complexity, customizing the migration code and generating an accurate mapping file (old order numbers to new ones) required additional time and effort.

Our Solution

Even though the order mapping file was complicated and there were many requirements, we worked closely with the client to ensure everything was handled properly. By maintaining clear communication and careful execution, we completed the mapping file accurately, reducing the need for fixes and saving time.

After finalizing the mapping, we ran the All-in-One Migration Service to transfer the remaining data. Since we have done everything according to the mapping file previously, the client could review and approve everything immediately without major issues.

Project Timeline

Migration Preparation

  • Technical consultation: 4 days

Demo Migration

  • Run Demo Migration and wait for client’s confirmation: 2 days

Full Migration

  • Run the Full Migration and review: 2 days

Project Handling

  • Project reviewing based on client’s feedback: 3 days

What Customer Thinks About Us

“We had a complex migration project, and LitExtension handled it exceptionally well. Their expertise and efficiency saved us a lot of time and effort. Highly recommend their service!”

More Stories of Success

Magento to Shopify 1 9a2802d2

Magento to Shopify Migration

Shopware to BigCommerce b07d172c

Shopware to BigCommerce Migration

Magento 1 to Magento 2 027cdc24

Magento 1 to Magento 2 Migration

case 3 07 3c09e4aa

Salesforce to Shopify Plus Migration

Worried About Losing SEO Rankings During Migration? Get the Ultimate SEO Migration Guide from Experts!
Expert SEO Survival Guide for Smooth Migration!