E-commerce migration
Migrate to BigCommercefrom your current store platform
A BigCommerce move turns on how your options split into variants and modifiers, what the 600-SKU limit does to your largest products, and who creates the redirects the migration app won't.
Variants and modifiers are different things here
BigCommerce separates variant options, which create SKUs, from modifiers, which don't. A variant option such as size has stock and a SKU of its own. A modifier such as engraving text changes the order line but is not an inventory item. Getting this split right is the main modelling decision in the move, because source platforms often treat both as the same kind of attribute.
BigCommerce's Platform Limits page sets a maximum of 600 SKUs or variants per product. Its product documentation puts no limit on the number of modifiers. So a product with too many combinations has two ways through: split it into several products, or move the options that don't need their own stock to modifiers.
Catalogue size depends on the storefront. The same limits page lists 1,000,000 SKUs per storefront on Stencil and 2,000,000 product and variant SKUs on Catalyst, so the front-end choice is made with the catalogue count in hand.
Customers and passwords
Passwords can't be exported from the source store. BigCommerce's customer transfer guide says a password can be set through CSV import, and customers imported without one go through the password reset process. In practice that means planning a message to customers and a clear notice on the login page before launch, or support will take the questions instead.
Redirects depend on how the data moved
BigCommerce's data migration app creates 301 redirects for the products it moves. Everything else is your job: categories, content pages, brand pages, products imported by CSV or API, and any old URL patterns that outside links still use. The store must be on a paid plan to create redirects at all, so this can't wait for launch week.
We build the redirect list from the old sitemap, your analytics landing pages and Search Console's linked pages, then test every line after import. A redirect chain from an earlier replatform gets flattened at the same time, so each old URL goes straight to its final address.
Checks before you switch
- Counts of products, SKUs, customers and orders against the source, plus order totals by month.
- A manual sample of the awkward records: bundles, tax-exempt customers, products at the variant limit.
- Test orders through each payment and shipping method on the new store.
- A final delta of new orders and customers at cutover, with the old store still available until figures agree.
What we can show you
We have not published a BigCommerce migration. What we have published in commerce is a long-running WooCommerce engagement with Dynamics integration, and that experience applies to order and customer data flows. If a proven BigCommerce record matters most to you, weigh that when choosing. If it's a clear plan with checks you can audit, we can talk through yours.
BigCommerce migration questions
What happens to a product with more than 600 combinations?
It can't stay as one product with that many SKUs. We split it into several products or turn the options that don't need their own stock into modifiers, which don't count towards the limit.
Do customers need to reset their passwords?
Those imported without a password do. Passwords can't be exported from the old store, so we plan the customer message and the login page notice as part of the launch.
Which of your products would hit the limit?
Send a catalogue export and we will identify the products over 600 combinations and tell you how we would remodel them.
We reply within one business day (IST).