Move your AbleCommerce store without guessing at the upgrade

Gold is end-of-life. Version 7 and Gold do not patch into 9. We will tell you what data will come across, what has to be re-skinned, and whether staying on AbleCommerce is still the right job.

Australian .NET team. We look at the store before anyone talks about a rebuild.

Still running AbleCommerce?

The store still takes orders. That is why it has been left alone.

AbleCommerce has been around a long time. A lot of the installs we hear about were bought because you could own the source and hook it to an ERP. Then the person who knew the themes left, and the version number stopped moving.

You might recognise one of these:

  • You are on AbleCommerce Gold — that is version 8 — or on 7
  • Someone said “just upgrade to 9” and then went quiet
  • USPS or another carrier plugin has already stopped working
  • Custom themes, scriptlets, or nVelocity pages are the storefront
  • The checkout plugins are old, and you are not sure what 9.0.12 actually replaces
  • You are not sure whether to stay on AbleCommerce or leave it

You do not need a new brand, or a Shopify pitch. You need a clear read on the store you already have.

Why these stores stall

AbleCommerce 9 is a real product. The current release is 9.0.12, dated 18 May 2026. The problem is not that the vendor vanished. It is the gap between Gold or 7 and a storefront that still gets support.

Gold EOL

Data only

Licence gate

Still MVC5

Gold is officially finished.

The May 2026 vendor newsletter ended support for AbleCommerce Gold. They said it in those words: it is a 10+ year old application, there are known security vulnerabilities, and USPS will cease to function if it has not already. There is no security patch that keeps you on Gold.

The upgrade is a data move plus a re-skin.

Vendor help is explicit. From Gold R10–R12, or from 7.0.3–7.0.7 and all Gold versions, orders, users, and products can come across. Themes, scriptlets, nVelocity pages, ConLib user controls, and WSP or WAP customisations do not. Retail-facing pages sit on a new CMS. You need a separate development environment and a version 9 licence. A Merge CMS Staging Data plugin exists so the live Gold or 7 store can keep running while a staging 9 site is re-skinned. That is a major upgrade, not a weekend patch.

Upgrades are subscription-gated.

9.0.12 needs a live or development key with subscription through the release date. Demo installs cannot be upgraded. In-version upgrades through Upgrade Manager are not cumulative. If maintenance lapsed, you do not have the download.

You are still on Framework after you get to 9.

AbleCommerce 9 is ASP.NET MVC5 on .NET Framework 4.8. The vendor’s own help requires Asp.Net 4.8. It is not ASP.NET Core, and it is not modern .NET. Hosting and hiring stay on Windows, IIS, and the Framework talent pool. An “upgrade to latest AbleCommerce” does not exit that world.

Payment plugins move with the version.

9.0.12’s headline change is a new PayPal Complete Payments integration, on top of an April 2026 security patch. Old checkout plugins are a live risk. Carrier integrations are the same story — the vendor called USPS out on Gold for a reason.

None of that makes the catalogue, orders, or ERP rules worthless. It does mean “apply the latest installer on Monday” is usually the wrong first move.

How we work

We start with the store, not with a destination.

1

Look at what you have

Version (7, Gold, or 9.x), themes and scriptlets, payment and shipping plugins, ERP hooks, licence and subscription state, and how the site is hosted. We will tell you what will survive a data upgrade, and what has to be rebuilt on the new CMS.

2

Decide the job

There are three honest outcomes. We recommend one, not all three.

3

Do the work in stages

Catalogue, customers, orders, and URLs matter more than a clean-room rebuild. The live store can keep running while a staging 9 site is re-skinned. Unused themes and dead plugins do not come across.

4

Hand it back so the next person can run it

Source, a short record of what changed, and a store someone else can understand.

Three honest outcomes

  • Upgrade to AbleCommerce 9 when you want to keep the product, have or can buy a v9 licence, and can fund the re-skin. That is the vendor-supported path.
  • Move off AbleCommerce to another .NET commerce stack, a SaaS storefront, or a custom modern .NET shop if the catalogue and order rules are the asset and the AbleCommerce UI is not.
  • Stabilise first when the store is fragile or the licence is unclear: document the custom layer, patch what we can on a current 9.x install, and plan the real move without taking production down to guess.

We will not tell you AbleCommerce 9 is modern .NET. We will not tell you WordPress or Shopify is the answer to every Gold store. If you already know you want to stay on AbleCommerce forever, the vendor’s own upgrade services may be a better fit. If you want an honest fork in the road, talk to us.

What we need for the first call

A URL and a rough version is enough to start.

  • Which AbleCommerce version: 7, Gold (8), or 9.x — and the build if you know it
  • Whether the storefront is stock, a bought theme, or custom scriptlets / nVelocity / ConLib
  • Which payment and shipping plugins are live
  • Whether you have ERP or order-logic customisations in the source
  • Whether the v9 licence and subscription are current
  • Hosting today (your IIS box, a Windows host, or AbleCommerce’s own hosting)
  • What “done” looks like: stay on AbleCommerce, leave it, or get a clear picture first

The first call is 30 minutes. You leave with a recommendation you can take to a manager, not a rebuild estimate pulled from thin air.

Related work

We have taken over and modernised ageing .NET systems for Australian organisations, including work with Data#3, Hastie, NESS, and NSW Health. NESS is ongoing nopCommerce maintenance and a Dynamics NAV B2B integration — related commerce work, not an AbleCommerce upgrade. An AbleCommerce 7, Gold, or 9 store still starts with its own assessment. We will not pretend it is a project we have already published.

FAQ

Can we just patch Gold?
No. The vendor ended support for Gold in May 2026. The documented path is a version-9 data upgrade plus a storefront re-skin. There is no Gold security release that closes that gap.
Is AbleCommerce 9 modern .NET?
No. It is ASP.NET MVC5 on .NET Framework 4.8. A successful 9.x upgrade keeps you on Windows and IIS. If leaving Framework is the real goal, that is a different conversation.
Do we have to leave AbleCommerce?
No. Current 9.x is a supported line. Leaving only makes sense when the custom layer, the hosting model, or the Framework constraint is the thing you actually want to change.
Will payment and shipping just work after the upgrade?
Do not assume that. The vendor flagged USPS on Gold, and 9.0.12 ships a new PayPal integration plus a security patch. Checkout and carrier plugins need their own pass.
We only have the live store and an old server.
That is common. Bring that.

Talk through the AbleCommerce store you already have

Thirty minutes. Bring a URL and a version number if you know it. We will tell you whether to upgrade to 9, leave AbleCommerce, or leave it alone for now.

Book a free 30-minute discovery call