Performance Optimization & Maintenance
Profiling, caching, query tuning and ongoing maintenance for stores that have outgrown their setup.
Services
nopCommerce Migration & Upgrades
Whether you need a nopCommerce upgrade from an older 3.x or 4.x release to 4.90 or 5.0, or a migration to nopCommerce from another platform, we plan the move around your data, plugins, theme and customisations so go-live is predictable.
Existing store
CONCEPT SUPPLY
- Safety & PPE
- Hand tools
- Storage
- Vented safety helmet18.50
- Nitrile work gloves12.40
- Stackable storage bin14.75
- LED work light34.00
- Compact cordless drill89.00
Target store preview
staging.concept-supply.example
Concept Supply
Safety & PPE- Safety & PPE
- Hand tools
- Storage
- Vented safety helmet18.50
- Nitrile work gloves12.40
- Stackable storage bin14.75
Staging checklist
Rehearsal environment- Catalog mapping (complete)Categories and products matched
- Customer records (complete)Accounts and addresses imported
- Order history (in progress)Import running on staging
- Plugin compatibility (needs attention)One plugin needs rework
- Redirect review (pending)Waiting for sign-off
Example URL mapping
/category/12/safety-ppe
301 redirect
/safety-ppe
Where this helps
Situations that typically lead businesses to this kind of work.
- The store runs on an older nopCommerce or .NET version.
- Custom code was written directly into core files.
- Third-party plugins are not available for the target version.
- You are moving from another platform and need to keep products, customers and orders.
Capabilities
What we deliver
Version upgrades
Upgrades across nopCommerce releases: SQL upgrade scripts for 4.30 and earlier, automatic database migrations from 4.40 onwards.
Plugin porting
Custom and third-party plugins updated to the target version’s APIs.
Core change extraction
Customisations moved out of core files and into plugins where possible.
Platform migration
Products, categories, customers and order history migrated from other platforms.
SEO continuity
URL mapping and redirects planned to protect existing search visibility.
Rehearsed cut-over
Migration runs on staging first, with a documented go-live checklist.
Planning the work yourself first? Read our step-by-step guide to upgrading nopCommerce to 4.90 or 5.0 without breaking plugins — version paths, App_Data files, database migrations and a pre-launch test plan.
Deciding whether to move to 5.0? Read what changes in nopCommerce 5.0 — .NET 10, features moved into plugins and what plugin developers have to update.
Moving from WooCommerce, Magento, Shopify or a custom platform? Read our nopCommerce migration guide — what the built-in import covers, import order, customer passwords and 301 redirects.
If a migration includes moving product records between stores, see how a reviewed product import and export workflow handles SKUs, media and related catalog data.
Upgrades
nopCommerce upgrade services
nopCommerce has no automatic upgrade. Each upgrade means replacing the application files, keeping your settings, upgrading the database and making sure every plugin and theme supports the new version. The database step depends on where you start: stores on 4.30 or earlier apply SQL upgrade scripts one version at a time, while 4.40 and later upgrade the database through migrations on the first start of the new release.
The application side usually takes more planning than the database. Each release targets a specific .NET runtime — 4.70 runs on .NET 8, 4.80 and 4.90 run on .NET 9, and 5.00 runs on .NET 10 — and nopCommerce will not load a plugin that does not declare support for the running version. Customisations made directly in core files have to be found and re-applied, ideally as plugins so the next upgrade is simpler.
For the full procedure, including the App_Data files to keep, the connection-string change introduced in 4.50 and the .NET 10 runtime 5.00 needs, read how to upgrade nopCommerce to 4.90 or 5.0.
- Inventory of the current version, plugins, theme, core changes and hosting runtime
- Recommended upgrade path, including any intermediate versions for 3.x and early 4.x stores
- Custom plugins retargeted, rebuilt and tested against the new nopCommerce source
- Third-party plugin and theme compatibility checked with each vendor, with replacements where needed
- A full rehearsal on a staging copy of your production database
- Go-live checklist, rollback plan and post-launch monitoring
Migration
Migrating to nopCommerce from another platform
A platform migration moves your catalog, customers and order history into nopCommerce while the business keeps trading. Stores commonly arrive from WooCommerce, Magento or Adobe Commerce, Shopify, AspDotNetStorefront and custom-built .NET systems. Each exports data differently, so the work starts with a field-by-field mapping rather than a generic import.
Customer passwords are the usual exception. Other platforms hash passwords in their own way, so they often cannot be carried over directly. The options are a planned password-reset message at launch, or a custom plugin that validates the old hash at a customer’s first sign-in and then stores it in nopCommerce’s format.
For the import order, what to do about customer passwords and how to map old URLs, read how to migrate to nopCommerce step by step.
- Products, variants, attributes and specification attributes
- Categories, manufacturers, tags and product images
- Customers, addresses and customer roles
- Order history for reference and customer accounts
- Prices, tier prices and stock by warehouse where used
- Reviews, blog posts and content pages where the source platform provides them
Search visibility
Protecting search rankings during an upgrade or migration
A migration changes URLs almost by definition, and an upgrade can change them if custom routes or an SEO plugin stop working. Before launch we export every indexed URL from the old store, map each one to its new nopCommerce page, and test the redirects on staging.
- One-to-one 301 redirects from old product, category and content URLs
- Page titles, meta descriptions and search engine names carried across
- Redirect and status-code checks on staging before go-live
- Updated XML sitemap submitted to Google Search Console after launch
- Search Console coverage and 404 monitoring in the weeks after launch
Planning
What determines the effort
Two upgrades between the same versions can need very different amounts of work. We give an estimate after the assessment rather than a fixed price up front, because these factors decide most of it:
- How many major versions the store is behind, and whether it is on 4.30 or earlier
- The number of plugins, and how many are custom versus third-party
- Whether customisations were made in core files or in plugins
- How much the theme overrides default views
- Catalog, customer and order volume, and any integrations with ERP, CRM or payment providers
Approach
How we approach it
- 01
Assess the current store
We inventory versions, plugins, customisations and data volume.
- 02
Plan the path
We recommend an upgrade path and flag anything that needs rework.
- 03
Rehearse, then go live
We rehearse on staging and agree a cut-over window with you.
Platform
nopCommerce versions we support
We build for and support nopCommerce 4.50 to 5.00. Each release runs on a specific .NET version, which sets the hosting a store needs and how much work an upgrade involves.
Stores on 4.40 or later upgrade the database automatically when the new release first starts. Plugins and the theme still need builds for the target version.
Planning a move between versions? Read our nopCommerce upgrade guide.
| nopCommerce | .NET runtime | Notes |
|---|---|---|
| 4.50 | .NET 6 | |
| 4.60 | .NET 7 | |
| 4.70 | .NET 8 | |
| 4.80 | .NET 9 | |
| 4.90 | .NET 9 | Previous release line, latest patch 4.90.8 |
| 5.00 | .NET 10 | Current release, 27 October 2026 |
Checked against the nopCommerce source code and release notes on 27 October 2026. Sources: nopCommerce releases on GitHub, Official upgrade documentation.
Questions
Migration & Upgrades FAQ
Something else on your mind? Ask us directly.
Can nopCommerce be upgraded across several versions at once?
For stores on 4.40 or later, the new release upgrades the database through migrations on first start, so the official procedure does not require installing every intermediate release. Stores on 4.30 or earlier must apply each SQL upgrade script in sequence first. Plugins and themes must support the target version either way.
Which nopCommerce version should we upgrade to?
nopCommerce 5.00, released on 27 October 2026 on .NET 10, once every plugin and your theme have 5.00 builds. If a plugin you depend on is not ready yet, we upgrade to 4.90.8 on .NET 9 first, and the work carries over to 5.00 later.
Will our plugins work after the upgrade?
Only if each plugin has a build for the target version. nopCommerce checks the versions a plugin declares and will not load one that does not support the running release. Custom plugins need to be rebuilt against the new source; third-party plugins need an updated build from their vendor or a replacement.
Will an upgrade change our store’s URLs?
A standard upgrade keeps product and category search engine names. URLs can change if the store depends on custom routing or an SEO plugin that has no compatible version, which is why we test URLs and redirects on staging before go-live.
Can customer passwords be migrated from another platform?
Often not directly, because platforms hash passwords differently. A password-reset message at launch is the simplest option. Where a smoother experience matters, a custom plugin can verify the old hash at first sign-in and re-save the password in nopCommerce’s format.
Do you rehearse the migration before go-live?
Yes. Every upgrade or migration runs first on staging with a copy of production data. We agree the cut-over window, freeze period and rollback plan with you before touching the live store.
Related
Often combined with
Custom nopCommerce Development
Tailored storefronts, admin workflows and business rules built on nopCommerce and ASP.NET Core.
Custom nopCommerce Plugin Development
Self-contained plugins for payments, shipping, pricing, widgets and integrations — packaged for clean upgrades.
Ready to plan your nopCommerce project?
Tell us about your storefront, ordering workflows or integrations by email, phone or WhatsApp. An outline is enough to start.