Virto Commerce v2 has been unsupported since 1 June 2022. Current v3 is on .NET 10. Deep customisation is a project. We will tell you whether the vendor path still applies.
Australian .NET team. We look at the platform before anyone talks about a rebuild.
01
What you have
02
What is safe to keep
03
Upgrade or move
The platform still takes orders. That is why it has been left alone.
Virto is a headless commerce engine with a module story. A lot of the installs we hear about were customised in v2, then the person who understood the extension points left, and “it still runs” became the whole strategy.
You might recognise one of these:
You do not need a new brand, or a SaaS pitch. You need a clear read on the modules you already have.
Virto Commerce is still a real product. Current platform line is v3. In February 2026 the vendor moved the core platform from .NET 8 to .NET 10. Platform and module versions for that jump are 3.1000+; other modules go to Stable Release 12. The problem is not that the vendor vanished. It is that v2 is a different .NET generation, and custom modules are the upgrade.
Vendor community post when v3 GA’d: version 2 will not be supported since 1 June 2022. v2 is the Framework-era platform. There is no current support contract to lean on. The site can still run. It is not a supported product.
v2 is Framework-era. v3 is a different .NET generation. Deep customisation voids the easy path.
Vendor promised scripts and guides for shops that stayed on extension points. Deep customisation is extra effort — their words, not ours. v3 beta-era notes aimed at API and DB backward compatibility with 2.x if extension points were used. Unity DI became Microsoft DI. If the business rules live outside those extension points, you are building a project, not running a script.
3.800+ is the .NET 8 line. Microsoft ends .NET 8 LTS on 10 November 2026. The .NET 10 line is 3.1000+. Vendor says the .NET 10 platform is backwards compatible with previous stable releases on .NET 8 (3.800+). Custom modules should still be updated: install .NET 10, update Platform, Customer, and xAPI to 3.1000+, other modules to Stable 12+, retarget projects to net10.0. Module version skew — Platform 3.1000 against old modules — is an ops failure mode.
Virto is headless. The storefront and xAPI clients break if only the platform moves. Do not assume the admin SPA is current just because the engine is on .NET 10 — verify that at discovery. Hiring follows modern .NET and headless, not the v2-era admin skill set.
None of that makes the catalogue or the module rules worthless. It does mean “run the v3 script on Monday” is the wrong first move if the customisation is the product.
We start with the platform, not with a destination.
v2 versus v3, .NET 8 versus .NET 10, which modules are custom, whether extension points were actually used, and which storefronts and xAPI clients sit in front. We will tell you whether the documented path applies.
There are three honest outcomes. We recommend one, not all three.
Catalogue APIs and the modules people actually depend on come across. Deep custom code that sat outside extension points is rewritten. Storefronts move with the platform, not after it.
Source, a short record of what changed, and a platform someone else can understand.
We will not tell you v2 still has a vendor contract. We will not tell you Shopify is the answer to every headless engine. If you already know you want to stay on Virto forever, a Virto-only partner 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.
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 and Dynamics NAV — related commerce work, not a Virto upgrade. We have not published a Virto Commerce case study. Your platform 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 v3 on .NET 10, leave Virto, or leave it alone for now.
Book a free 30-minute discovery call