There is no automatic upgrade. A 3.x shop has two framework breaks and a script-to-migration hop before current 4.90.6. We will tell you what plugins and ERP hooks will survive, and whether staying on nopCommerce is still the right job.
Australian .NET team. We look at the store before anyone talks about a rebuild.
01
What you have
02
What is safe to keep
03
Upgrade or move
The store still takes orders. That is why it has been left alone.
nopCommerce 3.x is ASP.NET MVC 5 on .NET Framework. 4.00 looks like Core and is not — it still targets Framework 4.6.1. A lot of the shops we hear about were bought because you could own the source and hook it to NAV or another ERP. Then the person who knew the plugins left, and the version number stopped moving.
You might recognise one of these:
You do not need a new brand, or a Shopify pitch. You need a clear read on the store you already have.
nopCommerce is still a real product. The current release is 4.90.6, published 8 July 2026, on .NET 9. The problem is not that the vendor vanished. It is the gap between a Framework storefront and a line that still gets product updates — and the Microsoft clock sitting under current 4.90.
The vendor says so. Backup the site and the database, then climb. To reach 4.30 and below you execute SQL upgrade scripts stepwise. A 3.90 shop targeting 4.20 goes 4.00, then 4.10, then 4.20. 3.x to 4.x specifically: install 4.00 over the existing database, run the 3.90-to-4.00 migration script, then keep climbing. From 4.40 the SQL scripts stop; first application start runs migrations. You cannot jump 3.90 to 4.90 in one script.
It shipped with an ASP.NET Core 2.0 web stack targeting .NET Framework 4.6.1. Settings.txt and InstalledPlugins.txt converted to JSON. Full .NET Core starts at 4.10. A shop that “already moved to Core” on 4.00 did not leave Framework.
Third-party plugins and themes must exist for the target minor. 4.90.x plugins work across 4.90.0–4.90.6. They do not work across majors. Payment, shipping, and ERP plugins are rebuilt, not retargeted.
B2B shops often bought nopCommerce for NAV or another ERP. Those hooks sit in the application. They are rewritten at each major, not patched by the upgrade ZIP. Our published NESS work is ongoing nopCommerce maintenance and a Dynamics NAV 2018 integration — SOAP Page, Codeunits, customer and product upsert. That is the shape of the problem. It is not a published 3.x to 4.90 upgrade.
Microsoft ends .NET 9 STS and .NET 8 LTS on 10 November 2026. A shop that just landed on 4.90 in August 2026 has under three months of Microsoft runtime support unless nopCommerce ships a .NET 10 build, or they accept an unsupported runtime. That is a planning fact, not a scare headline. The Windows box under a 3.x shop may already be worse — Server 2012 ESU Year 3 ends mid-October 2026; Server 2016 extended ends mid-January 2027.
None of that makes the catalogue, orders, or ERP rules worthless. It does mean “run the latest installer on Monday” is usually the wrong first move.
We start with the store, not with a destination.
Version, custom plugins and themes, payment and shipping providers, ERP or NAV hooks, source customisations, and how the site is hosted. We will tell you what will survive the official climb, and what has to be rebuilt.
There are three honest outcomes. We recommend one, not all three.
Catalogue, customers, orders, and URLs matter more than a clean-room rebuild. Plugins that have no target-major equivalent do not come across as a file copy.
Source, a short record of what changed, and a store someone else can understand.
We will not tell you nopCommerce is perfect. We will not tell you Shopify is the answer to every 3.x shop. If you already know you want to stay on nopCommerce forever, a dedicated nop shop may be a better fit. If you want an honest fork in the road, talk to us.
A URL and a rough version is enough to start.
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.
NESS is published nopCommerce maintenance and a Microsoft Dynamics NAV 2018 B2B integration. That is related nopCommerce work. It is not a 3.x to 4.90 upgrade case study. We have also taken over ageing .NET systems for Australian organisations, including work with Data#3, Hastie, and NSW Health. A 3.x or 4.00 store still starts with its own assessment. We will not pretend it is a project we have already published.
Thirty minutes. Bring a URL and a version number if you know it. We will tell you whether to climb to 4.90, leave nopCommerce, or buy time — and we will not pretend 4.90 is a multi-year runtime home.
Book a free 30-minute discovery call