WooCommerce hosting for shops moving off BigCommerce.
BigCommerce models a catalogue with option sets, modifiers and rules. WooCommerce models it with variations. Mapping between the two is the migration.
Where BigCommerce and WooCommerce disagree.
Products, orders and customers exist in both. How a purchasable item is described is where they part company.
Option sets and modifiers
BigCommerce separates options that create variants from modifiers that only change price. WooCommerce has variations and little else, so each one needs deciding rather than importing.
URLs built by its own rules
Product and category addresses follow BigCommerce conventions that WooCommerce will not reproduce, so ranking pages need redirects generated from the old structure.
Passwords that cannot travel
Customer accounts and order history come across; the passwords do not. Every customer goes through a reset, which is worth telling them before launch rather than after.
A store built on an API
The catalogue is extracted through their API rather than a database dump, so rate limits and pagination shape how long the export takes.
Checkout and payments rebuilt
BigCommerce hosts the checkout itself. That entire step is rebuilt in WooCommerce, with the payment gateway reconnected rather than carried.
Map the catalogue before you move it.
An unmapped import produces a shop with the right product count and the wrong purchasable options against a good share of them.
- Option sets and modifiers mapped to variations
- Redirects generated for product and category URLs
- Password reset flow prepared and announced
- Payment gateway reconnected and test-ordered
A catalogue that stays quick as it grows.
BigCommerce shops arriving here are usually large. Variations multiply the product tables, which is exactly where an untuned WooCommerce install slows down.
What this move needs that a host migration does not
Each row is a place the two platforms describe the same shop in incompatible terms.
| Setting | What we do | Why |
|---|---|---|
| Product options | Option sets and modifiers mapped onto WooCommerce variations | BigCommerce distinguishes options that create a variant from modifiers that only adjust price, and WooCommerce has no equivalent to the second — so each one is a decision, not an import. |
| URL structure | Redirects generated from the old product and category addresses | Their URLs are built by platform conventions WooCommerce will not reproduce, so every page carrying ranking needs an explicit redirect rather than a matching permalink. |
| Customer passwords | Accounts and order history migrated, with a reset for every customer | The platforms hash credentials incompatibly and BigCommerce never exposes the hashes, so there is no route that lets a customer keep the password they had. |
| Extraction method | Catalogue pulled through the BigCommerce API, paced to its rate limits | There is no database to dump on a hosted platform, so the export is an API crawl whose duration is set by their limits rather than by the size of the catalogue alone. |
| Checkout | Rebuilt in WooCommerce with the payment gateway reconnected | BigCommerce hosts the checkout itself, so nothing about that step exists in an export and the whole flow is recreated before any real order can be taken. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Do my BigCommerce options become WooCommerce variations?
Can I keep my product URLs?
Do my customers have to set a new password?
How long does exporting a large catalogue take?
What happens to my checkout?
Own the storefront and the checkout.
Free migration, options mapped deliberately, and a redirect for every product that ranks.