3. Vikrant Shukla
Magento Certified Solution Specialist
VP - eCommerce
Netsmartz
Head of Magento Practice at
Envision Ecommerce, A Netsmartz Company
@vikrantshukla
/in/shuklavikrant
4. • Why Magento Migration from 1 to 2?
• Analysis of Magento 2 Ecosystem
• When is the right time?
• How to do the Migration?
• Analysis of Main Components
• Best Practices
• Analysis of Extensions
• Dependencies Analysis
• Migration Steps
• Q/A
Agenda
12. Analysis of Main Components
Data Code Theme
Standard Complex
Ground up Magento theming
Configuration rather than
customization of business logic
Handful of popular and mature
3rd party extensions
Complicated UX/UI / retrofits
Customization of business logic
Early versions of extensions,
many extensions, custom
extensions
Complicated integrations
Data exchange integrations via Magento
APIs
13. Migration Analysis Methodology
Review andAssess
• Desktop and personal device
requirements
Integrity of Magento Core code
Custom Modules
Extensions
Customized Features
Integrations
Database
Theme and Templates
Test Documentation
Infrastructure
Environments
•
•
•
•
•
•
•
•
•
•
Strategies
• Custom Modules
• Extensions
• New Features
• Theme
• Personal Devices
• Integrations
• Information Migration
• Business Process Changes
• Infrastructure
• Environments
• Testing
Current Magento
Landscape
Codebase & Database
System landscape &
Systems of record
Requirements &
Wireframes
Test Documentation
Existing and Future-state
Infrastructure Diagrams
Environments
Dev Tools & SDLC
14. Requirements
• Obsolete customizations
• Magento native features and functionality in use
• Desktop vs. mobile, progressive enhancements
• Mapping requirements to tests and acceptance
Code Audit
• Custom development
• Third-party extensions
• Dependencies between extensions
• Un-used modules
• JavaScript functionality
• Business logic in templates
Analysis Phase - Features
Theme
• Identify theme requirements
• Create theme approach
• Theme is not migrated by tools
Testing Process
• List down all the major features
• End-to-end (integration) testing
• Written documentation and gap analysis
• Mapping tests to requirements?
Non-code Related Strategies
• Integrations
• Information Migration
• Infrastructure and Environments
• Business Process Changes
16. List all installed extensions.
Divide extensions into four groups.
Cleanup
List Extensions Available In Magento 2.
List Extensions To Be Custom Built
• Unnecessary
• Expired
• Non-Priority
• Must needed extensions.
• Good to have.
• Can be installed in the future.
• Not needed.
Extensions
20. Step 1: Setting Migration
Step 2: Data Migration
Step 3: Delta Migration
• Data: SameAs Data Migration
• Code: bin/magento migrate:delta [-r|--reset] {<path to config.xml>}
• Data: Catalogs, Customers,And Orders,
• Code: bin/magento migrate:data [-r|--reset] {<path to config.xml>}
• Data: Stores, Websites,And System Configuration
• Code: bin/magento migrate:settings [-r|--reset] {<path to config.xml>}
Data Migration Tool Installation
21. http://devdocs.magento.com/magento-system-requirements.html
Magento 2 has new infrastructure requirements.
Update your infrastructure to suite Magento 2.
Dev Box is a useful tool
• http://devdocs.magento.com/guides/v2.1/install-gde/docker/docker-over.html
• Dropped support for PHP 5.5.X.
• Added support for PHP 7.0.X.
• Added support for Elasticsearch 1.7 And 2.X.
• Native support for SOLR and Varnish
Infrastructure Management
22. Key Take Away
• Be a Consultant and tell your client that they are already late to Migrate to
Magento 2
• Make sure that you have proper backups
• Not everything will be migrated, its not 1:1 Clone
• Analysis and Planning is more important phase of Migration
• Analysis of what moves on to Magento 2 and what is left behind is must
• Remember the Steps, Settings, Data and Delta
• Magento Migration is a development from Scratch, take best advantage to get rid
of unwanted business flows and hacks in code