Upgrade Smartstore without treating 5+ as a file copy

Classic Smartstore.NET 4 is Framework 4.7.2. Anything older than 4.2 has no supported jump. Current 6.4.0 is on .NET 10. We will tell you whether the documented climb is worth it, or whether to leave.

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

Still running Smartstore.NET 4?

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

Smartstore is an open-source B2B and B2C shop from Smartstore AG. Classic Smartstore.NET and current Smartstore are not the same product surface. A lot of the installs we hear about were built on Framework MVC, then the person who knew the theme left.

You might recognise one of these:

  • You are on Smartstore.NET 4.x, or older than 4.2
  • Someone said “just upgrade to 6” and then went quiet
  • Custom MVC themes or Framework plugins are the storefront
  • A payment or shipping provider has no current module
  • Legal has not finished the AGPL conversation
  • You are not sure whether to stay on Smartstore 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

Smartstore is still a real product. Current GitHub line is Smartstore 6.4.0, published 29 May 2026, updated to .NET 10. The README calls it an ASP.NET Core 10 platform. The problem is not that the vendor vanished. It is that 5+ is a port of classic Smartstore.NET 4, not a DLL retarget.

Pre-4.2

Framework 4.x

Port not retarget

AGPL

Older than 4.2 has no supported jump.

Vendor and README: upgrading from versions earlier than 4.2 is not supported. Migrate to Smartstore.NET 4.2 first, then upgrade to Smartstore 5+. From 4.2 you replace application files, keep App_Data, and data migrates automatically. There is no vendor calendar EOL for 4.x on the pages we can cite. What we can say: 4.x is Framework-era; current investment is the Core / .NET 10 line.

Caption under the diagram:

Pre-4.2 has no documented jump. 5+ is a port. That is why stores stall.

5+ is a rewrite of the presentation layer.

Smartstore.NET 4 ran on .NET Framework 4.7.2 and ASP.NET MVC. Smartstore 5+ is the ASP.NET Core port of that product. Themes, plugins, and Framework MVC customisations do not become Core modules by file copy. Payment and shipping providers on 4.x may have no 6.x module. Plugins and themes are version-locked to the Core line.

AGPL-3.0 is a licence conversation, not a footnote.

The open-source line is AGPL-3.0. A commercial licence is something you buy from the vendor if you do not want that copyleft on customisations. We will not call AGPL “free for any commercial use”. That review is often why the project never starts.

Current 6.4.0 is on .NET 10 — if you get there.

Microsoft’s .NET 10 LTS ends 14 November 2028. That is a real runway after the port. The ecosystem is smaller than nopCommerce or a hosted SaaS. We will not invent Australian store counts. Hiring and plugin coverage are the constraint, stated as ecosystem size, not a census.

None of that makes the catalogue or the order rules worthless. It does mean “replace the files on Monday” is the wrong first move if you are older than 4.2, or if the theme is the store.

How we work

We start with the store, not with a destination.

1

Look at what you have

Version (pre-4.2, 4.2, or already 5+), themes and plugins, payment and shipping providers, whether customisations are AGPL-sensitive, and how the site is hosted. We will tell you whether the documented 4.2 → 5+ path applies.

2

Decide the job

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

3

Do the work in stages

Catalogue and orders matter more than a clean-room rebuild. Framework themes and plugins that have no Core module 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

  • Climb 4.2 to Smartstore 5+ / 6.4 on .NET 10. That is the documented vendor path, once you are on 4.2.
  • Replatform to another .NET commerce stack or a SaaS storefront if the port cost, the AGPL conversation, or plugin coverage is the real job.
  • Custom .NET 10 shop if the catalogue rules are the asset and Smartstore is no longer the product you want to maintain.

We will not tell you Smartstore 6 is a file copy of 4. We will not tell you Shopify is the answer to every Framework shop. If you already know you want to stay on Smartstore forever, the vendor’s own path 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 Smartstore version: older than 4.2, 4.2 / 4.x, or already 5+ / 6.x
  • Whether the storefront is stock, a bought theme, or custom MVC
  • Which payment and shipping providers are live
  • Whether legal has a view on AGPL versus a commercial licence
  • Hosting today (your IIS box, a Windows host, Linux already)
  • What “done” looks like: stay on Smartstore, 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 nopCommerce maintenance and a Dynamics NAV integration — related commerce work, not a Smartstore upgrade. We have not published a Smartstore case study. Your store still starts with its own assessment. We will not pretend it is a project we have already published.

FAQ

Can we jump a pre-4.2 shop straight to 6.4?
No. The documented path is migrate to Smartstore.NET 4.2 first, then upgrade to Smartstore 5+. Earlier than 4.2 is not supported.
Is Smartstore 5+ just a retarget of 4.x?
No. 5+ is a port of Smartstore.NET 4 from Framework MVC to ASP.NET Core. Presentation and modules are rebuilt.
Does AGPL mean we can customise for free?
AGPL-3.0 is not a blank commercial cheque. Read the licence, or buy a commercial licence from the vendor if you do not want copyleft on customisations. That conversation belongs before a production fork.
Is 6.4.0 a long home if we get there?
It is the current product, on .NET 10. Microsoft’s .NET 10 LTS ends 14 November 2028. Plugin and hiring coverage are still the smaller-ecosystem constraint.
We only have the live store and an old server.
That is common. Bring that.

Talk through the Smartstore you already have

Thirty minutes. Bring a URL and a version number if you know it. We will tell you whether to climb from 4.2, leave Smartstore, or leave it alone for now.

Book a free 30-minute discovery call