Volusion to BigCommerce Migration Services

Yes. BigCommerce documents a free Data Migration app that lists Volusion among its supported platforms, and data can also be brought in through CSV files, the API, or a managed migration service. What moves automatically versus manually differs by data type, so a scoped plan is the first step.

We did not find any official announcement of a Volusion shutdown as of this writing. Check Volusion directly for your account’s current terms and plan details, and keep your Volusion account active until your data has been exported and checked.

Export everything you may need first: products, customers, orders and any content. BigCommerce's guidance recommends keeping an export of historical orders for reference and tax purposes. Keep your Volusion store live until the new store has been tested and launched.

It depends on catalog size, how many option combinations your products have, how much custom work the design needs, and how many apps and integrations you must replace. Data transfer is often the shorter part, while theme build, testing and redirect mapping take most of the time.

Volusion's documented export tool sits in the admin under Inventory and Volusion API, where you can run Generic Products, Orders or Customers exports. It requires a Business or Prime monthly plan, and each run outputs up to 100 records, so larger catalogs need several runs. Volusion also offers other import and export options in its admin that are worth checking for your plan.

BigCommerce's product import uses a CSV with column mapping, and its documentation sets the upload limit at 20 MB per file. Images must be public HTTP or HTTPS URLs, and categories are assigned by category ID rather than name. Large catalogs are split into several files.

BigCommerce documents a maximum of 600 variants per product and says the modern CSV import supports variants but not creating modifier options. Volusion option combinations often need to be reshaped into BigCommerce variants or modifiers, so complex products are best mapped by hand and tested.

Categories are not created by product CSV import, since it assigns existing category IDs, so the category tree is usually set up first. Images are imported from publicly accessible URLs, which means they need to be reachable while the import runs. The Data Migration app or an API-based migration can handle some of this as well.

Yes. BigCommerce's customer CSV import requires email, first name and last name, and can include addresses, customer group and store credit. Customer import files are limited to 2 MB, so large lists are split into several files.

BigCommerce's migration guidance says passwords cannot be migrated from most platforms for PCI compliance, so customers typically reset on first login. A separate customer import article describes a Password column that can be mapped on import, but Volusion exports are not documented to supply usable passwords, so plan on password resets.

BigCommerce documents that orders cannot be imported by CSV. They can be brought in with the Data Migration app, the API, or the Data Migration Services team. Imported historical orders can be tagged so they do not count toward sales volume, and they do not deduct stock.

BigCommerce's support site lists gift certificates as transferable via CSV with a free importer app, though emails are not sent automatically. Customer groups can be set in the customer import, and BigCommerce supports price lists and B2B tooling, but the setup depends on your wholesale rules and should be scoped individually.

No. Themes are platform-specific, so the storefront is rebuilt on a BigCommerce theme. This is usually a chance to modernize the design, improve mobile layouts and rework navigation.

BigCommerce recommends 301 redirects from old URLs to new ones to limit SEO loss, and its Data Migration app creates them for products it migrates. Pages, categories and any URLs the app does not cover need their own redirect map, and trial stores cannot create redirects. No migration can guarantee rankings stay unchanged.

BigCommerce says web pages and blog posts are not covered by the Data Migration app or CSV import, but they can be imported through the API or pasted in as HTML. Page content is therefore often moved by script or by hand.

Possibly. Check which gateway and processor you use now and whether it is supported on BigCommerce for your country and business type. Payment setup, fees and approval times should be confirmed with providers before launch.

Cost depends on catalog size, custom design, integrations and how much data is moved by app versus by hand. BigCommerce's Data Migration app is described as free, while managed services and agency work are quoted per project. A scoped estimate is the only reliable figure.

Volusion add-ons do not carry over, so each one needs a BigCommerce app, native feature or custom integration. List every app and connection you use, such as accounting, shipping, marketplaces and email, and confirm replacements before the build starts.

60 days of free post-launch migration support within the agreed scope: migration-related data or functionality issues, agreed late records, broken links and included integrations. New features and ongoing development are separate work.