WooCommerce is a capable, open-source way to start an online store on WordPress. Many growing brands eventually look at a hosted platform such as BigCommerce when the maintenance load, plugin stack or checkout setup starts to hold the business back. A WooCommerce to BigCommerce migration can protect your catalog, customers and search visibility, but only if you treat it as a planned cutover, not a file copy.
This guide covers why stores switch (and when they should not), what actually moves, how to handle customer passwords, how BigCommerce URLs differ from WooCommerce, and the order of work that keeps sales and rankings intact. It is based on official BigCommerce, WooCommerce and Google documentation, checked in November 2026. If you want a team to run the migration with you, get a proposal.
Why stores switch from WooCommerce to BigCommerce
The reasons we hear most are operational. BigCommerce describes replatforming as a response to growth limits: performance or scaling issues, a rising total cost of ownership from apps and maintenance, missing B2B or multi-storefront capabilities, or friction with integrations.
Less platform maintenance
WordPress core, WooCommerce, the theme and every plugin have their own update cycles, and a failed update can take the store down. On a hosted platform, hosting, patches and checkout security are part of the service.
Performance and peak traffic
A self-hosted store is only as fast as its hosting, cache and plugin stack. Image-heavy catalogs and sale-day traffic are a common breaking point.
Checkout and payments
WooCommerce checkout is flexible, but that usually means more plugins and more PCI scope on your own hosting. BigCommerce provides a hosted checkout; payment gateways still have to be enabled on the new store.
B2B, multi-storefront and integrations
Brands that need native B2B features, more than one storefront, or fewer one-off plugins often evaluate BigCommerce. The real test is whether it covers the jobs your current plugins are doing.
When you should not migrate yet
Stay on WooCommerce, or delay the move, when the store is stable and the platform is not blocking growth; when you depend on custom plugins or a tightly coupled ERP, PIM or subscription setup with no tested BigCommerce equivalent; or when you are in a peak selling window. Build on a staging storefront first, and cut over in a quiet period. BigCommerce notes that the existing store can stay live during data transfer, with downtime limited to a planned switch.
If the site is a content-heavy WordPress publication with a store attached, consider BigCommerce for WordPress, which keeps WordPress for design and content and uses BigCommerce for catalog, checkout and orders, instead of leaving WordPress altogether.
If you are still choosing a destination platform, our guides to Shopify vs. BigCommerce and Shopify vs WooCommerce compare the trade-offs. This article assumes you have already decided on BigCommerce.
Pre-migration audit
Do this work before you import anything. A clean source store is faster and safer to move than a cluttered one.
Catalog and content
Export products with WooCommerce's built-in Product CSV Importer and Exporter, including custom meta if you use it. Count SKUs, variants, images, categories and discontinued items, and drop what should not move. BigCommerce's prepare-your-data guidance is to review the export, filter unwanted records, and map fields to its product schema before you import.
Customers, orders and reviews
Export customers and a full order history for tax and reference, even if you also use a migration app. WooCommerce's core product export does not include orders; use an order export extension or a migration tool. Count reviews and note whether they live in native comments, a plugin or a third-party service.
URL and SEO inventory
Crawl the live site and export every indexable URL: products, categories, tags, the shop archive, pages, blog posts, landing pages and paginated archives. Capture titles, meta descriptions, canonicals, hreflang if you use it, and a Search Console baseline. This list becomes the redirect map.
Apps, theme and operations
List every plugin that touches checkout, tax, shipping, subscriptions, wholesale pricing, inventory, email, search, reviews or analytics, and name the BigCommerce app, native setting or custom work that will replace it. Themes, payment gateways, tax and shipping do not arrive with a catalog import.
Back up the WordPress site (files and database) and store the exports somewhere durable. Keep the WooCommerce store running until the BigCommerce storefront has passed a full test pass.
What moves, and what does not
BigCommerce documents several paths: its Data Migration app, CSV import, the APIs, expert-led Data Migration Services, and marketplace apps. The Help Center article Transferring Your Data to BigCommerce is the most specific public breakdown. Marketing pages sometimes describe a broader set of data; treat the Help Center table as the working checklist and confirm the current scope of your chosen tool before you start.
| Data | Data Migration app | CSV import | Other path |
|---|---|---|---|
| Products, variants, SKUs, images, categories | Yes, within the current record limit | Yes, after field mapping | API or a managed migration |
| Customers | Yes, without passwords | Yes, without exported passwords | API; customers set a new password |
| Historical orders | Yes, within the current record limit | No | API or Data Migration Services. Keep a WooCommerce export for tax and reference. |
| Product reviews | Listed as supported; verify after import | No | API, or a marketplace review importer |
| Blog posts and web pages | Not included, per the Help Center | No | API, or copy into BigCommerce and 301 the old URLs |
| Customer passwords | No | No | Cannot be migrated for PCI compliance; plan a reset |
| 301 redirects | Confirm in your chosen tool | Yes, via Settings → 301 Redirects | API, or add redirects manually |
| Payment gateways, tax, shipping, apps, theme | No | No | Re-enable or rebuild on the new store |
The Data Migration app is documented for up to 500,000 total records across products, customers and orders, and it can import from WooCommerce. Check the current record limit and pricing on BigCommerce's site before you rely on it. Required product fields in the documented schema are name, type (physical or digital), weight (zero for digital products) and price.
Customer passwords
Plan this before launch. BigCommerce's Help Center is explicit: customer passwords cannot be migrated for PCI compliance. Shoppers need to set a new password, usually through "Forgot your password?". BigCommerce also documents a "Force password reset on next login" control in Customer Account Management, plus an API option to force a reset. Tell customers ahead of time, and test the reset email so the first live login is not a surprise.
Migration methods
Most projects use more than one method: an app or service for the heavy datasets, CSV or the control panel for cleanup, and the API for anything the app cannot represent cleanly.
BigCommerce Data Migration app
The official self-serve path from WooCommerce. BigCommerce describes a guided workflow, post-import error reporting and a ceiling of 500,000 records. Audit variants, images, categories, customers and sample orders after the import.
CSV import
A good fit for products and customers once the columns match BigCommerce's templates, and for bulk 301 redirects. It is not a path for orders. Encode CSVs as UTF-8, as BigCommerce warns that some characters can break an import.
API
The Catalog, Customers and Orders APIs can move data that CSV cannot, including orders, and can set a product custom_url so you keep an existing path. Use this for large or heavily customized catalogs, and respect the published rate limits.
Partners and third-party tools
BigCommerce also offers expert-led Data Migration Services and certified partners. Third-party cart migration services, including tools in the same category as Cart2Cart, LitExtension and marketplace apps such as MigrationPro, can help when you need orders, reviews or content moved in one project. Compare what each tool actually transfers, and check current pricing, before you choose.
If you want to keep WordPress for content and only move commerce off WooCommerce, BigCommerce for WordPress is the official alternative to a full storefront migration. It has its own requirements, including a "Post name" permalink setting and no Multi-Storefront on that BigCommerce store, so evaluate it as a separate architecture rather than a shortcut through this checklist.
Step-by-step migration checklist
Use this as the working order. Products, customers, orders, URLs and 301 redirects, and SEO each have a distinct job; skipping one of them is how launches go wrong.
Clean, map, then import
Map attributes and variations to BigCommerce options, modifiers and variants, and set type, weight and price for every product. Import into a staging or unpublished store, then spot-check images, variant SKUs, inventory, categories and digital versus physical settings.
Move records, plan the reset
Import names, emails, addresses, groups and any marketing-consent fields you are allowed to keep, and watch for duplicates. Schedule the email that explains how to set a new password, and test the reset link. Do not promise that existing WooCommerce passwords will work.
Use a path that supports orders
CSV import will not bring historical orders into BigCommerce. Use the Data Migration app, the API or a managed service, and import products and customers first so line items and customer links resolve. Keep the WooCommerce order export for tax and disputes.
Map every important path
Build a one-to-one map from each live WooCommerce URL to its BigCommerce equivalent. Import it in Settings → 301 Redirects after the catalog and pages exist, then test products, categories, pages, blog posts and the /shop/ archive.
Carry the signals, then prove it
Copy titles, meta descriptions and image alt text into BigCommerce's SEO fields. Set URL structure deliberately, confirm canonicals point at the new URLs, and submit xmlsitemap.php in Search Console after cutover. Google recommends keeping redirects in place for at least a year.
Rebuild, test, then switch
Install the theme or custom storefront, reconnect payments, tax, shipping, email and analytics, and run the testing checklist below. Only then point the domain at BigCommerce and watch Search Console, 404s and checkout.
SEO preservation
Search is where a sloppy migration does lasting damage. Google's site moves and migrations guidance is the standard: use server-side 301 or 308 redirects, avoid long chains, do not send lots of old URLs to an irrelevant homepage, and update canonicals. BigCommerce says a temporary dip is normal while Google recrawls, and that rankings can be preserved when you map URLs, set 301s and migrate titles, descriptions and SEO URLs.
How the URLs change
WooCommerce permalinks are highly configurable. Once pretty permalinks are on, the defaults are typically /product/product-name/ and /product-category/category-name/, plus a /shop/ archive, but many stores change or drop the product base. Never assume the default; use the crawl from your audit.
BigCommerce's default, documented in SEO Fields, is "SEO Optimized (Short)": yourdomain.com/product-name. Other presets are Long (/products/product-name) and Category (/category/product-name), plus a Custom format. BigCommerce recommends leaving the short format in place unless you have a reason to change it. If you change structure later, tick the option to 301 the previous paths. To keep a high-traffic WooCommerce path as the public URL, you can set the product's custom_url during creation.
| Page type | WooCommerce (typical default) | BigCommerce (short default) |
|---|---|---|
| Product | /product/blue-hoodie/ | /blue-hoodie |
| Category | /product-category/hoodies/ | A category URL such as /hoodies/ |
| Shop archive | /shop/ | No direct equivalent; use a "shop all" category or the closest top-level category, and 301 /shop/ to it |
| Page | /about/ (depends on WordPress permalinks) | A web page URL you define, often /about/ |
| Blog post | Depends on the WordPress permalink setting | The BigCommerce blog permalink you assign; 301 the old path |
Redirect each product, category and article to its equivalent. Send discontinued products to a replacement or the parent category, not a homepage dump (Google may treat those as soft 404s). Import the map in Settings → 301 Redirects using relative paths from the store root, after the catalog and pages exist, because the platform will not accept a redirect from a path that is already a live page. Paginated archives can redirect to the equivalent first page or category.
Metadata, sitemaps and Search Console
Move unique titles and meta descriptions into the SEO fields for the homepage (Settings → Website), products, categories, web pages and blog posts. Recreate structured data your WooCommerce SEO plugin was outputting if the new theme does not already emit it, and check robots plus the www versus non-www redirect so the sitemap and canonicals agree.
Every BigCommerce store generates an XML sitemap at /xmlsitemap.php, documented in Locating Your Sitemap and the Google Search Engine article. After cutover, submit that sitemap in Google Search Console. If you are keeping the same domain, do not use Change of Address. Inspect key pages, watch coverage and 404 reports, and request indexing for high-value URLs that are slow to recrawl.
Payments, apps and the theme
These almost never come across with the catalog, and they are the pieces customers notice first if they are missing.
- Payments. Payment gateways must be enabled separately on BigCommerce. Do not assume saved cards or tokens move with a standard catalog migration. Reconnect the gateways you will use, run test orders, and check failed-payment messaging and any regional methods you rely on.
- Tax and shipping. Tax classes, zones and rates are not transferred in the official data-transfer table. Configure them on the new store, test several addresses (including exempt and international cases if you sell that way), and rebuild shipping methods against a rate card or live tickets.
- Apps and integrations. Apps have to be installed separately. For each WooCommerce plugin on your audit list, pick a native BigCommerce feature, a marketplace app or a custom integration. Leave time for email, search, reviews, subscriptions, inventory and analytics.
- Theme and templates. A WordPress theme will not become a BigCommerce Stencil or headless storefront. Rebuild the homepage, listing and product templates, cart, checkout styling within what the platform allows, and account pages. That is also the moment to tighten product-page and checkout UX, which our store optimization work follows on other platforms and applies the same conversion principles here.
Testing checklist
Test on the staging or unpublished BigCommerce storefront, with payment and shipping in test mode where the provider allows it, before you touch DNS:
- Product detail: options, inventory, images, reviews, and add-to-cart for simple, variable and digital products.
- Navigation, search, filters, and a "shop all" path if you created one for
/shop/. - Checkout: guest and logged-in, discounts you still honour, tax, shipping, payment success and failure, confirmation email, and the order in the control panel.
- Accounts: registration, password reset, address book, imported order history, and any customer-group pricing.
- Key pages, blog posts, forms and legal pages.
- A scripted sample of old URLs, checked for 301s to the right destination, with no chains or loops.
- Titles, canonicals, robots, sitemap contents, and structured data on product and article pages.
- Analytics and pixels firing once for views, add-to-cart, checkout and purchase, plus a pass on the mobile templates you will actually ship.
Launch day
BigCommerce says you can keep your existing domain, and that the old store can stay live during data transfer, with the only planned outage at cutover. Freeze catalog and order changes on WooCommerce, or plan a short final delta import. Put payments, SSL, domain settings and staff accounts in their final state, and name a rollback owner. Switch DNS in a low-traffic window, then confirm the 301 map is serving on the live hostname, not only on a preview URL. Send the customer password-reset notice, place a small real order to prove the live gateway, and submit /xmlsitemap.php in Search Console.
Leave the WooCommerce install running, but not indexed, until you are confident in the new store. A password-protected or noindex copy is a useful reference for product data, order history and old URLs. Do not leave it publicly indexable in parallel with the new site.
Post-launch monitoring
In the first two weeks, crawl the live domain against your pre-launch URL list and fix new 404s or redirect chains quickly. Watch Search Console for coverage errors, soft 404s, and drops on the URLs that used to carry the most impressions: a short dip can be normal, a cluster of 404s or homepage redirects is not. Watch analytics for checkout completion and landing pages that suddenly have no sessions, and spot-check imported orders, inventory and customer accounts daily for the first week. If you change URL structure after launch, add the matching 301s immediately.
Once the store is stable, you can reduce WordPress to a private archive or a lightweight redirect host. Google still asks you to keep the redirects in place for at least a year. Reconnect growth work on the new domain: paid media, lifecycle email and on-site conversion, the same disciplines we run through our ecommerce marketing programs, including paid ads and email and SMS.
Common pitfalls
These problems show up after a move, not during the import progress bar.
Assuming default URLs
WooCommerce permalinks vary widely. If you build the redirect map from textbook defaults instead of a crawl of the live site, you will 404 the URLs Google and customers actually use.
Redirecting everything to the homepage
It is fast, and it is the wrong fix. Google's site-move guidance treats large numbers of irrelevant redirects as a soft-404 problem. Map URL by URL.
Importing redirects too early
If the old path already exists as a live BigCommerce page, the redirect import can be rejected. Create products, categories and pages first, then import the map, then test.
Silent password failures
Customers will try their old WooCommerce password, fail, and assume the store is broken. Warn them, test the reset email, and do not bury the forgotten-password link.
CSV-only thinking for orders
Orders cannot be imported with BigCommerce's CSV tools. If order history matters, choose the app, the API or a managed service, and still keep the WooCommerce export.
Forgetting apps, tax and payments
A perfect catalog on a store that cannot tax correctly, or that is missing the review, search or subscription app, is not a launch. Rebuild the operational stack on purpose.
Leaving WordPress indexable
Two live, indexable copies of the same catalog compete and confuse the redirect story. After cutover, the old site should redirect or be closed to indexing.
Changing URLs after launch without 301s
If you switch from short to long or category URLs after the domain is live, 301 the previous BigCommerce paths or you will undo the map you just built.
How Startup Slang helps
We are an AI-first marketing and development agency in Toronto and Montreal. Our BigCommerce team plans and builds storefronts, and our services group covers the development and marketing work around a replatform. For a WooCommerce to BigCommerce move, that usually means the audit, catalog and URL mapping, storefront build, redirects, launch and the first weeks of monitoring.
After launch we can keep going on growth through ecommerce marketing, and through AI services when automation or content operations are part of the brief. If you are ready to talk through the catalog and the timeline, get a proposal.
Sources
Official documentation, checked in November 2026:
- Migrating to BigCommerce and the Data Migration app listing
- Transferring Your Data to BigCommerce
- Prepare Your Migration Data
- SEO Fields (URL structure), Backing Up Your Store (301 import), Locating Your Sitemap, Google Search Engine
- Managing Customer Accounts and Importing and Exporting Customers
- Using BigCommerce for WordPress
- WooCommerce Product CSV Importer and Exporter
- Google Search Central: Site Moves and Migrations
Frequently asked questions
Can I keep my domain when I migrate from WooCommerce to BigCommerce?
Yes. BigCommerce says you can keep your existing domain by updating DNS and setting 301 redirects. A same-domain move does not use Search Console's Change of Address tool; that is for a change of domain or subdomain.
Will my customers' passwords work on BigCommerce?
Usually no. BigCommerce states that customer passwords cannot be migrated for PCI compliance. Import the customer records, then have shoppers set a new password with the forgotten-password flow, or force a reset on next login. Tell them before launch.
Can I move historical WooCommerce orders to BigCommerce?
Yes, but not with a CSV file. The Help Center says orders can be imported with the Data Migration app, the API, or Data Migration Services. Export your WooCommerce orders anyway and keep that file for tax and support.
Will I lose my Google rankings when I move from WooCommerce to BigCommerce?
A temporary dip while Google recrawls is normal. Lasting losses usually come from missing or irrelevant redirects, dropped content, or canonicals that still point at the old site. Map every important URL, use 301 or 308 redirects, migrate titles and descriptions, submit the new sitemap, and monitor Search Console. Keep redirects in place for at least a year.
What is the difference between the Data Migration app, CSV import and a third-party tool?
The Data Migration app is BigCommerce's official self-serve importer from WooCommerce, documented for products, customers and orders up to its published record limit. CSV import is a good fit for products, customers and bulk 301 redirects, but not for orders. Third-party services and certified partners can help when you need a broader dataset. Check current pricing and the object types each option supports before you choose.
How long does a WooCommerce to BigCommerce migration take?
It depends on catalog size, plugins and integrations. BigCommerce publishes broad ranges: 500 SKUs or fewer can take one to two weeks, mid-size stores three to six weeks, and large stores up to twelve weeks. Treat those as published estimates, not a promise for your stack. We give a timeline after an audit.
Do I have to leave WordPress to use BigCommerce?
No. BigCommerce for WordPress is an official plugin that keeps WordPress for design and content and uses BigCommerce for catalog, checkout and orders. It requires WordPress permalinks set to Post name, and it is not available on a Multi-Storefront-enabled BigCommerce store.
What happens to payment gateways, tax, shipping and apps?
They are not carried over by a standard catalog migration. Payment gateways must be enabled separately, tax must be configured separately, and apps must be installed separately. Rebuild and test all of them before you switch the domain.
