Platform migration

Moving from Volusion to Shopify

Your product pages live at addresses like /ProductDetails.asp?ProductCode=ABC123. Shopify’s redirect tool cannot redirect a URL with a query string in it. That one sentence decides whether your search rankings survive the move, and most migration quotes never mention it.

Check your store’s URLs All platforms

Direction, not urgency

Volusion is not dying. It is thinning.

It is worth being straight about this, because a lot of pages on this subject open by telling you the platform is about to collapse. It is not. Volusion emerged from its 2020 restructuring, the platform still runs, and if your store is quietly taking orders every day then nothing is on fire.

What has changed is the ecosystem around it. As of Q3 2026, Store Leads counts roughly 3,260 live Volusion storefronts, down about 19% year over year¹. A platform shrinking at that rate loses the things that surround a platform before it loses the platform: the app developers, the agencies who know it, the Stack Overflow answer for your exact problem, the person you can hire when something breaks at 9pm on a Friday.

That is the honest case for moving. Not urgency. Direction.

What usually forces the decision

In practice it is rarely the feature set. It is the ceiling. Volusion’s plans are capped by annual sales volume rather than by product count, and crossing a cap moves you up a tier automatically. A store that is growing eventually finds itself paying meaningfully more each year for a platform whose capability has not moved in the same period. That is usually the month the comparison stops being theoretical.

The line item most quotes omit

The URL problem nobody warns you about

Every migration checklist covers products, customers and orders. Those are the easy parts. The part that quietly costs stores their organic traffic is the URLs, and Volusion has a specific problem here that most platforms do not.

You probably have two sets of URLs, not one

Volusion’s original product URL is a query string:

/ProductDetails.asp?ProductCode=ABC123

At some point you were probably told to switch on Search Engine Friendly URLs, which produces the tidier form:

/product-name_p/ABC123.htm

There is also a third form. When Volusion moved its own backend off ASP, it began answering the .asp addresses with a redirect to a .php twin:

/ProductDetails.asp?ProductCode=ABC123
  -> 307 /ProductDetails.php?ProductCode=ABC123
  -> 200 /product-name_p/ABC123.htm

That is a real chain on a real store, checked in September 2026. Both query-string forms answer, both are indexable, and both need mapping. So the count is not one legacy URL per product. It is two.

Here is the trap. Switching on SEF URLs adds the clean version. It does not retire the old one. The .aspaddresses stay reachable, stay in Google’s index, and keep whatever inbound links they have collected over the years. Most Volusion stores that have been running for a while are carrying both sets, and the owner believes they only have one.

Check this yourself, right now

Search Google for site:yourdomain.com inurl:asp

Every result is a URL that has to be redirected by hand. If that search returns nothing, your migration just got considerably simpler and you should say so when you ask anyone for a quote.

Or skip the searching: the checker at the bottom of this page reads your sitemap and tests the legacy URLs on your own store.

Why the destination platform cannot fix it for you

Shopify’s URL redirect table matches on the path and ignores everything after the question mark. So a redirect entered for /ProductDetails.asp?ProductCode=ABC123 is stored, in effect, as a redirect for /ProductDetails.asp— and the next rule you add overwrites it. Import a thousand product redirects and you end up with one, pointing your entire indexed catalogue at a single page.

This is not a Shopify defect so much as a mismatch. Hosted platforms model redirects as page-to-page moves, because that is what almost every other platform needs. Volusion is one of the few still identifying products by query parameter.

What has to happen instead

The redirects have to be handled above the store — at the CDN or in middleware that can read the query string, parse the product code out of it, and issue a real 301 to the new product URL. On Shopify that means Cloudflare or an equivalent layer in front of the domain. On WooCommerce it is server rules, which is simpler because you control the server.

Either way it is a different piece of work from importing a spreadsheet of redirects, it needs the full indexed URL list before anyone can scope it, and it is the line item most commonly missing from a migration quote. If you are comparing proposals, that is the question to ask.

How many are you carrying? The checker reads your sitemap and tests these URLs on your own store. A few seconds, and nothing but the domain.

Check your store’s URLs

Checkable in your own admin

What transfers, what needs work, what is gone

Checkable against your own admin before you talk to anyone.

Data	Verdict	Detail
Products and SKUs	Transfers cleanly	Core fields — name, SKU, price, weight, stock, description — come out of the CSV export intact and map to any modern platform.
Product options and variants	Needs real work	Volusion stores options in separate relational tables rather than on the product row. Generic migration apps routinely flatten a shirt with three colours and four sizes into twelve unrelated products, or drop the per-variant prices. This is the part that needs scripting and the part worth checking line by line afterwards.
Customer records	Transfers cleanly	Names, email addresses and stored addresses export normally.
Customer passwords	Does not come across	Volusion hashes passwords with legacy algorithms that no current platform will accept. There is no migration path and no workaround. Every customer resets their password, so the launch email has to tell them that before they discover it at checkout.
Order history	Needs real work	Exportable, but the line-item structure rarely matches the destination's import format without reshaping. Decide early whether you need full order history in the new platform or whether an archived export satisfies your accountant.
Discount codes	Transfers cleanly	Coupon codes carry across with their rate and creation date. One of the few things on this list that genuinely just works.
Gift card balances	Does not come across	The one to check before you sign anything, and the one most migration plans forget. An outstanding balance is money you owe a customer, so this is a liability on your books rather than a data-tidiness problem: the codes and their remaining values have to be reconciled by hand and reissued on the new platform, and the arithmetic has to match. If you have gift cards in circulation, settle how they will be honoured before the migration starts, not after somebody tries to spend one.
Product reviews	Needs real work	Extractable from Volusion, but most destinations keep reviews in an app rather than the core catalogue, so where they land depends on which review app you choose. Worth deciding before launch, not after.
Theme and template	Does not come across	Volusion templates are ASP and do not port anywhere. The storefront is rebuilt. This is usually the least painful loss on the list.
URLs and rankings	Needs real work	The whole ballgame. See below — this is the section to read if you read only one.

The one genuine misfit

Volusion to Shopify, specifically

Most Volusion stores that move end up on Shopify, so it is worth being concrete about the one place the two platforms genuinely do not fit together. It is not the thing most guides warn you about.

The three-option ceiling

Nearly every Volusion-to-Shopify guide still warns that Shopify caps products at 100 variants. That stopped being true on 15 October 2025, when Shopify raised the limit to 2,048 variants for every merchant on every plan². If a page is still citing 100, it has not been touched in a year.

What did not change is the limit on options: three per product, enforced as a per-shop resource limit rather than a published constant³, and that is the one that actually stops a Volusion catalogue. Volusion keeps options in its own relational tables with no such ceiling, so a product sold by colour, size, material and length is four options and does not fit Shopify at any variant count. The variant number is a red herring. Count your options instead.

Find your worst product before you choose a platform. If anything in your catalogue needs four or more options, that has to be solved by restructuring the product, by an app, or by choosing a different destination — and it is far cheaper to know that now than during a build.

How long it takes

The data extraction is fast on any store. What sets the timeline is design, option mapping and the redirect work, so it scales with complexity rather than with product count alone.

Small catalogue, simple options — 2 to 3 weeks.: A few hundred products, one or two options each, no B2B pricing.
Large catalogue or heavy options — 4 to 8 weeks.: Thousands of products, option sets that need restructuring, or a URL inventory in the tens of thousands.

Anyone quoting you a fixed timeline before seeing your option structure and your URL count is quoting the easy version.

What it costs

A store move sits in the $5,000 to $15,000 Shopify range. Where you land inside it is mostly catalogue size.

Under 500 products: $5,000 – $8,000
500 – 5,000 products: $8,000 – $15,000
Over 5,000 products: Quoted after the URL inventory

Redirect mapping is quoted separately, because it scales with how many URLs you are carrying rather than how many products you sell.

Find out which number you are dealing with

Order matters more than duration

The order the work happens in

The sequence matters more than the timeline. Doing these out of order is what produces a migration that technically completed and still lost half its traffic.

Pull the indexed URL list first. Search Console and a crawl of the live store, before anything is built. This is the document the whole redirect map is derived from, and it cannot be reconstructed after the old store is switched off.
Export and inspect the catalogue. Specifically the option and variant tables, which is where automated tools fail quietly.
Build the new store and import. Products, customers, then whatever was decided about order history.
Write the redirect map against the URL list, including both the .asp and the .htm forms, and test it against real indexed URLs rather than a sample.
Export the full DNS zone and drop the TTLs 24 to 48 hours before the switch. Every record, not just the web ones — losing your MX records takes your email down with no warning and no queue. See below.
Launch, then watch coverage rather than traffic. Search Console’s crawl reports tell you whether the redirects are being followed weeks before the traffic numbers settle enough to mean anything.
Tell customers about the password reset in the launch email, because they cannot carry their passwords across and finding that out at checkout costs you the order.

After the launch, not before

The 48 hours nobody plans for

Migration guides end at launch. The damage happens after it, in the window where the domain is pointing at two places at once.

DNS does not switch. It leaks.

Pointing your domain at the new store does not move everyone at once. Resolvers hold the old answer until their cached copy expires, and most of them do that correctly: measuring more than 27,000 resolvers across 9,500 networks, one study found 92.5% honoured a 60-minute TTL exactly⁴. The problem is the minority that does not, and how you make it larger.

Two things follow, and neither is theoretical. Orders keep landing on the old store after you have stopped watching it, so both platforms need checking for a full two days. And customers ring up about an order placed ten minutes ago that does not exist in the system you are looking at — which reads to them as a company that has lost their money.

Here is the part that is genuinely counter-intuitive. The share of resolvers that ignore your TTL and keep serving the old answer rises as you shorten it⁴.

60 minutes

0.31%

30 minutes

2.53%

15 minutes

2.87%

5 minutes

6.53%

1 minute

8.74%

Resolvers serving a stale answer past the published TTL. Some DNS software applies a minimum TTL floor regardless of what you set⁴.

So you can shorten the window but not close it, and shortening it is still the right move — a five-minute TTL loses you 6.5% of resolvers, where an hour-long one would have kept nearly all of them but for a much longer window. Drop it to five minutes 24 to 48 hours before the switch, not on the day; the old, long TTL has to expire before the short one takes effect. Then plan for a tail rather than a clean cutover.

The one that actually costs money: your email

This is the mistake worth reading twice. Moving your domain to new nameservers moves the source of truth for every DNS record, not just the ones about your website. Anything that existed only on the old nameservers and was not copied across simply stops existing.

That includes your MX records, which are what tell the world where to deliver your email. And mail does not behave like a web request here. It does not queue and retry until you notice. It fails immediately. Every order confirmation, supplier message and customer enquiry sent during that window bounces and is gone.

So before anyone touches a nameserver, export the current zone in full — A, AAAA, CNAME, MX, and the TXTrecords carrying SPF, DKIM and DMARC — recreate all of it at the new provider, and confirm it resolves before the switch rather than after. If your email is on the same domain as your store, and on a Volusion store it usually is, this is the single highest-consequence step in the entire migration.

What people ask first

Questions worth asking

No, and this is the single most common wrong assumption about a Volusion migration. Turning on SEF URLs adds the clean form; it does not retire the old one. The /ProductDetails.asp?ProductCode= versions stay reachable, stay indexed, and keep whatever inbound links they have accumulated. Check it yourself in about a minute: search Google for site:yourdomain.com inurl:asp and see what comes back. Most stores that have been on Volusion for more than a few years still have live .asp results.

Not for the product URLs. Shopify's URL redirect table matches on path and ignores everything after the question mark, so a rule for /ProductDetails.asp?ProductCode=ABC123 collapses into a rule for /ProductDetails.asp and every product you own resolves to the same destination. The redirects have to be handled above the platform — at the CDN or in middleware that reads the query string — which is a different piece of work from importing a CSV of redirects, and it is the piece most migration quotes leave out.

Yes, and nothing about your live store changes until you choose. A Shopify store is built and populated on its own myshopify.com address, so you can browse the whole thing, place test orders and check your products for as long as you need while Volusion carries on taking real orders. The switch is a separate, deliberate step: pointing your domain. Nobody should be asking you to commit before you have walked through the finished store.

Any migration costs something for a few weeks while search engines re-crawl and re-evaluate. What decides whether that is a dip or a cliff is almost entirely redirect coverage. Anyone who quotes you a guaranteed retention percentage before looking at your URL inventory is guessing. The honest sequence is to pull the full list of indexed URLs first, map every one of them, and only then talk about expected impact.

There is no announced shutdown, and stores run on it every day. The case for moving is not that the platform is about to disappear. It is that the ecosystem around it has thinned — fewer apps, fewer developers who know it, fewer people to hire when something breaks — and that thinning compounds. As of Q3 2026, Store Leads counts about 3,260 live Volusion storefronts, down roughly 19% year over year. That is the real argument: not urgency, but direction.

Shopify for most, because the checkout and the app ecosystem solve the largest number of accumulated problems in one move. BigCommerce if avoiding per-transaction fees on a hosted platform matters more than app selection. WooCommerce if you are already invested in WordPress and have someone to maintain a self-hosted stack. The redirect work described on this page is the same in all three cases, because the problem is on the Volusion side.

Sources

Two vendor pages, one independent tracker and one peer-reviewed measurement paper. The redirect chains in the URL section were checked by hand rather than cited, because no one publishes them.

1
The state of Volusion — Store Leads. Live storefront counts, tracked independently of any vendor. Q3 2026.
2
We’ve increased the product variant limit to 2048 — Shopify. The change, its date, and the 100-variant limit it replaced. 15 October 2025.
3
Admin API: the Product object — Shopify. That options remain capped per shop, by Shop.resourceLimits.maxProductOptions. Current documentation.
4
TTL Violation of DNS Resolvers in the Wild — Bhowmick, Ashiq, Deccio & Chung. Peer-reviewed measurement of 27,000+ resolvers across 9,500 networks. Passive and Active Measurement conference, 2023.

Shopify has said it intends to raise the three-option ceiling. It had not when this was checked in September 2026, and if it has by the time you read this, the option argument above weakens and the migration gets easier — check before you plan around it.

Your store, not a general claim

Check your own store

Everything above is a general claim about Volusion. This tests it on your store: it reads your sitemap, then requests the legacy URL for a few of your products and reports where each one lands. Takes a few seconds, asks for nothing but the domain.

When you want the map, not just the number

The checker tells you how many addresses you are carrying. The work is mapping every one of them to its replacement and proving the redirects fire before you switch the old store off. That starts with your Search Console data and a full crawl, which is the first thing I would do and the thing worth comparing between quotes.

Talk through your migration (303) 815-0215

Redirect chains verified by hand against live Volusion stores in September 2026. Everything else is sourced below.