Moving to BigCommerce starts with knowing what you have. We go through your products, customers, content and the tools connected to your store, like inventory, shipping and tax. Then we map out the data move, the storefront work and the launch, so you have a plan you can sign off on.
BigCommerce Partner
Migration and development. View profile ↗
Illustrative workflow, not a live project
Big Cartel
CS-Cart
Drupal Commerce
Ecwid
Joomla
Lightspeed
Magento
Miva Merchant
Network Solutions
OpenCart
OroCommerce
osCommerce
PrestaShop
Sana Commerce
Shift4Shop
Shoplazza
Shopify
Shopware
Turbify
Volusion
Weebly
Wix
WooCommerce
Zen Cart
ZoeySend us your site address. We’ll work out what it runs on and tell you what we need to see.
Which records move automatically varies by platform and by store. We review yours first and confirm what can come across to BigCommerce.
Handmade wooden gifts & religious artifacts
We moved Earthwood Products from Volusion to BigCommerce after 15 years, then built wholesale on top: customer groups, per-product minimums, a $150 order minimum and purchase order checkout.
Read the case study
“I had Volusion for 15 years as my host and it was never a very good experience. i have wanted to move to another provider and i finally did that using Ecommerce pros. It was a great experience. They delivered as promised. They even did some things that i wanted done that weren't really in the quote and they didn't charge for that. Definitely would use them again!!”
Cris · BigCommerce migration
Send your website address, the platform you’re on now and a line about what you want from BigCommerce. We’ll go through your data, storefront features and connected systems, then write up the scope, the costs and how we’d approach launch.
You don’t need to export anything or share a login to begin. Keep passwords, API keys and customer files out of this form.
Variant choices and SKUs
Each file on its product
How customers browse
Extra product details
Marketing consent handled on its own
Brought in or archived
Depends on access at the source
The content we agree on
Titles and descriptions come along
Old links get tested
Set up again and tested
Checked and agreed with you
What we look at, what happens to it on BigCommerce and how we check the result.
| Information reviewed | Proposed treatment | Main acceptance check |
|---|---|---|
| Products, variants and SKUs | Imported. The agreed products with their valid variants, identifiers, prices and stock. | Every combination, SKU, price, stock level and active status. |
| Images and media | Imported. Image files and the products they belong to, where we can reach them. | The right image on the right product and variant. |
| Categories, collections and navigation | Imported and rebuilt. Categories, menus and filters are set up around how BigCommerce structures a catalog, which can differ from your source categories, collections and rules. | The browsing structure and the key landing pages. |
| Custom information and specifications | Imported and rebuilt. Custom fields, the fields of a suitable app or page content we agree on. | Details show up where customers look for them. |
| Information reviewed | Proposed treatment | Main acceptance check |
|---|---|---|
| Customers and addresses | Imported. The profiles and addresses we agree on, with marketing consent mapped on its own. | Duplicates, useful history and separate proof of permission. |
| Historical orders | Imported or archived. Either an agreed import or an archive you can still open. | Items, totals and fulfillment status, with no new emails, shipments or charges triggered. |
| Accessible genuine reviews | Imported. Through a compatible review app, depending on access at the source. | Real reviews, matched to the right products and credited to the right people. |
| Account sign-in | Rebuilt. You pick the BigCommerce customer account experience. Passwords are handled apart from customer records. | How existing customers log in and what they see once they do. |
| Information reviewed | Proposed treatment | Main acceptance check |
|---|---|---|
| Pages and blog content | Imported and rebuilt. Content we agree on is recreated or brought across. | Formatting, links and embedded media. |
| SEO titles and descriptions | Imported. The agreed titles and descriptions are carried over. | The right title and description on each page. |
| URLs and redirects | Rebuilt. Each old URL worth keeping stays, or points to a relevant page on BigCommerce. | Redirects, canonicals and internal links all get tested. |
| Information reviewed | Proposed treatment | Main acceptance check |
|---|---|---|
| Apps and custom functionality | Rebuilt. A BigCommerce feature, a suitable app or scoped development. Importing data won’t recreate code written for another platform. | The feature behaves the way your team expects. |
| Pricing, promotions and business rules | Rebuilt. BigCommerce features, an app or development, matched to the plan and setup you choose. | Each customer group sees the right products and prices. |
| Balances and recurring commitments | Rebuilt or archived. Balances, subscriptions and credits are reconciled, and each gets a treatment we agree on. | Value is honored once and can’t be spent twice. Subscriptions, payment credentials, gift cards and credits are each assessed on their own. |
| Connected systems and payments | Reconnected. Agreed connections, with a named owner for every type of record. | Records move in the direction we agreed and a test order goes through. |
Some records import after cleanup. Some features need a different build. Some systems get reconnected, and some history is better kept in an archive you can open. What can move depends on what we can access at the source and what is practical, so exceptions and extra costs are written down before you approve the scope. We can’t promise that every data type transfers from every platform.
What the feature does for you right now.
A built-in BigCommerce feature, an app, an integration or scoped development, and we explain the cost and the trade-offs.
The test we run to confirm it works as your team expects.
Typical examples include product options, wholesale pricing, subscriptions, search, loyalty, fulfillment and accounting. Until we’ve looked at your store, we can’t name the app or promise identical behavior.
These are samples. Your proposal maps the requirements found in your own store.
| Current requirement | Proposed BigCommerce approach | Acceptance check |
|---|---|---|
| Product personalization | Product options, an app or development that fits | Customer instructions show up on the order |
| Wholesale pricing | A customer and pricing setup that fits | Approved wholesale customers see the right prices |
| ERP stock updates | The connection we agree on | Stock levels and orders match up |
| Navigation | Categories and menus mapped across | Main buying paths work end to end |
Theme setup, layouts that fit your brand, product pages and navigation.
Explore BigCommerce design →Custom functions and connections for the times an app can’t do the job.
Explore BigCommerce development →Migration checks on URLs, content and metadata. Ongoing optimization is a separate service.
Each piece of work gets its own line. Migration, storefront work, extra development and optional ongoing services are listed separately, so you pay only for what you pick.
We plan and test the migration SEO work we’ve agreed on, though rankings and traffic can still move after a platform change. How redirects behave depends on the source platform and the approach we settle on, so we can’t promise unchanged traffic or complete redirect coverage. Our article on SEO considerations for ecommerce migration goes deeper.
Illustrative example paths only. We work from your store’s actual URLs, redirects and settings.
We go through your catalog, data, features, URLs and connected systems, then put together a proposal covering scope, the BigCommerce setup we recommend, who handles what and the quote.
You approveThe scope, the quote and who is responsible for what.
We decide what transfers where, then try the tricky cases on a handful of sample records.
You reviewThe sample records and the harder buying scenarios.
We build the private BigCommerce store, set up the storefront and hook up the apps and systems we agreed on.
You reviewThe private BigCommerce store, before anyone else sees it.
We compare the data against your source and go through the buying paths together.
You reviewThe data checks and test orders.
We apply the last agreed updates and run the switch once you give the go-ahead.
You approveThe call on when to go live.
We look at what happened around the switch, account for any late records and then hand the store to you.
You receiveThe finished store plus post-launch support.
Migration apps, exports and authorized APIs can help move the records they support. Our managed service covers the mapping, storefront, features, testing and launch work around that transfer. A free migration app doesn’t make the whole managed project free. How long it takes depends on your store, and your proposal confirms timing after the review.
We get the agreed records ready while your current store carries on as normal.
You look over the private BigCommerce store with us and we fix the issues we agreed on.
Records that keep changing get a last update, then we manage the cut-off and the switch itself.
We check activity around the switch and account for any missing records, even a single order.
That way the switch follows a plan everyone has seen.
We can’t promise zero downtime, uninterrupted checkout or unlimited automatic synchronization. You’ll know in advance what happens during the switch, and we advise keeping the original store open until the agreed checks are done and nothing still depends on it.
Company accounts, pricing, order quantities, payment terms and how business customers place orders.
Separate domains, catalogs, languages and currencies running on shared operations.
Which system owns each record, which way updates travel and an order flow that has been tested.
Point of sale choices, recurring commitments, access to digital products and items that behave unusually.
We assess each of these before promising anything. Every one gets checked against the right BigCommerce configuration, plan, apps and implementation, since not every capability comes with every plan or every migration project.
I had Volusion for 15 years as my host and it was never a very good experience. i have wanted to move to another provider and i finally did that using Ecommerce pros. It was a great experience. They delivered as promised. They even did some things that i wanted done that weren't really in the quote and they didn't charge for that. Definitely would use them again!!
The online store migration was seamless without having 0 downtime. The staff is properly trained, well communicated and proactive Highly recommended
Web commerce pros created a really lovely design for our website. They also changed the layout for our images and updated/resized images so that the site is overall much more attractive. We have been receiving a lot of positive feedback from customers on the ease of use and the overall look of our site. In addition, we are very grateful to Roy for coming up with a creative solution for allowing customers to easily create their own quotes, which has been very helpful to both our operations and our customers.
The first two reviews come from BigCommerce migrations. The other two are about Shopify migrations and keep their original labels. Our 5.0 rating reflects all client reviews, including projects that weren’t on BigCommerce.
How much data we can reach and how tidy it is.
The variants, options and custom fields you use.
Customer accounts, past orders and balances.
The theme, pages and layouts you want.
Rebuilding what your apps and custom code used to do.
Customer groups, pricing rules and extra storefronts.
Links to your ERP, PIM, shipping and accounting tools.
URL mapping, checks and the switch itself.
Each part of the cost appears on its own line, so no single number hides anything. Platform plans, apps and payment providers set their own terms and change them over time, which is why we confirm current options while scoping. We make no assumption that BigCommerce will cost more or less than your current platform.
New features and ongoing development are separate work. Our BigCommerce development and integrations services cover those.
60 days freepost-launch migration support
What it typically covers
Yes, once we’ve looked at your setup. We check the source platform, the records we can reach and the functionality you rely on before confirming the route and scope. Send your website address and current platform, or tell us the store is custom-built, and we’ll explain what can transfer, what has to be rebuilt and what we need from you.
Yes. We go through the catalog, apps, content, customer records and integrations on your Shopify store, then agree how each part moves to BigCommerce. Our dedicated Shopify to BigCommerce migration guide has the detail.
That depends on your products, how customers buy, how you operate and what it all costs. We work with both Shopify and BigCommerce, so we compare the proposed setup against what your business needs. BigCommerce isn’t automatically the right destination for every store, and if another route suits you better, we’ll tell you.
The products, customers, orders, content and SEO information we agree on and can access. What transfers depends on the source platform and on how each record maps to BigCommerce, so your proposal lists every record type and how it will be handled.
Partly. Design elements we agree on can be recreated on BigCommerce, but themes and platform-specific apps or custom code generally don’t carry over. Each feature needs a BigCommerce feature, a suitable app or scoped development, and an acceptance check.
Each is handled on its own. A customer’s contact record is one thing, and their password and payment credentials are another. Subscriptions, stored payment methods, gift cards and store credit each get an individual assessment, and we confirm a supported method or an alternative before launch.
Where it makes sense, we keep suitable URLs, map changed paths to relevant pages and test the agreed redirects and SEO settings. A platform change can still affect rankings and traffic, so we can’t promise unchanged results.
Usually, yes. Preparation happens apart from your live store, and we agree the final update and cutover plan around your source platform and integrations. If there will be temporary restrictions, we tell you in advance.
We settle which system owns each changing record, how final updates are made, when the cut-off is and how late activity gets reconciled. Not every tool supports automatic synchronization, so we confirm the method for your store rather than assuming.
The price depends on your store, so your proposal sets it after the free store review. Our professional services are listed apart from the recurring platform, app and payment-provider costs, so you can see each one on its own.
We confirm the timeline after reviewing complexity, source access, dependencies and your approval points. Running the data import is only one piece of the project, so its duration says little about the overall timeline.
Every migration includes 60 days of free post-launch migration support within the agreed scope. Your proposal spells out what that covers and what you’re responsible for at handover. New features and ongoing development count as separate work.
Heading to a different platform? Take a look at our shopping cart migration services or our Shopify migration services.
Tell us where your store lives now and what the next one has to do. We’ll walk you through the migration scope, the storefront work and the launch plan.
Or call 888-711-2347
Want the full contact page instead? Contact Web Ecommerce Pros
Includes 60 days of free post-launch migration support inside the agreed scope.
