Volusion to BigCommerce Migration

Plan Your Volusion to BigCommerce Migration

Start with the records your business needs after the move. List products, categories, customers, historical orders, manufacturers, coupons, reviews, pages, and the supported blog fields. Keep source examples your team can compare during the Demo and after Full Migration.

Moving store data also involves checking relationships and preparing the new storefront. A product import does not complete historical orders, customer accounts, reviews, content, or checkout configuration. Choose the workflow that matches the work your team will handle.

Automated Migration is the primary workflow here. You control the configuration and review, with support available for migration issues. Record custom Volusion integrations, pricing behavior, and requirements outside the listed transfer before planning launch.

Prepare Backups and Representative Source Records

Keep copies of important Volusion data, images, and content. Record selected entity counts and retain products with options, several images, different quantities, historical orders with multiple items, coupons, reviews, and article pages for comparison.

If you create native Volusion API exports for backup, verify that they cover the complete record range. Volusion documents batched exports and export timestamps; a single response does not establish that the full order history is present. Keep order headers and line-item information together when checking completeness.

Prepare BigCommerce and review records already present there. Save a target backup before approving Clear Target Data, identify records that must remain, and decide how to handle Demo or test records before Full Migration.

Plan the target theme, apps, payments, shipping, taxes, notifications, domain, and checkout separately. Data migration does not convert Volusion templates, custom scripts, payment credentials, or fulfillment integrations into BigCommerce equivalents.

Step 1. Connect Volusion and BigCommerce

Sign in to the LitExtension app and create a migration. Select Volusion as Source Cart and BigCommerce as Target Cart, then enter the required store details.

Both platforms are hosted. Follow the source and target access instructions displayed by LitExtension rather than trying to upload an open-source connector to either platform. Keep the required connections available through the transfer and validation.

Complete connection checks before selecting data. If a check fails, review the store details and access setup, then share the error information with support. Native file exports can serve as backups without replacing the app’s connection requirements.

Step 2. Select Data and Configure Options

Products, Options, and Inventory Control Grid

Products include names, SKUs, short/full descriptions, status, manufacturer, prices, quantities, stock-management settings, meta titles/descriptions, weight, tags, attributes, variants, thumbnail images, and additional images. Volusion Product Code maps to SKU.

Volusion’s Inventory Control Grid associates option combinations with child products. Include parent products, child ProductCodes, and combinations that carry different quantities or prices in your Demo checks. Compare relationships and purchasing behavior as well as individual field values.

BigCommerce distinguishes inventory-bearing variants from modifiers that customize a purchase. Attributes and Variants are included as groups, but this does not recreate every dependency, swatch, text input, price adjustment, or custom rule. Test the selections your customers use, including unavailable combinations.

Special Price, product Tax Class, dimensions, creation dates, downloadable-product rules, grouped-product associations, and up-sells/cross-sells are not included. Keep requirements for those features separate from the standard transfer.

Product Categories and Manufacturer Names

Categories include names, descriptions, sort order, images, and meta titles/descriptions. Volusion category Thumbnail Image supplies the category image. Separate Category Parent, Hidden, and meta-keyword fields are not included. Review category assignments and prepare BigCommerce navigation separately.

Manufacturers include names only. Manufacturer images, descriptions, and metadata are not included. Check the target presentation with representative products rather than assuming the source manufacturer page design transfers.

Customers and Account Access

Customer profiles include first names, last names, emails, and billing addresses. Passwords, separate profile shipping addresses, newsletter subscriptions, standalone phone fields, and customer status are not included. Historical orders include billing/shipping addresses separately.

Volusion documents that customer passwords cannot be exported through its API or Import/Export feature. Prepare BigCommerce account access and password-reset communications before launch. Test the intended sign-in and order-history experience with representative target customer records.

Historical Orders, External IDs, and Final Stock

Orders include dates, statuses, items, subtotal, discounts, taxes, shipping price, total price, comments, customer names/emails, and billing/shipping addresses. Order Items and address fields remain groups without extra detailed-field promises. Order tags and tracking fields are not included.

Select Preserve Order IDs to retain original Volusion references in BigCommerce’s External ID field. BigCommerce assigns its own internal order IDs. Compare both identifiers in the Demo so customer-service staff know which reference to use when looking up older purchases.

Validate historical totals and customer relationships against source orders. Check final product quantities after the order transfer and any final updates, as well as after the catalog import. Use the source order as the reference for a historical price rather than the current product price.

Coupons and Product Reviews

Coupons include titles, codes, coupon dates, usage limits, fixed discount amounts, and start/end dates. Coupon descriptions, customer groups, percentage values, status, and minimum/maximum spend are not included. Test the promotions your target store needs before launch.

Reviews include creation dates, status, ratings, and comments. Reviewer names/emails, customer IDs, and review titles are not included. Inspect representative comments, ratings, and their storefront display during the Demo.

Volusion Articles and Blog Fields

CMS pages include titles from Page Name, content from Article Body, and status. Page URLs, last-modified dates, creation dates, categories, authors, and thumbnails are not included. Review page formatting, internal links, and the target design separately.

Blogs include titles from Article Title and creation dates only. Blog-body content, categories, URLs, summaries, and thumbnails are not included. Keep required article text and media for separate preparation; the presence of a Blogs tab does not mean the complete blog is transferred.

Standalone Taxes and Multiple Languages are outside this route. Historical order tax amounts do not configure checkout tax rules or recreate your source language setup.

Apply the Relevant Additional Options

Create 301 Redirects connects old Volusion URLs to relevant BigCommerce destinations. Preserve Order IDs stores source references as External IDs. Strip HTML Tags cleans product and category names.

Description Images transfers reachable images embedded in product and category descriptions. Check these separately from ordinary product and category images. It does not add embedded CMS-page image coverage or blog-body migration.

Clear Target Data removes existing records for selected migration entities. Save a backup, review the cleanup scope, and identify records that must remain before enabling it. Shopify Smart Collections does not apply to BigCommerce.

Step 3. Review the Free Demo and Complete Migration

Run a Free Demo before Full Migration. Compare product text, ProductCodes/SKUs, attributes, option combinations, prices, quantities, images, categories, customer billing addresses, external order references, totals, coupons, reviews, page content, and blog titles/dates.

Matching counts alone do not establish correctness. Investigate differences in parent/child relationships, order values, formatting, missing images, and target presentation. Provide source and target examples when asking support to investigate a discrepancy.

After resolving unexpected results, start Full Migration. It runs on LitExtension’s servers, so you can close your browser and return to check progress. Volusion can continue accepting orders during transfer. Your team reviews the completed automated transfer before launch.

Review SEO and Launch Readiness

Keep a list of important old product, category, article, and campaign URLs. Test redirects against relevant BigCommerce destinations, update internal links, and inspect product/category metadata. CMS URLs and blog-body content are outside this transfer, so plan those destinations and remaining content deliberately.

Check for missing pages and avoid redirecting unrelated URLs to a generic destination. Test navigation, account access, product options, stock behavior, discounts, payments, shipping, taxes, notifications, and checkout on desktop and mobile. Redirects do not guarantee unchanged search rankings.

Keep source access and assets available until validation and final updates are complete. Coordinate the domain switch and remaining source-store operations after testing the target, rather than closing Volusion immediately after the first transfer.

Plan Final Updates, Cost, and Timing

Track new and changed source records. Recent Migration transfers new records, Smart Update handles changes, and Re-migration reruns the transfer. These operations are free for 60 days and do not provide continuous synchronization. Review the final data and stock levels before launch.

Cost and timing depend on selected data volume, options, images, connections, and agreed custom work. Allow time for preparation, Demo feedback, Full Migration, validation, and storefront setup. Use Estimate Migration Cost or Schedule a Call to discuss requirements.