Netztech: a Magento 1 to Magento 2 Commerce migration
Netbase migrated Netztech from Magento 1 to Magento 2 Commerce in 35 working days, moving 11 extensions across with installation, configuration, customization and data transfer. No business result was recorded for this project, so none is published. What this record reports instead is a duration and a scope, both attested.
Submit a project See all work records
Record at a glance
- Evidence level
- Named record: delivered scope and duration; no measured result exists
- 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
- Published metrics
- None. The project documents record no business outcome
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:
- installation of the extension on Magento 2 Commerce;
- configuration to match the behaviour the store relied on under Magento 1;
- customization where the Magento 2 version of an extension did not behave the way the store needed;
- data transfer, so that what the extension held in the old system was present in the new one.
Netbase's own materials describe these as 11 extensions, and the source behind them calls the same set 11 modules. Both wordings are registered; no other count is.
Why there is no percentage on this page
This is the only named migration record on the site, and it is the one with no figure. That is not an omission to be filled in later with something borrowed. The project documents record what was delivered and how long it took, and they record no revenue, conversion, uptime or performance outcome. Attaching a number from another project, or implying an improvement the source does not state, would make this page less true than it is now.
A duration is worth reporting on its own terms. 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. The methodology page explains why the record stops there.
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.
Does no metric mean the migration went badly? No. It means no business outcome was measured and recorded, which is common on a platform migration where the goal is continuity rather than change. Where a figure exists, this site publishes it; where one does not, it says so.
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.
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.