Record at a glance
- Evidence level
- Named record: delivered scope and duration
- Client
- Netztech, named with permission on record
- Service
- Legacy Application Modernization
- Delivered scope
- Magento 1 to Magento 2 Commerce migration, including 11 extensions
- Duration
- 35 working days
Context
Magento 1 reached end of life, which turned an upgrade into a deadline for every store still on it. A migration of this kind is not a redesign: the catalogue, the customers, the orders and the behaviour a business depends on all have to arrive intact on a platform that structures them differently. Netztech needed that crossing made, and made once.
What the migration covered
The 11 extensions are the part that decides how long a migration like this takes. Each one was handled as its own piece of work rather than assumed to carry over:
| Step | What it covered | Best for |
|---|---|---|
| Installation | Installing the extension on Magento 2 Commerce | Extensions with a direct Magento 2 release |
| Configuration | Matching the behaviour the store relied on under Magento 1 | Stores that cannot change how an extension behaves for shoppers |
| Customization | Changing the Magento 2 version of an extension when it did not behave the way the store needed | Extensions whose Magento 2 release does not match Magento 1 behaviour |
| Data transfer | Moving what the extension held in the old system into the new one | Extensions that store their own data, not just configuration |
Netbase's own materials describe these as 11 extensions, and the source behind them calls the same set 11 modules.
How should a buyer read the duration?
Thirty-five working days is a plannable number: it tells a buyer that a migration of this shape, with roughly this many extensions, is a matter of weeks rather than quarters, which is the question most people actually bring to a platform deadline. A buyer planning a similar move can start by listing every extension the store depends on and checking whether a Magento 2 version of each exists. The methodology page explains how work records are evidenced. A store owner deciding whether to rebuild headless instead of migrating in place can weigh that trade-off on headless vs traditional ecommerce, and the fuller build scope behind a migration like this one is on ecommerce development.
Questions buyers ask
Would our migration also take 35 working days? It would take its own time. The count and complexity of your extensions, the state of your data and the amount of customization carried over are what move that number.
What should we settle before starting? Mostly the data. Legacy data migration planning covers the decisions that decide whether a cutover is quiet or not.
Can Netbase work with a client in my country? Yes. Every service on this site is delivered remotely from Hanoi, and Netbase has worked with clients in 80 countries. Delivery communication is in English, with weekly reviews and a named project manager.
Does Netbase work in my industry? Netbase takes on projects in any industry where the work can be delivered remotely and accepted by milestones. The industry pages describe the approach sector by sector, and the Work records show delivered projects.
How do I pay for a project? Payment is by bank transfer to the company account of Netbase JSC or through PayPal Business. The payee is always Netbase JSC, the company that operates OutsourcingVN.
Who do I talk to, and how do I start a project? Talk to Huy Nguyen (David), Founder and CEO of Netbase JSC: message him on WhatsApp at +84 937 869 689 or email project@netbasejsc.com. You can also send your brief through the project request form. Say which workflow or system the project concerns and what has to stay unchanged; the first step is a discovery conversation, and scope and milestones are agreed after it.
Facing a platform deadline?
See how the other work records are evidenced, then submit a project brief listing your platform version and the extensions you cannot lose. OutsourcingVN is operated by Netbase JSC and is Netbase's own outsourcing-services platform, so the estimate comes from the team that would do the migration.