Gold Partner. We will tell you whether to extend the shop you have, take it over, or migrate onto nopCommerce. If you are on 3.x or 4.0, that is a different job.
Australian .NET team. nopCommerce Gold Partner. 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.
A lot of the shops we hear about were chosen because you could own the source and hook it to a CRM or ERP. Then the person who knew the plugins left, and the next feature became a guess.
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, or the one you are about to start.
If the version is 3.x or 4.0, go to nopCommerce upgrade. That page is the climb. This one is not.
nopCommerce is still a real product. The problem is rarely “nopCommerce cannot do it”. It is a store whose plugins, theme, and backend hooks are the actual product.
Source customisations sit in plugins or in the application. Without them, “just add a feature” is a guess. Takeover is a real job: support, the next plugin, and a store someone else can understand.
Payment, shipping, and anything written for this store is not a marketplace download. The theme is often the storefront. Custom development, plugin work, and theme work are how a current shop actually moves.
B2B shops often bought nopCommerce so it could talk to NAV or another backend. Those hooks are written, not installed. Published NESS work is nopCommerce maintenance and a Dynamics NAV integration. That is the shape of the problem.
Customer groups, tier pricing, purchase orders, multi-store. If those are wrong, a prettier theme does not fix the shop. B2C shops stall on the same pattern when checkout, plugins, or the theme cannot be touched.
There is no automatic upgrade. That assessment lives on /nopcommerce-upgrade. Do not start a “rebuild on current” from this page if the real work is the official climb.
None of that makes the catalogue, orders, or pricing rules worthless. It does mean “pick a theme on Monday” is usually the wrong first move.
We start with the store, not with a theme.
Version, custom plugins and themes, payment and shipping, CRM or ERP hooks, B2B rules, and how the site is hosted. If there is no store yet, we look at the catalogue, the backend it has to talk to, and whether nopCommerce is still the right home.
There are three honest outcomes. We recommend one, not all three.
Catalogue, customers, orders, and the rules people actually use come across. Plugins that do not exist for the target store are rebuilt, not file-copied.
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 store. If you already know you want a nopCommerce-only partner forever, that is fine, we are a Gold Partner, and we will still tell you when the job is an upgrade, a takeover, or a leave. If you want an honest fork in the road, talk to us.
A URL is enough to start. A sentence about the store you do not have yet is enough too.
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.
These are published nopCommerce jobs. They are not a promise that your store is the same project.
A new build, a takeover, or a migration onto nopCommerce still starts with its own assessment.
Thirty minutes. Bring a URL, or a sentence about the shop. We will tell you whether to build, take over, migrate onto nopCommerce, or send an old 3.x store to the upgrade page.
Book a free 30-minute discovery call