Volusion → to Shopify

Volusion to Shopify: getting off a platform that stopped moving

Volusion stores tend to be old, large and profitable, which is exactly why leaving feels risky. Fifteen years of orders, a catalog with thousands of SKUs, and URLs that have ranked since 2010. This guide is how we move Volusion V1 stores to Shopify without breaking any of that, including the parts the automated tools skip.

Why stores leave Volusion

• The platform is not developing. Volusion has been through ownership changes and a bankruptcy, and the V1 admin that most long-running stores use has not materially changed in years. Security patches and feature work have slowed to a trickle.
• Checkout and payments. No Shop Pay, no accelerated wallets beyond the basics, and a checkout that cannot be customized.
• Bandwidth and overage fees. Volusion still bills on bandwidth, which punishes image-heavy catalogs.
• Templates. The theme system is dated, mobile performance is poor, and finding developers who still work on it is getting harder.
• Integrations. Email, reviews, ERP and shipping tools have either dropped Volusion support or never had it.

What migrates from Volusion to Shopify

Volusion’s admin exports are better than most legacy platforms, and its API, while old, is usable for orders and customers.

Data	Source on Volusion	Moves to Shopify?
Products with codes, names, descriptions, prices, sale prices, stock, weights, categories, images, option sets	Inventory, Import/Export, Products (CSV, all columns)	Yes. Volusion child products (the option combinations) become Shopify variants. Products with more than three option types or more than 2,048 combinations need a restructure, which we plan in the audit.
Categories and subcategories	Categories export	Yes, as collections with the hierarchy preserved through tags and menus.
Orders with line items, totals, tax, shipping, payment status, tracking numbers	Orders export or the Volusion API	Yes. Imported as real orders with the original order number, date, a paid transaction and per-shipment tracking. Refunded orders get a real refund record.
Customers with addresses, order history, email marketing consent	Customers export	Yes. Consent carried exactly. Guest orders are linked by email.
Passwords	Not exportable	No. Reset on first login or passwordless accounts.
Reviews	Product reviews export	Yes, into Judge.me or your chosen app.
Coupons and gift certificates	Exports exist for both	Coupons recreated as discount codes. Gift certificate balances recreated as Shopify gift cards.
Custom fields, MAP pricing, per-product shipping	Product export columns	Custom fields become metafields. Per-product fixed shipping becomes a shipping profile.
Templates and articles	Manual	Design rebuilt on Shopify. Content pages moved by hand.

The Volusion URL problem

Volusion product pages live at /product-name-p/product-code.htm and categories at /category-name-s/id.htm, with the older /ProductDetails.asp?ProductCode=XYZ form still indexed on many stores. Shopify uses /products/handle and /collections/handle. Both old forms need redirects, and the product code in the URL is the reliable join key. We build the map from the export plus a crawl of the live site and the Search Console page list, so URLs that Google still holds but the admin has forgotten are covered too. Every redirect is requested against the live domain before launch.

Tools

Cart2Cart and LitExtension both support Volusion as a source and are fine for a first pass on products and customers. Neither migrates tracking numbers on shipped orders, both model refunded orders as simply paid, and both flatten the category URL structure into slugs that may never have existed. For stores with long order histories, which is most Volusion stores, we run the import ourselves so that every order reconciles to the cent, every parcel keeps its tracking number and every old URL resolves.

How we run it

1. Audit. Exports, API access, URL crawl, option-set analysis, integration inventory, fixed-price scope.
2. Build in a free Shopify development store. Theme, checkout, payments, shipping zones copied from Volusion’s rate tables, taxes.
3. Catalog restructure where needed for products that exceed Shopify’s option limits.
4. Sample import and sign-off, twenty of each entity including refunded, split-shipment and guest orders.
5. Full run. Silent import, no emails, no stock changes. Large order histories run over several days.
6. Redirects for both URL forms, tested individually.
7. Integrations, reviews import, gift card recreation.
8. Cutover with a delta sync, then a 30-day 404 watch.

Timeline and cost

Store size	Timeline	From
Under 500 products, under 5,000 orders	6 to 8 weeks	$2,500
Up to 5,000 products, up to 50,000 orders	8 to 12 weeks	$3,500
Larger catalogs, ERP or custom integrations, Shopify Plus	12 to 20 weeks	Quoted after audit

Fixed price after the audit, 50 percent to begin and 50 percent once the store is live and you are fully satisfied with the figures. You pay Shopify nothing until launch.

The Volusion exports in detail

Volusion V1 exports are wide CSV files from Inventory, Import and Export, and choosing the all-columns option matters because the default column set drops the fields that make the migration accurate.

Export	Columns that matter	Shopify destination
Products	ProductCode, ProductName, ProductDescription, ProductPrice, SalePrice, StockStatus, ProductWeight, PhotoURL, CategoryIDs, IsChildOfProductCode, OptionIDs, CustomField1 to CustomField10, MetaTag_Title, MetaTag_Description, ProductURL	Parent products become products; rows with IsChildOfProductCode become their variants. Custom fields become metafields. Meta tags carry across to the SEO fields. ProductURL is the redirect source.
Options	Option categories and option values with price and weight differentials	Options and variants. Differentials are applied to variant prices so the customer pays what they paid before.
Categories	CategoryID, CategoryName, ParentID, CategoryURL, meta tags	Collections with the hierarchy in menus and tags. CategoryURL is the redirect source.
Orders	OrderID, OrderDate, OrderStatus, PaymentMethod, SubTotal, Tax, ShippingCost, Total, ShipTo fields, TrackingNumber, plus the OrderDetails export with one row per line item	Real orders with the original number, a paid transaction and a fulfillment carrying the tracking number. Statuses map to paid, refunded, cancelled or pending.
Customers	CustomerID, email, names, addresses, EmailSubscriber, AccessKey (wholesale tiers)	Customers with consent from EmailSubscriber and wholesale tiers as tags or B2B companies.
Reviews	Product reviews with rating, name, date, text, approval status	Judge.me or your review app, matched on ProductCode.

Two things trip people up. Volusion HTML descriptions often contain inline styles and table layouts from the old template, which we strip so the text takes the new theme’s styling. And PhotoURL points at the Volusion CDN, which stops serving once the store closes, so images are downloaded and rehosted on Shopify before cancellation, not after.

Shipping, tax and payments

Volusion shipping is configured as methods with rate tables by weight, price or quantity, and many stores carry a decade of accumulated rules. We export the tables, rebuild the ones still in use as Shopify shipping profiles and zones, and retire the rest with your sign-off. Live carrier rates from UPS, FedEx or USPS need Shopify’s carrier-calculated shipping, which is included on Advanced and Plus and available on Grow with annual billing, so the plan choice is made in the audit rather than discovered at checkout. Tax by state moves to Shopify Tax, which handles nexus and rates automatically in the US. Payment gateways are re-entered; Shopify Payments is the usual choice, and Authorize.net or a merchant account can be kept where a contract requires it.

Common mistakes in Volusion migrations

• Exporting with the default column set and losing custom fields, meta tags and product URLs.
• Redirecting only the pretty URLs and leaving the ProductDetails.asp form, which is what old backlinks and Google’s memory point at.
• Cancelling Volusion before images are rehosted.
• Importing refunded orders as paid, which shows a balance owing on every one of them in the Shopify admin.
• Not deciding the carrier-rate question before the plan is chosen.

Checklist before you start

• Run all six exports with every column and keep the files.
• Crawl the live site and download the Search Console page list for the redirect inventory.
• List your shipping methods and note which ones customers actually use.
• Note gift certificate balances and active coupon codes.
• Keep Volusion active for at least two weeks after launch.

Wholesale customers and pricing tiers

Many Volusion stores run a wholesale channel through customer access keys and per-tier pricing, where a logged-in trade customer sees a different price list. On Shopify this becomes B2B on Shopify Plus, with companies, locations, price lists and payment terms, or on standard plans a customer-tag approach where tagged customers see discounts through automatic discounts or a wholesale app. The audit works out which fits: a handful of trade accounts with simple percentage-off pricing is fine on tags, while dozens of accounts with net terms, tax-exempt status and their own catalogs belong on B2B. Either way the tier assignments come from the customer export and nobody loses their pricing at launch. Tax-exempt customers, common on Volusion wholesale accounts, are flagged in the export and set as tax-exempt on Shopify with their certificate details stored on the customer record.

Reviews, Q&A and the marketing tools

Volusion’s built-in reviews export with the rating, reviewer name, date and text, and whether the review was approved. They import into Judge.me or the review app you choose, matched on product code, and the approved flag decides which are published. Product questions and answers, where the store used them, are exported and either rebuilt as an FAQ metafield on the product or loaded into an app that supports Q and A. Volusion’s newsletter tool and its abandoned-cart emails are replaced by Klaviyo or Shopify Email, with the subscriber list coming from the customer export’s EmailSubscriber flag so consent is exact. Affiliate tracking, if you used Volusion’s built-in affiliate program, needs an app such as UpPromote and a note to affiliates about new links.

A note on Volusion V2

Everything above describes Volusion V1, which is what the great majority of long-running Volusion stores use. Volusion’s newer platform, sometimes called V2 or VOLT, has a different admin, cleaner exports and an API that Cart2Cart and LitExtension also support. The migration is simpler because the URL structure is modern and the data model is closer to Shopify’s, but the process, the tooling choices and the cost bands are the same, and the checklist above applies.

What you get at handover

Every Volusion migration ships with a reconciliation ledger that runs from the export counts down to the live counts for products, variants, customers and orders, with every exclusion named; a redirect verification list covering both URL forms with the status each returned; the image rehost log; the wholesale tier mapping; and a recorded walkthrough of the Shopify admin for your team. Where the order history ran over several days, the ledger also shows the daily batches and any records that needed a second pass.

Questions we settle in the survey

• Which of the accumulated shipping methods do customers actually use?
• Do you need live carrier rates at checkout, which decides the Shopify plan?
• How many wholesale accounts are there, and do they need net terms?
• Which order statuses should import as paid, refunded, cancelled or pending?
• Is the store on Volusion V1 or the newer platform?

Frequently asked questions

Start with the migration survey. For a similar legacy platform, see the Shift4Shop guide, and for enterprise-scale stores the Shopify Plus migration page.