Loading…
Your Full-Service Digital Agency & AI Strategy Partner
Real strategists. Real AI tools. Real growth. — 1Digital® since 2012
Workspace by 1Digital® — the agency platform we built. Coming to select agencies. Join the early-access list →
Volusion → BigCommerce Replatform
Replatform from Volusion to BigCommerce while the current API surface is still available — extracting gift-card and store-credit balances the standard export omits, projecting the Options system into variants and Product Modifiers, rewriting the .asp / query-string URL surface into clean BigCommerce 301s, and formalizing wholesale in B2B Edition Price Lists. 200+ migrations completed on a documented no-data-loss cutover playbook with rollback paths.
Trusted by 400+ Brands · Certified Partners
Of results, scale, and quality at the enterprise level.
Specialists across SEO, AI SEO, PPC, design, dev, and strategy.
US core team for clear communication; vetted global specialists for international client work.
Rated 4.9/5 across 941+ verified client reviews.
Reviewed by the 1Digital® Migration TeamLast updated:
TL;DR
1Digital® migrates merchants off Volusion onto BigCommerce — Stencil themes, Catalyst headless, B2B Edition, and Open Checkout. Volusion's narrowing API surface makes proactive extraction safer than reactive: gift cards and store credit are pulled via API (the export omits them), the .asp / query-string URL surface is rewritten to clean BigCommerce 301s, Customer Tiers become B2B Edition Price Lists, and the schema graph is rebuilt — usually a net SEO upgrade.
Related: All platform migrations · Volusion → Shopify Plus · BigCommerce Experts · BigCommerce Developer · Data Migration
Why Replatform Now
Volusion has run on diminishing engineering investment for years — a shrinking partner ecosystem, a stagnant theme engine, and an API surface that has been narrowing rather than expanding. There is no single end-of-life date; the risk is gradual erosion of extraction tooling and integrations. Migrating proactively means a controlled parallel build instead of a forced, time-boxed scramble.
Volusion's standard CSV/admin export caps row counts and omits gift-card balances, store-credit ledgers, abandoned-cart history, the full historical URL inventory, and several custom-field types. What looks like a complete export is partial — the gaps are exactly the records customers expect to survive a move.
Gift-card codes, redemption history, and store-credit ledgers are held in Volusion-internal structures the export never surfaces. On BigCommerce these become native gift cards plus Customer Group store-credit balances — but only if they are extracted via the API and targeted queries first, with a balance-by-balance audit trail.
Volusion's product Options model (option categories, swatches, price/weight deltas) does not map cleanly to a single target shape. On BigCommerce it splits between true variants and Product Modifiers depending on whether the option drives SKU/price or is presentational.
Most Volusion B2B merchants run wholesale on Customer Tiers plus email and spreadsheets — there is no real quote-to-cash. BigCommerce B2B Edition (Companies, Buyer Roles, Quoting, Shopping Lists, Invoice Portal, Net Terms) replaces that workflow natively, which is usually an operational upgrade as much as a migration.
BigCommerce Open Checkout is a forkable React + TypeScript checkout with zero platform transaction fees on any gateway, and Enterprise Multi-Storefront runs one catalog across multiple branded storefronts without parallel admin instances — neither has a Volusion equivalent.
What We Migrate
Field-level mapping with referential integrity — gift cards, store credit, and Customer Tiers all carry across with audit trails intact, including the records the standard export silently drops.
Products, Volusion Options (option categories + swatches), Bundles, Kits, downloadable products → BigCommerce products + variants + custom fields + Product Modifiers. Asset library re-hosted on the BigCommerce CDN with image-URL rewrites inside product descriptions.
Customer profiles, address books, marketing consent, Volusion Customer Tiers (wholesale/volume pricing groups) → BigCommerce customers + Customer Groups, or B2B Edition Company Accounts where wholesale is involved. Passwords reset-on-first-login.
Full order history, line items, fulfillments, refunds, returns, and abandoned carts → BigCommerce orders with ledger continuity for revenue reporting, LTV, and support look-back.
Gift-card codes, balances, redemption history → BigCommerce native gift cards (customer-facing codes preserved so existing cards keep working). Store-credit ledgers → Customer Group credit balances, validated balance-by-balance before cutover.
Volusion Customer Tier pricing → BigCommerce B2B Edition Price Lists with Customer Group assignment. Off-platform quote workflows → B2B Edition Quoting; net terms → B2B Edition Net Terms + Invoice Portal.
Volusion Articles (the built-in blog), CMS pages, and custom HTML pages → BigCommerce Pages + Page Builder + blog. Editorial content preserved with publish date; slugs 301'd to BigCommerce equivalents.
Full URL inventory — /ProductDetails.asp?ID=, /<slug>-p/<code>.htm, category-code URLs, Article URLs, and accumulated vanity paths — projected onto a page-level 301 map with per-URL title/meta/canonical carryover and a rebuilt schema graph.
Volusion native reviews plus Yotpo / Trustpilot / Bazaarvoice → Yotpo / Trustpilot / Bazaarvoice / Okendo for BigCommerce with star ratings, verified-buyer flags, and AggregateRating schema continuity for AI-engine citations.
How We Migrate
Inventory every native feature, third-party connector, payment gateway, shipping rule, tax setup, Customer Tier, gift-card configuration, and Article/CMS structure, then map each to a BigCommerce equivalent. Critically, identify which records the standard export does NOT contain — this determines the extraction plan.
Catalog count, Options/Bundle/Kit complexity, customer/order volume, gift-card and store-credit ledger size, Article count, and the full historical URL inventory including /ProductDetails.asp?ID=, category-code, and vanity paths. Produces data-parity targets and a URL-mapping spreadsheet.
Volusion /ProductDetails.asp?ID=, /<slug>-p/<code>.htm, category-code, and Article URLs → BigCommerce /<category>/<product>/, /<category>/, /<page-slug>/ with 301 rules, explicit retire-vs-preserve decisions on discontinued products, canonical strategy, and a rebuilt schema graph (typically a net SEO upgrade since Volusion's native schema is thin).
Stencil theme or Catalyst storefront. Iterative loads with parity reports: catalog, Customer Tiers → Price Lists, orders, gift cards + store credit validated balance-by-balance, reviews. Apps configured against staging; Open Checkout customizations forked and QA'd.
Freeze Volusion writes (admin saves off, cart disabled), sync the final delta (orders, customers, gift-card redemptions, inventory) via Volusion API → BigCommerce API, flip DNS at low TTL, and validate Open Checkout, payments, shipping, tax, search, gift-card redemption, GA4, Consent Mode v2, and pixels live.
30+ days of crawl-error triage (301 verification is critical given the dramatic .asp → clean-URL change), Search Console change-of-address, ranking and AI-citation monitoring, Core Web Vitals tracking, conversion-rate watch, gift-card redemption validation, and an edge-case fix sprint.
Feature Mapping
Most Volusion native features have a BigCommerce equivalent that is actively maintained and more extensible — typically a platform upgrade in addition to a continuity step.
| Volusion | BigCommerce Equivalent |
|---|---|
| Volusion native checkout | BigCommerce Open Checkout (forkable React + TypeScript) with Apple Pay / Google Pay / PayPal / Amazon Pay accelerators |
| Volusion native payment gateways | BigCommerce native gateways (Stripe, Braintree, Adyen, PayPal, Worldpay, Authorize.net, Square) — zero BC transaction fees on any gateway |
| Volusion native shipping rules | BigCommerce native shipping + ShipperHQ for advanced rules + ShipStation for fulfillment |
| Volusion native reviews | Yotpo, Trustpilot, Bazaarvoice, or Okendo for BigCommerce |
| Volusion Articles (built-in blog) | BigCommerce Blog with full article history and SEO 301s |
| Volusion native tax (legacy table-based) | BigCommerce Tax (TaxJar native) or Avalara AvaTax for BigCommerce |
| Volusion Customer Tiers (wholesale pricing) | BigCommerce B2B Edition Price Lists with Customer Group assignment |
| Mailchimp / Constant Contact for Volusion | Klaviyo for BigCommerce (deeper segmentation and event coverage) |
| Volusion gift cards | BigCommerce native gift cards with balance + redemption history preserved |
| Volusion custom HTML / template engine | BigCommerce Stencil theme (Handlebars + SCSS) or Catalyst (Next.js + GraphQL) headless |
| QuickBooks / NetSuite via Volusion connectors | BigCommerce QuickBooks app, Celigo, Boomi, or MuleSoft for ERP |
The Technical Reality
The single most damaging assumption on a Volusion migration is that the admin export is the data. It is not. Volusion's standard product/customer/order export caps row counts and silently omits gift-card balances, store-credit ledgers, abandoned-cart history, the full historical URL inventory, and several custom-field types. A merchant who exports CSVs and hands them to a generic importer will go live missing the records customers care about most.
Our framework treats extraction as an integration project: we pull against whichever Volusion API surface is live for the account, supplement with targeted queries for the proprietary tables (gift cards, store credit), and use CSV only as a fallback for fields the API genuinely does not expose. Because Volusion's tooling has narrowed over time rather than expanded, the practical takeaway is that a proactive extraction while the current API surface is still available is materially lower-risk than waiting — the data does not get easier to retrieve later.
Volusion is an ASP-era platform: product pages are commonly /ProductDetails.asp?ID=<id> or the SEO-friendly /<slug>-p/<code>.htm, categories are code-based (/<slug>-c/<code>.htm), Articles have their own path scheme, and stores accumulate years of vanity URLs and discontinued-product paths. BigCommerce uses clean /<category>/<product>/ trailing-slash URLs. This is one of the largest URL-pattern shifts of any common migration route — query-string and .asp/.htm paths to a completely different structure.
We export the complete historical URL inventory (including the query-string product IDs, both .htm slug forms, category codes, Article URLs, and vanity paths), then build a page-level 301 map with explicit per-URL decisions: which discontinued products 301 to a parent category, which vanity URLs are retired, and how Article paths fold into the BigCommerce blog. Post-launch we verify every redirect with Screaming Frog and Search Console coverage. Because Volusion's native schema is typically thin or absent, the rebuilt Product/Breadcrumb/Organization graph is usually a measurable SEO upgrade on top of the continuity work.
Volusion Customer Tiers (named wholesale/volume pricing groups, sometimes with tier-specific visibility and shipping) map to BigCommerce B2B Edition Price Lists with Customer Group assignment. The migration is frequently the moment a merchant formalizes a B2B operation that was running on spreadsheets and email: B2B Edition's Companies, Quoting, Shopping Lists, and Invoice Portal give a structured quote-to-cash flow Volusion never offered.
Gift cards and store credit are the highest-stakes data on this route because the balances are money owed to customers. We extract codes, balances, and redemption history via the API and targeted queries, load them as BigCommerce native gift cards (preserving the customer-facing code so physical/emailed cards keep working) and Customer Group credit balances, and validate every balance individually against the source ledger before cutover. A parity report — not a spot check — is the sign-off artifact, because a single missed balance is a support escalation and a trust problem on day one.
SEO Equity Protection
Volusion → BigCommerce has one of the largest URL-pattern changes of any common migration route. The .asp / query-string 301 map is non-negotiable, and a missed gift-card balance is a day-one trust problem.
Timeline & Engagement
Standard B2C
Catalog under 5K SKUs, Stencil theme, no gift-card ledger, common app stack (Klaviyo, Yotpo, ShipStation), 2 payment gateways, single storefront.
B2B / Gift Cards / Mid-complexity
Customer Tiers → B2B Edition Price Lists, gift-card + store-credit migration with balance-by-balance parity validation, ERP / QuickBooks, BC Tax / Avalara, Open Checkout customization.
Catalyst / Multi-Storefront / Enterprise
Catalyst (Next.js) storefront, Multi-Storefront for portfolio brands, full B2B Edition rollout, large catalog (50K+ SKUs), heavy legacy .asp URL inventory cleanup.
Engagements start at $185/hour. Fixed-fee proposal after discovery — typically $20K (simple) to $125K+ (enterprise Catalyst with B2B Edition + ERP).
Request a Proposal
Share your catalog scale, Customer Tier setup, gift-card and store-credit ledger size, ERP / QuickBooks connector, payment gateways, and what is pushing you to move (sunset concerns, API narrowing, feature gaps, scale). A senior strategist responds within one business day with a pricing band and a draft migration roadmap.
FAQ
Free migration audit. Fixed-fee proposal. Gift-card and store-credit balances validated balance-by-balance. 200+ migrations run on a documented no-data-loss cutover playbook.
