AbleCommerce to Shopify or BigCommerce: What Transfers and What Doesn’t

This post explains exactly which parts of an AbleCommerce store carry over to a hosted platform like Shopify or BigCommerce, which parts have to be rebuilt, and where migrations usually go wrong. It is written for store owners and IT managers weighing a move, including those who may be better off staying where they are.

AbleCommerce has run serious online stores for a long time, and plenty of them are still running well. We know, because we still build and support them at the source level for clients like Bond Arms, Marathon Tires, and National Tool Warehouse. So this is not a post arguing that you should leave. It is a post about what a move actually involves, written by the people who would have to do the work either way.

If you are considering the move, the questions that matter are not about features. They are about your data, your URLs, and the custom logic your business depends on. Those three things decide whether a migration is straightforward or painful.

Should you migrate off AbleCommerce at all?

Often, no. If your store is stable, your version is supported, and your customizations are working, the honest answer is that migrating spends a large budget to end up somewhere you already are. We keep AbleCommerce stores healthy and current for clients who have no reason to move, and that is frequently the better investment.

The reasons that genuinely justify a migration are narrower than most vendors suggest:

• Your team cannot find anyone to maintain the platform, and the risk of being unsupported has become the real problem
• You need a checkout, subscription, or point-of-sale ecosystem that would be expensive to build and maintain yourself
• Your version is far enough behind that upgrading in place costs a meaningful fraction of a rebuild
• Your business model changed, and the store is now fighting the platform rather than serving it

If none of those describe you, staying put and investing in maintenance is a defensible decision. If one or more do, keep reading.

What transfers cleanly from AbleCommerce?

Most of your catalog and customer records transfer, with mapping work. Anything that lives as structured data in the AbleCommerce database has a path to a hosted platform. The effort is in translating its shape, not in whether it can move.

Reliable to migrate:

• Products, including titles, descriptions, SKUs, pricing, and images
• Variants, once AbleCommerce option and variant structures are mapped onto the destination platform’s option model
• Categories, remapped as collections
• Customer records, including addresses and contact details
• Order history, imported as historical records for reference and reporting
• Content pages, though layout is usually rebuilt rather than copied
• URLs, preserved through a redirect map, which is critical and covered below

What does not transfer, and has to be rebuilt?

Anything that was custom code on the AbleCommerce side has no automatic equivalent. AbleCommerce is a .NET application whose source, CommerceBuilder, can be modified directly. That flexibility is exactly why long-running stores accumulate logic that cannot be exported.

Expect to rebuild:

• Customer passwords. Password hashes cannot be carried across. Customers reset on first login, and that reset flow needs planning and a clear customer email.
• Custom DAL or core modifications. Any behavior implemented by changing CommerceBuilder source has to be re-expressed as an app, a script, or a workflow on the destination platform.
• Custom checkout logic. Hosted checkouts are deliberately constrained. Rules that were trivial to inject in .NET may need a different approach entirely.
• Custom payment or shipping integrations, which become apps or third-party services.
• Theme and templates. The front end is rebuilt, not ported.
• Admin reports and internal tooling built on top of the AbleCommerce database.
• Complex B2B pricing rules, if they were implemented in custom code rather than configuration.

That last one deserves a flag. If you run customer-specific pricing, contract pricing, or procurement integrations, scope those first rather than last. They are the most common reason a migration estimate turns out to be wrong.

Shopify or BigCommerce, and does the choice change the migration?

The data migration is broadly similar either way. What differs is where your custom logic lands, so the platform choice should follow your requirements rather than the other way round.

Practical differences worth weighing:

• Checkout flexibility. BigCommerce allows more checkout customization on its higher plans. Shopify’s checkout is more locked down, which is a constraint if your order flow is unusual and a benefit if you would rather not maintain one.
• B2B and customer-group pricing. Both can do it, but the mechanics differ enough that you should model your actual pricing rules against each before committing.
• App ecosystem. Shopify’s is larger, which usually means fewer things you have to build.
• Catalog structure. Product option and variant limits differ, and a large AbleCommerce catalog with many options is worth test-mapping against both before you choose.

To be straightforward about our own experience: our delivered AbleCommerce migrations have been to Shopify, and we are a Shopify Partner. We also work on BigCommerce sites and can take an AbleCommerce store there, and we will tell you plainly if we think the other platform fits your requirements better.

How do you keep your search rankings through a migration?

By mapping every existing URL to its new destination before launch, and shipping those redirects on day one. Ranking loss after a replatform is almost always a redirect problem, not a platform problem.

The sequence that works:

1. Export a complete list of live URLs from the AbleCommerce store, including product, category, and content pages
2. Pull the pages that actually earn impressions and clicks from Google Search Console, so priority is based on evidence rather than guesswork
3. Map each old URL to its closest new equivalent, one to one wherever possible
4. Implement the redirects as permanent 301s, not temporary ones
5. Preserve titles, meta descriptions, and heading structure on the pages that already rank
6. After launch, watch coverage and crawl errors, and fix redirect gaps quickly

Common failure points we see in migrations done without this discipline: category URLs collapsed into a single collection, product URLs redirected to the homepage instead of the matching product, and structured data quietly dropped so rich results disappear. For a wider view of the planning involved, see what to know before migrating ecommerce platforms.

Why the same team should know both sides

Most migration work goes wrong at the point where someone has to explain what the old system was actually doing. An AbleCommerce specialist who has never shipped on Shopify cannot answer that, and neither can a Shopify agency seeing CommerceBuilder source for the first time.

We have built on AbleCommerce since the platform’s early versions and still maintain stores on it today. We have also delivered migrations onto Shopify, including ChefShop, a client we have worked with since 2014. That overlap is the whole point: the people reading your old custom code are the people writing the new implementation.

Talk to the team that knows both platforms

We build and support AbleCommerce stores at the source level, and we build on Shopify as a Shopify Partner. If you are weighing a move, we will give you an honest read on whether it is worth doing, and a scoped plan if it is. See our migration services or get in touch.