Store migration
We move Volusion stores onto Shopify with the catalogue, the customers, the order history and the gift certificate balances intact. Volusion stores carry two generations of URL at once, the old ProductDetails query strings and the newer .htm paths, and both are usually still indexed. Working out which of yours Google actually holds is the first job, not the last.
Why stores leave
Most Volusion migration pages lead with the 2020 bankruptcy. We think that is the weakest argument on the list, and we explain why below. These are the reasons that actually hold up.
2019
Attackers compromised Volusion cloud infrastructure and skimmed card details across thousands of storefronts. For a merchant weighing platforms, that is a more relevant piece of history than a restructuring that finished years ago.
V1
Classic Volusion is a SQL backed ASP application. If you are still on it, you are running a storefront built for a version of the web that no longer exists, and you face a rebuild eventually whatever you decide.
0
Shopify Store Migration imports from Square, WooCommerce, Etsy, Wix, Amazon, eBay, Clover and Lightspeed. Volusion is not on that list, so every route is a third party tool or a script.
Two
Volusion redirects its old query string addresses to the newer .htm paths, which means Google has often held both over the years. A redirect map built from only one of them leaves the other pointing at nothing.
What you gain
The case for moving is not that Volusion is about to disappear. It is that the gap between what Volusion ships and what your competitors are using widens every quarter, and closing it on Volusion is not something you can buy.
Shopify checkout is maintained by Shopify and carries Shop Pay. On Volusion the checkout is one of the harder things to modernise and one of the most consequential for conversion.
The pool of developers who will take on a Volusion build shrinks every year, and the ones who remain charge accordingly. Replacing a Shopify developer is a normal hiring exercise.
Wholesale pricing, multi currency, multi language and retail all sit in the platform rather than in bolt ons. For a Volusion store these usually arrive as capabilities you did not have rather than replacements.
Shopify allows 2,048 variants per product, not the 100 most guides still quote. The limit that bites is three options per product, and Volusion option structures do not always fit it without a decision from you.
The part nobody writes about
This is the most important section on the page. Volusion is unusual in that it has quietly been running its own redirects for years, and that changes what your migration has to account for.
.asp
Classic Volusion serves products from ProductDetails.asp with the product code as a query string parameter. Anything linked or indexed before you switched on friendly URLs is still that shape.
.htm
With search engine friendly URLs enabled, Volusion serves a path ending in .htm, with a marker for products and a different one for categories. Volusion then redirects the old query string form to this one, which is why both have been live for years.
Not
Shopify states that URLs containing query strings might not work as expected with URL redirects. So the .htm paths map cleanly and the .asp query strings need a mapping layer on the 404 template. A quote that treats them as one job has not looked.
100k
Shopify caps URL redirects at 100,000 on standard plans and 20,000,000 on Plus. Two URL generations across a large catalogue counts twice, so it is worth counting rather than assuming.
Rebuilt, not moved
Volusion storefronts are ASP templates with Volusion specific tags. None of it converts to Liquid, and on a V1 estate most of it should not be reproduced anyway.
Volusion templates do not convert. The front end is a rebuild on every replatform, and for a store that has been on V1 for a decade this is usually the point of the project rather than an overhead.
Anything written directly into the templates, and any add to cart or feed logic built around Volusion URLs, has no equivalent. Each capability becomes a Shopify app, a Function, a metaobject, or it goes away because the platform now does it.
Volusion option structures do not map one to one onto three Shopify options. Which of your choices earn a variant slot is a merchandising decision and it happens in week one.
Volusion customer groups and any tiered pricing become Shopify B2B price lists and customer segments. The logic survives, the mechanism does not.
Google Merchant Center and marketplace feeds built on Volusion export formats need rebuilding against Shopify. Stores routinely forget these until a channel goes quiet after launch.
Articles and pages carry across as content. The template furniture around them rebuilds as Shopify sections and metaobjects.
Scope
On a Volusion store two answers move the price more than anything else: which URL generations are indexed, and what shape your options are in.
What data migrates
The full entity list with the fields inside each one, because a list that just says products and customers is not something you can check a quote against.
Name, description, product code and SKU, UPC, price, sale price and cost, stock and stock tracking, weight and dimensions, vendor, every image in order, plus page title, meta description and the SEO fields attached to each product.
Volusion option structures become Shopify variants with absolute prices, inside the three option limit. Where an option was a text field or an upload rather than a real choice, it becomes a line item property instead of multiplying your catalogue.
Name, description, image and SEO fields. Categories become collections, and because Shopify collections do not nest, subcategory structure is rebuilt with tags and automated rules.
Names, email, telephone, newsletter status and full billing and shipping addresses. Groups become customer segments or B2B companies. Passwords do not move on standard plans, because Shopify cannot accept another platform hash. On Plus, Shopify support can whitelist a legacy algorithm and import them, which is the one real exception. Either way a reset campaign is planned for launch.
Order number and date, status, customer, billing and shipping addresses, and every line with its product, code, chosen options, quantity, price, discount, tax, shipping and total. Reconciled to the cent against your own data.
Outstanding balances are recreated as Shopify gift cards and the ledger is reconciled before cutover. This is the one entity customers notice instantly if it is wrong, and it is routinely left out of scope.
Codes, type, amount, minimum spend, validity dates and usage limits. Stacking rules get reviewed by hand, because the platforms disagree about how discounts combine.
Author, rating, text and date, matched back to the right product, loaded into Judge.me, Loox or Yotpo. Shopify has no native reviews feature to hold them.
Both URL generations are crawled and mapped, the .htm paths as native Shopify redirects and the .asp query strings through a mapping layer. Redirects are included in the price here, not sold as an extra.
What breaks
These are not hypotheticals. Each one is something an automated migration produces by default, and each one is cheap to prevent and expensive to discover after launch.
The automated tools model a refunded order as a plain paid order. Import fifteen years of history that way and your Shopify admin shows a balance owing on every refund you ever issued. Refunds have to be imported as real refund records against the order.
Order history arrives without the tracking numbers, so every historical shipment loses its parcel. Your support team finds out the first time a customer asks where something went in 2019. Tracking belongs on the fulfillment, and it has to be imported there deliberately.
Volusion product images are served from Volusion infrastructure. If they are referenced rather than downloaded and rehosted, they keep working right up until you close the account, then the catalogue goes blank. Images get rehosted before cancellation, never after.
Volusion exports let you choose the columns. The default set quietly omits the custom fields, the meta titles and descriptions and the product URLs, which are exactly the columns the migration and the redirect map depend on. Exporting with every column is a one click difference and it decides how good the result is.
The older query string addresses are what old backlinks and Google memory point at, and they are the ones a tool built redirect map skips. Shopify also says query string URLs may not redirect as expected, so those need a mapping layer rather than a row in the redirect table.
Live carrier rates at checkout are not on every Shopify plan. If your Volusion store quotes real time rates and nobody checks, the plan gets chosen and the capability is discovered missing at checkout testing. It is an audit question, not a launch week one.
Bolt ons to apps
Much of what a Volusion store pays for separately is simply part of Shopify, which is where the running cost usually falls.
Judge.me, Loox or Yotpo. Shopify has no native reviews feature, so this is one of the few places you add an app to keep what you already had.
Shopify Search and Discovery is free and covers most of what a paid Volusion search add on did. Klevu or Algolia where the catalogue justifies it.
Shopify B2B with price lists and quantity rules, native rather than an add on. For most Volusion stores this is an upgrade, not a replacement.
Shopify Markets with Translate and Adapt. Another capability that stops being something you buy and maintain.
The Google and Meta sales channels replace hand built export feeds, and they stay in step with the catalogue without anyone scheduling anything.
Rebuilt as an app or a custom app against the Admin API, often through middleware. Budget this properly. It is routinely the largest line after the theme.
The catalogue
Volusion lets you build a product from as many choices as you like. Shopify gives you three option slots and 2,048 variants. Reconciling those two models is the most consequential decision on the project and it happens in week one, not week fifteen.
The choices that drive price, stock or a distinct image earn a slot. Everything else is describing the product rather than varying it.
Personalisation text, a date, an uploaded file. These become line item properties. Treating them as options is how a catalogue turns into thousands of rows nobody can manage.
Where a choice added to a base price, that has to resolve into a real price on every variant, then get checked against your own price list rather than against the tool reporting on itself.
Easier to hit than the variant limit and mentioned by nobody. A product with an image per variant can run out of media before it runs out of variants.
Free
The same checklist we run internally. Forty one items across the URL audit, options to variants, gift certificates, data, redirects, feeds and launch. No email wall.
We reply within one working day.
How it runs
You keep trading on Volusion until the day we cut over. Nothing goes live until the numbers reconcile against your own data.
We crawl the live store and measure which URL generations are actually indexed, then look at the option structures and the gift certificate ledger. Those three answers shape the rest.
Start with the audit
The audit stands alone. If it says stay on Volusion for now, that is what it will say.
Book the auditEvery Volusion field gets a Shopify destination in writing and you approve it before anything is imported. This document is what prevents a rebuild in week fifteen.
A full import into a development store, then reconciliation against your own data. We expect to find problems here. That is what it is for.
Theme, apps, feeds and integrations, alongside the data work rather than after it.
A delta import picks up everything that sold while we were building, then DNS moves. Both redirect generations are live at the moment the domain switches.
Monitoring, Search Console, and the fixes that only surface once real customers are using it. Included, not billed separately.
Talk to us about your store
Send the address and we will tell you what the move actually involves.
Get a migration planSituations
Written as scenarios rather than logos. We do not publish client names or numbers without written permission, and we are not going to start on a page that is trying to win your trust.
Hobby and model retail
Old query string addresses and newer .htm paths were both in the index, because the store had switched on friendly URLs years after launch. The crawl found both and each got its own route to the new page.
No indexed page lost its destination
Speciality food
A four figure balance in outstanding certificates was sitting in the ledger and was not in anyone scope. It was exported, reconciled and recreated as Shopify gift cards before cutover rather than discovered by a customer at checkout.
Every balance honoured on day one
Industrial supply
The shopping feed was built from Volusion URL formats and would have broken silently at cutover. It was rebuilt against the Shopify catalogue and tested before the domain moved.
Shopping channel never went quiet
Search
Volusion has been redirecting its own old addresses to newer ones for years, so what is indexed today is rarely what the admin would suggest. Nobody can quote your migration honestly without crawling it first.
The friendly URL setting tells you what Volusion serves now. It does not tell you what Google has held for the last ten years, and the second one is what your traffic depends on.
The .htm paths become native Shopify redirects. The .asp query strings need a mapping layer, because Shopify says query string redirects may not behave as expected.
Product redirects are mechanical. Category pages are usually where the links and the rankings sit, and where the path change is largest.
Not the next morning. The map is loaded and tested on the development store, then goes live with the DNS change.
What you get
Not a list of intentions. Each of these is either in the contract or it is not, and you can hold us to every one.
OpenCart keeps selling for the whole project. A delta import picks up everything that sold during the build, then DNS moves. Planned downtime is zero, and the old store stays up afterwards, read only, so a bad week is recoverable.
Every URL that returns a 200 is crawled and mapped before launch, and the redirects go live with the DNS change rather than the next morning. Titles and meta descriptions carry across unchanged. Redirects and SEO URL mapping are in the price, not paid extras.
One named person who knows your store, runs the weekly call, and is the same person on launch day. You are not handed between a salesperson, a migration operator and a support queue.
Everything lands in a development store first and is reconciled against your own database. Variant counts, every variant price, order totals to the cent. The production import repeats something that already worked.
One number and one launch date, not a range and not an hourly estimate that drifts. If the audit finds something that changes the scope, you see it before you commit, not after.
Search Console watched daily, 404s fixed as they appear, stock levels sanity checked and Core Web Vitals tracked. Included in the price rather than sold back to you as support.
Cost
We quote fixed after the audit, never as a range before it. On Volusion the first two items move the figure more than anything else.
One indexed generation is close to mechanical. Two generations, which is the common case, means a native redirect map plus a mapping layer built and tested. We show you which you have before quoting.
A catalogue that fits three Shopify options cleanly costs less than one that needs restructuring, and Volusion products built from four or five choices are common.
Reconciling a certificate ledger and rebuilding live product feeds are real work that automated quotes leave out entirely.
Rebuilt as it is, given a facelift, or redesigned. All three are quoted inside the migration rather than as a second project.
ERP, accounting and 3PL connections are discrete rebuilds and the usual cause of an overrun.
Also migrating from
The playbook is mostly shared. What changes is where the platform hides your data and which constraints bite on the way in.
The closest relative here. Self hosted, and the same query string redirect problem.
Self hosted and module heavy, with categories that often sit at the root of the domain.
Self hosted and extension heavy, with a product model closer to Shopify variants.
A SaaS to SaaS move, so the data is clean and the work sits in the storefront and the apps.
Shopify imports WooCommerce natively, which makes it the easiest path of any platform here.
The opposite problem. The data is locked in and the export is the hard part.
Who you are hiring
The rating and the review count are on our Shopify Partner Directory listing, so you can verify them right now rather than take our word for it. The rest are commitments we put numbers on, because a number is something you can hold us to.
Risk
A migration you cannot reverse is a migration you should not start.
Keep the store running for a month after launch, read only. It costs very little and it means a bad week is recoverable rather than theoretical.
Every entity exported and held by you before a single record is imported, including the gift certificate ledger.
Everything lands in a development store and is reconciled first. The production import repeats something that already worked.
The native redirects and the mapping layer are both exercised on the development store against a list of your real indexed URLs, not a sample.
Never into a promotion and never on a Friday. The delta import means nothing is lost by waiting for the right morning.
Questions
The questions merchants actually ask, answered against Shopify and Volusion documentation and the public record rather than against what reads well.
No, and we would rather tell you that than sell you a migration on a scare. Volusion filed for Chapter 11 in July 2020 and emerged in January 2021 after restructuring. It is now owned by Newfold Digital, the group behind Bluehost, HostGator and Network Solutions, so it has more corporate backing today than it did then. The reasons to move are the 2019 breach, the age of the V1 architecture, the pace of change elsewhere and the shrinking developer pool. Those hold up without anyone needing to imply the lights are about to go out.
No. Shopify Store Migration imports from Square, WooCommerce, Etsy, Wix, Amazon, eBay, Clover and Lightspeed R and X. Volusion is not on that list, so every route in is a third party tool such as Cart2Cart, LitExtension, MigrationPro or Next-Cart, or a bespoke script against your exports and the Shopify Admin API. For a store with two URL generations and a certificate ledger we write the script.
They need a mapping layer. Classic Volusion serves products from ProductDetails.asp with the product code as a query string, and Shopify states that URLs containing query strings might not work as expected with URL redirects. So those get a layer on the 404 template that reads the old product code and routes it to the right Shopify product. Your newer .htm paths map cleanly as native Shopify redirects. Most stores need both, and most quotes account for one.
By crawling the live store and checking Search Console, which is the first thing the audit does. Volusion has been redirecting its own old addresses to the newer ones for years, so what the admin says it serves today tells you very little about what Google has held over a decade. Reading the setting is not a substitute for looking.
They are exported, reconciled and recreated as Shopify gift cards before cutover, so a customer with a balance can spend it on day one. This is real money you owe and it is the entity customers notice instantly if it is wrong. It is also the one most often left out of an automated migration scope, so ask any quote whether the certificate ledger is included.
On standard Shopify plans, no. Shopify has no way to accept a password hash from another platform, and the password fields on the customer API are deprecated, so customers reset on first login and we send that campaign as part of launch. On Shopify Plus there is a narrow exception worth knowing about: Shopify support can whitelist a legacy hashing algorithm and import the existing hashes, so customers keep their passwords. It is a support request on an enterprise plan, not a checkbox, and no migration app does it for you. If a provider offers password migration without mentioning Plus and a Shopify support ticket, ask which of those two they are leaving out.
It makes the case stronger rather than the project harder. V1 is a SQL backed ASP application and the storefront is from an earlier era of the web, so you face a rebuild eventually whatever you decide. It also means you are the most likely to have two URL generations indexed, which is the thing worth measuring before anyone quotes.
Six to ten weeks for a store with a clean catalogue, one indexed URL generation and no ERP work. Three to six months is the common range once feeds, integrations, a custom theme and a mapping layer for the old query string URLs are in scope. We give you a date with the fixed price after the audit rather than a range before it.
We do not publish a price here, because any number we put on this page would be wrong for most readers. The audit produces a fixed price and a launch date. On Volusion the two things that move it most are how many URL generations are indexed and whether your option structures fit three Shopify options.
Yes. Volusion stays live and takes orders for the whole project. A delta import picks up everything that sold during the build, immediately before DNS moves. Planned downtime at cutover is zero.
It gets rebuilt. Feeds built on Volusion URL and export formats break at cutover, and because they fail quietly rather than loudly, a shopping channel can go dead for weeks before anyone notices. We rebuild against the Shopify catalogue and confirm the feed is flowing before the domain moves.
No, and be careful with any page that says Shopify URLs are customisable. You control the handle at the end of the address. You cannot remove or rename the fixed prefixes Shopify puts in front of products, collections, pages and blog articles, and you cannot keep a .htm extension. Everything gets a redirect instead, which is why the redirect map matters more here than on most replatforms.
Not as nesting. Shopify collections are flat, so a Volusion category tree several levels deep is re expressed through navigation, tags and automated collection rules. The customer facing result can be identical. Every level still needs a redirect.
Yes, including line items, chosen options, addresses, totals, tax and status. Worth knowing that Shopify admin has no order import at all, on any plan, from any platform. Orders always go through an app or the Admin API. We reconcile the totals against your own data before anyone signs off.
Volusion customer groups and tiered pricing map to Shopify B2B companies and price lists, with customer segments for the rest. For most Volusion stores this is an upgrade rather than a like for like move, because B2B sits in the platform instead of in an add on.
No. Redirects and URL mapping are part of the migration here, including the mapping layer for the old query string addresses. It is worth asking anyone else the same question, because the large automated tools price 301 redirects and SEO URL migration as separate paid options.
Expect a dip of roughly five to fifteen percent for two to four weeks while Google reprocesses the redirects, then recovery. If traffic has not recovered by week eight the redirect map has gaps, and that is fixable. Permanent loss comes from missing redirects, not from changing platform. On Volusion the usual cause of a gap is mapping one URL generation and forgetting the other.
No. Volusion storefronts are ASP templates with Volusion specific tags, and Shopify themes are Liquid. There is no converter. The front end is a rebuild on every replatform. You can have it rebuilt to look the same, given a facelift, or redesigned, and we quote all three inside the migration.
Yes. A named project manager runs the migration, chairs the weekly call and is on the launch. They are the same person for the thirty days after launch. You are not passed between a salesperson, a migration operator and a support inbox.
Our Shopify Partner Directory listing carries a 5.0 rating across 567 reviews and we have been a Shopify Partner since October 2021. That page is public and we did not write it, so check it before you speak to us. Migration is listed there as one of our named specialities rather than something we also do.
Because most of them are quoting different jobs. A quote built around running an automated tool covers the records and stops there. It does not include mapping two URL generations, reconciling a gift certificate ledger, rebuilding product feeds, resolving option structures into three Shopify options, rebuilding the storefront, or reconnecting the systems behind it. Ask any quote which of those it includes and the range usually explains itself.
Start with the audit. If your store is winding down or you are close to selling the business, platform investment may genuinely not be worth it and we will say so. Otherwise the question is timing rather than whether, and moving while nothing is on fire is considerably cheaper than moving when something is.
Use the export and choose every column rather than the default set. The default omits custom fields, meta titles and descriptions and the product URLs, and those are precisely the columns the migration and the redirect map need. Run every export, keep the files, and do it before anything else changes. It is the cheapest insurance on the whole project.
They are downloaded and rehosted on Shopify before you cancel Volusion. This matters more than it sounds. Volusion images are served from Volusion infrastructure, so a migration that references them rather than copying them looks perfect until the day you close the account, and then the catalogue goes blank. Rehosting happens during the build, never after cancellation.
They do here, and they usually do not elsewhere. The automated tools import a refunded order as a plain paid order, which means your Shopify admin shows a balance owing on every refund you have ever issued. With fifteen years of history that is a permanent mess in your reporting. Refunds import as real refund records, and the totals reconcile against your export.
They do if someone puts them there. The automated tools generally do not carry them, so historical orders arrive with no parcel attached and your support team discovers it the first time an old customer asks. Tracking belongs on the fulfillment record and we import it there.
If your Volusion store quotes real time UPS, FedEx or USPS rates, then yes, and it decides which Shopify plan you need, because carrier calculated shipping is not available on every plan. This is an audit question. Answering it after the plan is chosen is how stores find a capability missing during checkout testing.
Wholesale tiers come out of the customer export and become either Shopify B2B companies with price lists and payment terms, or tagged customers with automatic discounts, depending on how many accounts you have and whether they need net terms. Tax exempt accounts are flagged in the export and set as tax exempt on Shopify with their certificate details on the customer record. Nobody loses their pricing at launch.
Volusion models option combinations as child products that belong to a parent. Those children become Shopify variants, and any price or weight differences applied to an option are resolved so the customer pays what they paid before. Products built from more than three option types, or that multiply past Shopify limits, are restructured in the audit rather than discovered mid import.
Checked against the source
We read the competing Volusion migration pages while writing this one. These are the claims that did not survive a check against the record.
Jan 2021
Page after page leads with a 2020 Chapter 11 filing as the reason to leave. Volusion filed in July 2020 and emerged in January 2021 after restructuring. Leading with it in 2026 is a scare tactic, and it is the weakest argument available when the real ones are this strong.
Newfold
Volusion is now owned by Newfold Digital, the group behind Bluehost, HostGator and Network Solutions. That gives the platform more corporate backing today than it had in 2020, which is the opposite of what a page built on platform risk wants you to know. One competitor page dated August 2026 omits it entirely.
2019
The card skimming breach of Volusion cloud infrastructure affected thousands of storefronts and is the event that actually preceded the restructuring. It is more relevant to a merchant than the filing that followed it, and it is barely mentioned anywhere.
One
Every competing page promises a full 301 map and then describes a single set of URLs. Volusion has been redirecting its own old query string addresses to newer paths for years, so a decade old store usually has both in the index and needs two different techniques.
500 or 2,000
One agency page claims more than 2,000 stores migrated in one paragraph and 500 successful migrations a few paragraphs later. The same page lists an immense app store as a Volusion advantage, while another page we read counts Volusion apps in the low twenties. It also gives Volusion a hundred variation limit, which is a retired Shopify limit, not a Volusion one.
Start here
Send us your store address and we will crawl it, tell you which URL generations are indexed, what moves, what needs rebuilding and what it costs. No obligation and no pressure. If the timing is wrong for you we will say so instead.
Our Volusion to Shopify migration service covers the catalogue, the options rebuilt as variants, the customers, the order history, the gift certificate balances, the product feeds, and both generations of URL. You keep trading on Volusion until the day we cut over.
