Migrating from Magento Commerce 1 to 2 is a great opportunity to provide a better user experience and make your eCommerce platform ready for the future. It can also be a challenge, especially for bigger and more ambitious projects. A strong migration strategy, planning, and of course the right project management approaches are obligatory. But done right, Magento Commerce 2 gives merchants infinite new possibilities and speeds up development.

2. The Road of Migration
Stefan Willkommer
CEO | TechDivision GmbH
@swillkommer

3. What would be…
..in a really perfect world?

4. 1. Build a 3yr Digital Strategy
2. Rescope and Descope
3. Go MVP and optimize use of OOTB
3 Phase Plan
for a successful Launch

5. 1. Build a 3 year Digital Strategy
• Develop Digital Strategy Pillars that align with Merchant Business Plan.
• Envison > Align > Enable
• Envision > data driven, global benchmarking, stakeholder interviews and workshops
• Align > Agree growth KPI’s and Tactical strategies
• Enable > Scope and Specification of Project
• Use “mined data” from M1.X DB, GA, New Relic, ERP and POS.

6. 2. Rescope and Descope
• Remove any unwanted extensions
• Check ROI and Business Case on Legacy approach
• Descope redundant or problematic components
• Understand Magento roadmap
• Deliver Functional and Technical Specification based upon Strategy and ROI
• Use MoSCoW
Don’t just rebuild what you have in M1.X use the opportunity
to do some housekeeping!

7. 3. Go MVP and optimize
use of OOTB
• Drive towards OOTB as a default
• Minimise customisation
• Fully understand advances and improvements from M1.X to M2.X
• Examples: Staging and Preview, Elastic Search, PageBuilder, MBI
Magento 2.X native is a huge leap forward from M1.X and has heaps of great new
features and functionality. Use these OOTB as default and un-bloat your ecosystem

8. But this world…
…is not perfect at all!

9. The Challenge

10. • grown System over apx. 6 years
• permanently upgraded from CE 1.6 to EE 1.14
• huge Database (zipped 30GB)
• restructuring of the catalogue
• integration of ERP, PIM, OMS and WMS
• integration Omnichannel Loyality
• large Stakeholdermap
• complex releasemanagement

12. HALLHUBER in Numbers
Turnover
200 Mio €
Employess
2.000 Online Revenue
XX%
Stores
>400

13. Data and Statistics

14. In total 27 persons involved
Up to 13 Developers

15. Project duration
14 Months

16. Worked hours
12.206 h

17. Customer Only
22 Extensions

18. 33 Vendor Extensions

19. Without subtasks
880 User Stories

20. Letter pages Requirements
2481

22. Burndown chart

24. Migration Requirements
Data migration Data optimizationFeature migration
• Feature migration with
feature redesign
• reverse engineering of
features based on front end
• Developing new features
• Product structure
• Categories only in Magento,
so far from PIM (TB.one)

25. Migration Strategy
• Requirements Reverse Engineering
• Classical RE of customer requirements
• Reaching the final database schema at an early point in time in the project
(reached with release 0.6.0.0 last release 0.14.x.x.x)
• From this point on Nightly migration of data
• Parallel further feature development / tests of the specialist departments
• Editorial maintenance of the new system

26. M1
Migration DB Production DB
• Attributes
• Customer
• Catalog
• CMS
• Sales
• Rules, Wishlist
• HGC, HHC, etc.
Import
MagentoDataMigrationTool
M2
Import/
Export
Import/
Redakteur
Redakteur

27. Feature Highlights

29. CUSTOMER LOYALITY

34. Thank You!
Any Questions?
Stefan Willkommer
CEO | TechDivision
@swillkommer