Skip to main content
Migration · Custom cart → Shopify

Legacy and Custom Cart to Shopify Migration

A legacy or custom cart to Shopify migration moves a homegrown, heavily modified or long-unsupported ecommerce system to Shopify. Kooks, Vosges Haut-Chocolat, eVacuumStore, Jimmy Beans Wool and Vermont Woods Studios are among the stores that left custom-built sites or carts for Shopify with Uncap.

A migration typically takes 10 to 16 weeks, and Uncap's median cutover is around 14 weeks.

Last updated

From Custom cart
In this article Talk to our experts

Someone built your store. It might have been an agency in 2014, or a developer who was on staff and is not any more. It runs. It takes orders. Nobody is entirely sure how.

There is no vendor to call, no version number, no support contract and no upgrade path. When something breaks you find whoever is available and they read the code until they work it out. That is not a criticism of the system, which has probably paid for itself many times over. It is a description of where you are.

Moving that to Shopify is a different project from moving off a named platform, and most of what you will read about it is written as though it were the same.

How to migrate a legacy system to Shopify, step by step

To migrate a legacy system to Shopify, start with a paid discovery that establishes what the old system holds, recovers the business rules buried in its code and inventories the URLs that rank, then rebuild accounts and integrations on Shopify, migrate the data and cut over with the old store still running. In order:

  1. Start with a paid discovery. An undocumented system cannot be priced honestly from the outside. Uncap plans the move with Uncap Blueprint, a $7,500 fixed-price plan delivered in four weeks and credited toward implementation. Once the specification exists, a migration from another platform typically takes 10 to 16 weeks, and Uncap's median cutover is around 14 weeks. A custom cart's own date comes out of discovery.
  2. Establish what exists. Find the database and what access still works, choose the extraction route (direct SQL against a copy, or an authenticated crawl when database access left with the developer), and document the hosting, email and DNS.
  3. Recover the business rules. Pricing tiers, minimums, case packs and approval rules in a custom build usually live in code. Read the code where it is legible, interview the people who take orders, and check order history for behavior the data cannot otherwise explain.
  4. Build the URL inventory. Merge server access logs, the Google Search Console export, any sitemap and a full crawl, rank the URLs by value, and map them to Shopify's fixed paths with 301 redirects.
  5. Rebuild the customer structure. Shopify models B2B as companies, company locations and contacts. Customer-specific pricing moves into catalogs, and more than 3 active catalogs across your B2B markets needs Shopify Plus.
  6. Map every integration. List the ERP, logistics, CRM, tax, EDI and punchout connections, plus the scheduled jobs and scripts, and rebuild them with the ERP as the system of record.
  7. Migrate the data. Extract products, variants, customers, pricing and the order history you decide to keep from the database, and load them in the order Shopify gives: “Import your products first, then your customers, and then any historical orders.”
  8. Cut over in parallel. Run the new store in a parallel environment, then go live with a DNS change and a rollback plan in place.

The hard part is the part everyone skips

A platform migration and a custom cart migration are different projects

Producing a correct, complete export from a database nobody documented is the migration.

Factor
Moving off a named platform
Moving off a custom cart
Data
A known data model and a documented export.
Extracted from the database, or by an authenticated crawl where access has been lost.
Business rules
Configuration you read out.
Code, recovered from the application, the people who take orders and the order history.
URL inventory
A route table to read.
Assembled from server logs, Search Console, crawls and archive snapshots.
Integrations
Reconnected to the new platform.
Rebuilt, with the ERP taking the central role the website used to hold.
Pricing the project
Scoped and quoted from the outside.
A paid discovery phase first, then scoped like any other.

Search for this and the first result will offer to migrate your custom cart from a CSV file.

Read that again. The entire premise is that you already have a clean export of your products, customers and orders, correctly structured, ready to upload. If you had that, you would not be reading this page. Producing a correct, complete export from a database nobody documented is the migration. Everything after it is routine.

The same is true of the other promises. Every migration page in this category lists 301 redirects as a feature. None of them explains how you build a URL inventory when there is no route table to read, no sitemap that reflects reality and no developer who remembers why the category pages have three different URL patterns.

So this page is about the part that is actually hard.

Finding out what you have

The first phase is not building anything. It is establishing what exists.

The database. Where it lives, what access still works, and what the tables actually mean. A custom cart has no entity relationship diagram, so product, variant, price, customer and order structures get identified by reading the schema and then testing assumptions against the live site. A table called prod_opts might be variants, or might be a discontinued feature from 2017 that still has rows in it.

The extraction route. Direct SQL against a copy is the clean version. Where database access has been lost with the developer, an authenticated crawl of the live site becomes the fallback, because a page that renders a price to a logged in customer is evidence of that price whether or not you can reach the table behind it.

The hosting. Frequently the least documented thing of all. Who has the account, what the server actually runs, whether anything else is running on it, and what happens to email and DNS at cutover.

None of this is glamorous and all of it decides the schedule.

The business logic is not in the database

This is the part that catches people out, and it is why a custom cart migration cannot be scoped from a data export alone.

In a packaged platform, pricing rules are configuration. You read them out. In a custom build, they are code. The rule that a particular account gets a different price above a certain quantity, or that a product cannot be ordered in fewer than a case, or that orders above a value need internal approval, is very often an if statement written years ago by someone responding to a phone call.

None of it exports. It gets recovered three ways: by reading the application code where it is legible, by interviewing the people who take the orders, and by analyzing order history for behavior the data cannot otherwise explain. A customer who has never once ordered fewer than twelve of something is telling you about a rule.

We budget for this explicitly, because the alternative is discovering it after launch from a customer who has just been quoted the wrong price.

Building a URL inventory when nobody wrote the routes down

Your rankings live in URLs you cannot list. That is the SEO problem in one sentence.

The inventory gets assembled from whatever still exists. Server access logs are the best source, because they show what was actually requested rather than what someone intended to publish. Google Search Console export shows what earns impressions. Any sitemap is a starting point rather than a truth. A full crawl finds what is linked. Archive snapshots find what used to be linked and may still hold links from other sites.

Those sources get merged, deduplicated and ranked by value, and then mapped to Shopify's fixed path structure. Shopify lists /products, /collections and /collections/all as fixed Shopify paths, so some patterns map cleanly and some need a decision about what matters. Making that decision deliberately, against traffic and link data, is the difference between a migration that holds its rankings and one that explains a drop afterward.

Where your customers land in Shopify

Shopify models B2B as companies, with company locations underneath them and contacts attached. If your custom cart has a flat customer table with a wholesale flag and some pricing columns, that structure has to be rebuilt rather than mapped across.

Most of the real work is in the shapes that do not transfer cleanly. A buying group with several ship-to sites. A parent account whose branches each have their own terms. A contact who buys for two different companies. Those all exist in Shopify, and they exist differently from how a bespoke system almost certainly did them.

Customer-specific pricing moves into catalogs, and there is a plan constraint worth knowing before anyone designs around it. Shopify's own documentation states: "On the Basic, Grow, and Advanced plans, you can assign up to 3 active catalogs across all your B2B markets. The Shopify Plus plan offers an unlimited number of catalogs and direct assignment to companies and locations."

If you have forty accounts on negotiated pricing, that sentence decides your plan.

What breaks that you did not know was connected

Ask what your custom cart integrates with and you will get a short answer. Then the migration starts and the list grows.

The common ones are an ERP or accounting system, a warehouse or third party logistics provider, a CRM, a tax engine, carrier rating, EDI to larger customers, and punchout to procurement systems. The awkward ones are the scripts. A nightly job that writes a file somewhere. A webhook nobody remembers configuring. A report that finance receives every Monday and would notice immediately if it stopped.

On a custom build the storefront is frequently the integration hub rather than a participant in it, which means those flows do not simply reconnect to Shopify. They get rebuilt, usually with the ERP taking the central role the website used to hold. Mapping every flow before cutover is not optional, and it is the part most likely to be underestimated.

Why we will not give you a fixed price before discovery

From an undocumented system to a scoped migration

After discovery, the migration is no longer undocumented.

1
Discovery
Find out what you have

Establish what exists before building anything.

  • The database and what the tables mean
  • The extraction route
  • The hosting, email and DNS
2
Blueprint
Write the specification

A paid discovery engagement that is yours whether or not you build with us.

  • Business rules documented
  • URL inventory built
  • Integration flows drawn
  • A plan with a real number
3
Migration
Scoped like any other

A parallel environment and a cutover plan with a rollback.

  • Go live is a DNS change
  • 301 map from logs and search data

Every other migration we do can be scoped from the outside. A Magento project has a known data model, a documented export, a predictable extension ecosystem and a published end of life date. We can look at a Magento store and quote it.

We cannot do that here, and neither can anyone else. A fixed price quoted against an undocumented system is either padded heavily enough to cover the worst case or it is a number that will move. Both are worse for you than the honest version.

The honest version is a paid discovery phase that produces the specification. Uncap Blueprint is that engagement: the schema mapped, the business rules documented, the URL inventory built, the integration flows drawn, and a plan with a real number attached. It is yours whether or not you build with us, which is the point. If you take it elsewhere, it still works.

Uncap Blueprint is a $7,500 fixed-price plan delivered in four weeks and credited toward implementation. For scale once the specification exists: a migration from another platform typically takes 10 to 16 weeks, and Uncap's median cutover is around 14 weeks. A custom cart's own date comes out of discovery.

After discovery, the migration itself is scopeable like any other, because by then it is no longer undocumented.

What we build

What Uncap builds in a custom cart migration

Extracted from your database rather than from an export you were supposed to produce.

01 · Data

Full data migration

Products, variants, customers, pricing and order history.

02 · Rules

Business rules rebuilt

Minimums, pack sizes, account pricing and approval workflows, documented first.

03 · Accounts

B2B account structure

Companies, company locations and contacts that match how your customers buy.

04 · SEO

URL inventory and 301 map

Built from logs and search data rather than a sitemap.

05 · Integrations

Integrations rebuilt

The ERP as the system of record, including the undocumented scripts and jobs.

06 · Cutover

Parallel environment and rollback

Go live is a DNS change rather than an event.

Full data migration of products, variants, customers, pricing and order history, extracted from your database rather than from an export you were supposed to produce.

Business rules rebuilt in Shopify after being documented rather than guessed at, including minimums, pack sizes, account pricing and approval workflows.

A B2B account structure using companies, company locations and contacts that matches how your customers actually buy.

A complete URL inventory and 301 map, built from logs and search data rather than from a sitemap that may never have been accurate.

Integrations rebuilt with the ERP as the system of record, including the scripts and scheduled jobs nobody had written down.

A parallel environment and a cutover plan with a rollback, so go live is a DNS change rather than an event.

Custom-built stores Uncap has moved to Shopify

Shopify has published case studies of two Uncap clients that left custom-built sites. Kooks came off a custom-built site that, in Shopify's words, "had limited product search, poor performance metrics, and no way to serve wholesale online." Shopify reports "A 22% increase in conversion rate" and a "38% reduction in total cost of ownership (TCO)" for Kooks on Shopify, and the build is in the Kooks case study. For Vosges Haut-Chocolat, Shopify notes that "a custom website created a lot of functionality and maintenance problems" before Uncap moved the store to Shopify Plus (Vosges case study).

Clutch's summary of one review describes a project where Uncap "migrated a sleep apnea supplies retailer's 15-year-old customized shopping cart to Shopify." The client's CEO wrote:

"We thought we would see a sales drop for 1-2 months but it turned our the sales had no changes at all."

Eric Yun, CEO, RespShop.comClutch review

Five more custom-built stores are in Uncap's own case studies. eVacuumStore ran on a custom platform wired to NetSuite, with thousands of schematic pages tied to products and no standard migration connector. Uncap carried the product data across in about 50 metafields, moved the schematics into interactive parts discovery, and kept canonical URLs, redirects and diagram indexing so search visibility came with the store. Jimmy Beans Wool left a custom cart that struggled with variant-level inventory and bundling, and moved to Shopify with every customer review, loyalty point and gift card carried over. Vermont Woods Studios replaced a 12-year-old, custom-built Zen Cart site holding thousands of products, pages, categories and blogs. The Nail Superstore, a manufacturer and distributor of professional nail supplies, left a custom ASP.NET platform with Apache Solr search, and its promotional programs, from Buy X Get Y and bundle discounts to free gifts and samples, were rebuilt on Shopify Plus, along with shipping rules for hazardous materials and case-pack weights, while its collections moved with 301 redirects. E3 Spark Plugs left a custom-built platform with slow performance, complicated navigation and a hard-coded product lookup for one Shopify Plus storefront, and the migration carried product information, storefront content and SEO.

The catalog structure can be the harder part of the move. Dash Designs came to Shopify from Web Shop Manager with a catalog where vehicle year, make and model, seat position, style, fitment, material and color combine into separate SKUs. Moving that structure as it stood would have meant 20,000 to 30,000 product pages. Uncap built a custom Shopify app that sells the full matrix from a manageable set of product pages, and prepared the move with URL redirects, customer data transition planning, payment testing and launch support. The store launched in May 2026 after a DNS switchover of about 20 minutes and began receiving orders immediately.

Other platforms Uncap has moved to Shopify

Uncap has also moved clients to Shopify from other commerce platforms. Sanitaire, a BISSELL brand, moved from Oracle ATG Commerce to Shopify Plus, with separate US and Canadian storefronts and legacy product, customer and content data carried over. Baseball Card Exchange left Oracle Commerce for Shopify Plus, and about 25,000 products moved with collections, content, customer records, historical orders and email subscribers. Microfiber Wholesale, a 75-year-old family-owned cleaning-supplies business, moved from PinnacleCart to Shopify Plus with products, collections, customers, order history and content carried over, with SEO redirects preserving important URLs. Great Lakes Bio Systems moved from Drupal Commerce to Shopify with its products, customer records, order history and navigation. ScooterWorks came from AbleCommerce, and its Shopify store now runs a custom Year-Make-Model search, shoppable parts diagrams and an integration with Dydacomp, the company's ERP from Freestyle Solutions.

What you should ask anyone else quoting this

Four questions, and the answers tell you quickly whether they have done it before.

How will you extract the data if the database credentials are gone. How will you build the URL inventory without a sitemap. Where do you expect the pricing rules to live, and how will you find them. And what happens to the nightly job that sends the file to the warehouse.

A vendor who answers the first one with "you provide a CSV" is quoting a different project from the one you have.

Ready to move off a system nobody maintains

Bring whatever you have. Access to the site, access to the server if it still exists, a rough idea of how many customers are on negotiated pricing, and the names of the people who take orders by phone. That last one matters more than it sounds.

Talk to Our Experts, or start with Uncap Blueprint, the paid discovery engagement that produces the specification this project needs before anyone can price it honestly.

Uncap is a Shopify Platinum Partner, on Shopify since 2013, and migrations from Magento, BigCommerce, WooCommerce and ten other platforms sit alongside this one.

Open source carts we migrate from

Plenty of custom stores started life on an open source cart and were modified until the original platform was hard to recognize. None of the platforms below has a page of its own on this site, and the method on this page applies to each of them: establish what the database holds, recover the rules from the code, build the URL inventory, then migrate.

  • Drupal Commerce to Shopify migration. Commerce built on the Drupal content management system, where the catalog and the site content share one database and custom modules usually carry the business rules.
  • PrestaShop to Shopify migration. A PHP cart extended through modules and theme overrides, so the installed modules get inventoried before anything is exported.
  • OpenCart to Shopify migration. A lightweight PHP cart where changes are often made through OCMOD modifications or direct edits to core files, which is why the code gets read rather than assumed.
  • osCommerce to Shopify migration. One of the original open source carts, still running long-lived stores whose code has been patched for years.
  • Zen Cart to Shopify migration. A descendant of osCommerce with the same history of long-running, heavily modified installs.
  • VirtueMart to Shopify migration. The ecommerce extension for Joomla, where the store shares its users and content with the Joomla site around it.
  • Sylius to Shopify migration. An open source ecommerce framework built on Symfony, usually chosen for bespoke builds, so most of the business logic is code written for that one company.
  • Spree Commerce to Shopify migration. An open source Ruby on Rails platform, typically extended with custom Rails code and bespoke integrations.
  • Saleor to Shopify migration. A headless, GraphQL-first platform built in Python and Django, where the storefront and the commerce engine are separate codebases to inventory.
  • Medusa to Shopify migration. Open source headless commerce built in Node.js, usually paired with a custom storefront and custom modules.
14 Common questions

Answers, before you ask.

Can you migrate a custom built ecommerce site to Shopify?

Yes, and the work is shaped differently from a platform migration. There is no export tool, no connector and no documentation, so the first phase establishes what exists: the database schema, the extraction route, the business rules living in application code, and the URL inventory. Once those are documented the migration itself proceeds like any other.

We do not have the original developer. Is that a problem?

It is the normal situation rather than an unusual one, and it changes the method rather than the outcome. Schema meaning gets established by reading the database and testing against the live site. Business rules get recovered from code, from the people who take orders, and from order history. Where server access has been lost entirely, an authenticated crawl of the live site becomes the extraction route.

Why will you not quote a fixed price up front?

Because a fixed price against an undocumented system is either padded for the worst case or it is a number that will change. Uncap runs a paid discovery phase that produces the specification, and after that the migration is scopeable like any other. The discovery output is yours to keep regardless of who builds it.

How do you handle SEO when we do not know our own URLs?

The inventory is assembled from server access logs, Google Search Console exports, any existing sitemap, a full crawl of the live site and archive snapshots, then merged and ranked by traffic and link value. Those URLs are mapped to Shopify's fixed path structure, with deliberate decisions where a pattern cannot map cleanly.

Will our customer specific pricing survive?

Yes, rebuilt as Shopify catalogs assigned to companies. Worth knowing before you plan: Shopify documents a limit of 3 active catalogs across all B2B markets on the Basic, Grow and Advanced plans, with unlimited catalogs and direct assignment to companies and locations on Plus. If you run negotiated pricing across many accounts, that decides your plan.

What happens to the business rules in our current site?

They get documented, then rebuilt. Minimums, pack sizes, quantity break pricing, restricted assortments and approval workflows are usually written into application code rather than stored as data, so they cannot be exported. Recovering them is a discovery task and it is budgeted as one.

Can we keep our order history?

Usually yes, and how much is a business decision rather than a technical one. Some businesses migrate everything, some migrate a recent window and archive the rest, and some keep the old database read only for reference. The question is what your team and your customers actually need to see.

What about the systems our website talks to?

They get inventoried first, because on a custom build the site is frequently the integration hub rather than a participant. ERP, warehouse or third party logistics, CRM, tax, carrier rating, EDI and punchout are the common ones. The awkward ones are the scheduled jobs and one off scripts nobody documented. Those are found by looking rather than by asking.

How long does a custom cart migration take?

Discovery sets the schedule, which is the honest answer. Data quality, the number of business rules embedded in code and the integration count drive it far more than catalog size does. Uncap Blueprint produces the timeline along with the specification.

We want to migrate our legacy system to Shopify. Where do we start?

With discovery, because an undocumented system cannot be priced honestly from the outside. Uncap Blueprint is a $7,500 fixed-price plan delivered in four weeks and credited toward implementation. It establishes the database schema, the extraction route, the business rules that live in the code and the URL inventory, and produces the specification the migration is then scoped against.

Client reviews

What clients in this space say.

Verbatim reviews from clients whose case studies connect to this page, linked to the original review.

Everyone in the company, from the owner down to the project managers and tech support, took the time to really get to know our company and our needs for the new website. They are brilliant and very knowledgeable of all that Shopify can do.

Peggy FarabaughOwner & CEO, Vermont Woods Studios
Talk to Our Experts →