E-commerce platform modernization checklist: what to check before you move a store

OutsourcingVN is operated by Netbase JSC, which migrates, recovers and rebuilds commerce platforms for a living, so read this checklist as a supplier's list. It is written to be usable with any team, and it leans on four Netbase records: a Magento 1 to Magento 2 migration, a scoped store recovery, a headless reward shop and conversion work on a print store.

Contents

• When is a commerce platform due for modernization?
• What should the checklist cover?
• Which modernization route fits your store?
• Worked scenario: a homeware store leaving an unsupported version
• What do Netbase commerce records show?
• Which questions should you ask a modernization supplier?
• What goes wrong in commerce modernization?
• How this guide is sourced and where it stops
• Common questions
• Bring your extension list and your end-of-support date

When is a commerce platform due for modernization?

A store rarely needs modernizing because it looks old. It needs it when one of four triggers appears: the platform version is leaving vendor support and security patches will stop; an extension or customization blocks a change the business has decided to make; the store has been compromised or keeps failing under ordinary load; or a new channel, such as a mobile app, a marketplace or a partner storefront, cannot be served from the current architecture.

Vendor lifecycles make the first trigger concrete. Adobe's published lifecycle policy for Adobe Commerce, checked on 2026-09-28, gives each version a three-year standard support window from general availability, and warns that staying on an unsupported version exposes the store to security vulnerabilities and loss of support. Put the end-of-support date for your version in the business case; it is the one deadline nobody can negotiate.

The legacy system modernization guide covers the general decision for any system. This page is the commerce-specific list that sits underneath it.

What should the checklist cover?

Work through each area and record evidence, not opinions. An area you cannot fill in is itself a finding.

The catalogue and customer rows feed the migration plan; the legacy data migration planning guide covers profiling, rehearsals and cut-over for those records.

Worked scenario: a homeware store leaving an unsupported version

A homeware retailer runs a store on a platform version that has left vendor support. It has 14 extensions, a payment gateway module, an ERP stock feed and around 3,000 products with variants. The scenario is illustrative and describes no client.

• Week 1, inventory. The team lists every extension against the running code. Two turn out to be disabled but still loaded; one has no supported version for the target platform and is replaced by a small custom module.
• Week 2, search baseline. A crawl lists the 400 URLs that earn most organic visits. Each gets a mapped target URL and a permanent redirect.
• Weeks 3-6, build and data rehearsal. Extensions are installed and configured on the new version, customizations re-implemented, and two trial data transfers are run and checked by the merchandising team.
• Week 7, cut-over. Orders are frozen for a short window, the final data transfer runs, redirects go live and test orders go through every payment route.

Google's site-move guidance, checked on 2026-09-28, recommends server-side permanent redirects from old to new URLs, kept for as long as possible and generally at least a year, and an updated sitemap. The retailer keeps its redirects indefinitely, because the cost is small and old links in emails and marketplaces keep working.

What do Netbase commerce records show?

For Netztech, Netbase delivered a Magento 1 to Magento 2 Commerce migration in 35 working days, including migrating 11 extensions with installation, configuration, customization and data transfer. The Netztech migration record is the clearest example of why the extension row in the checklist decides the scope: each extension became its own line of work.

For an existing client store, Netbase scoped a three-phase recovery of a compromised Magento site: investigation with an infected-file report and a recovery plan, then cleaning and system recovery, then file restore, recoding and hardening with Magento security patches applied, typically 6 to 13 days in total depending on the damage. The Magento recovery and hardening record shows the modernization trigger nobody plans for; recovery is never guaranteed, which is why the security row belongs in the checklist before an incident.

For a Dubai-based loyalty and rewards technology company, Netbase delivered a headless multi-store reward shop platform on Magento 2 Open Source with a Next.js front end, including a hybrid points-plus-cash checkout, Arabic and English, and integrations by webhook and scheduled sync, in four phases over 3.5 to 4.5 months. The loyalty reward shop record illustrates the headless route.

For 4over4, Netbase delivered e-commerce conversion work on its print store, including a product recommendation engine and an automated conversion of uploaded Adobe Illustrator files to SVG so layers can be edited; the 4over4 conversion record shows modernization that adds capability without moving platform. Netbase has also built representative Magento stores with companion Android and iOS apps for a women's fashion retailer in the Netherlands, an omnichannel fashion retailer in Nigeria and a parts and equipment seller.

Which questions should you ask a modernization supplier?

• How will you build the extension inventory? Expect a check against the running code and database, not a screenshot of the admin extension list.
• Which extensions will be replaced rather than migrated, and why? Each replacement is new code you will maintain.
• How many data rehearsals are included, and who signs them off? At least one rehearsal checked by your merchandising or operations team.
• What is the redirect plan, and who owns the crawl? A named person with the list of top landing pages.
• How will checkout be tested? A test order through every payment route, tax zone and shipping rule you use.
• What happens to the old store after cut-over? A defined read-only period and a decommissioning date.

What goes wrong in commerce modernization?

• Inventory from the admin screen only. Direct core edits and disabled-but-loaded modules surface mid-build as surprises.
• Search treated as a launch-day task. Organic traffic drops because top URLs were never mapped.
• Checkout tested with one card. A secondary gateway or a tax zone fails in the first week.
• Integrations assumed to reconnect. The ERP or stock feed silently stops, and stock levels drift.
• Modernization and redesign in one step. Two changes at once make any drop in conversion impossible to diagnose; Google's own guidance advises changing one thing at a time where possible.

How this guide is sourced and where it stops

Netbase facts come from approved entries in the OutsourcingVN claim register and their attested sources, published in registered wording: the Netztech migration, the scoped Magento recovery, the loyalty reward shop, the 4over4 conversion work and the representative Magento stores with apps. The methodology explains how claims are reviewed. The platform lifecycle and search-continuity points come from the Adobe and Google pages listed under Sources, checked on 2026-09-28. The homeware scenario is illustrative. Netbase's published records cover Magento migration, recovery, headless and conversion work; there is no published Netbase record here of a replatform from Magento to a different commerce platform, and no traffic or revenue result is claimed for any of these projects.

Bring your extension list and your end-of-support date

Legacy Application Modernization is the service route for migrating or restructuring a commerce platform, and the checklist above is the input it starts from.

OutsourcingVN is Netbase's own outsourcing-services platform. Submit a project with your platform version, extension list and integrations, and a person will reply with the route that fits and what discovery would need to check first.

Related services and solutions