Embed Size (px)
Citation preview
Is it the time?How does migration from Magento 1.x to 2.x look like?
Piotr Karwatka, CoCEO Divante
Divante
eBusiness Software House operating since 2008
Over 160 people at our office in Wroclaw, Poland
Clients from Europe, Asia, Africa and the North America
Case studies: divante.co/portfolio
Key to success?
Pragmatic over egocentric
Business goals first
Best tools available
The Migration process - basics
- Architecture has changed - a revolution; - new admin panel, new themes, new code structure,- PHP7, new JavaScript framework- code is easier to maintain and a lot of modules are already ported to M2,
- Good news - one can easily migrate data - there is a tool for that (Data Migration Tool),- But not for the code and not for the template (although there is limited Code Migration Tool)!
- Redesign is a good moment to plan migration.
- The amount of work needed to update the software of your store actually depends on the amount of dedicated changes that were applied during the implementation.
- The rule of thumb for custom features?
1. Check if the feature is in a M2 standard,2. Check if there is module for that and if it’s compliant with M2?3. None of the above - then re-write the code / create new module.
New Architecture
https://www.ubertheme.com/magento-news/11-exciting-features-magento-2/
1. New structure,2. New layout elements,3. CSS preprocessor,4. Magento UI library,5. HTML5, PHP7, RequireJS,
Composer …6. Improved indexers, FPC, Varnish,7. New Admin panel (UX improvements)8. New Responsive themes - Lumia +
Blank Theme
Magento Code Migration Tool
Supports:- Namespaces,- Module directory structure,- Configuration XML files,- Magento code interaction
Doesn’t support:- Template files and design,- Changes in business logic
Data Migration Tool
Supports:- Products and categories,- Customers,- Orders and invoices,- Shipments and credit memos,- Core configuration,- Wishlists & ratings,
Doesn’t support:- Catalog DB layout updates,- Web API credentials,- Admin users and privileges,- Media files,- Custom data,- 3rd party data
The Migration process - timeline
1. Audit your existing code - make extensions and custom code evident,
2. Run in parallel empty Magento 2 site,3. Migrate the data using migration tool,4. Make redesign - mockups + gfx +
Magento theme code5. For custom extensions:
a. Check new standard,b. Check if extension is already
ported,c. Rewrite the code.
6. Tests & stabilization7. Launch
Migration of 3rd party features
http://www.slideshare.net/mzeis/migrating-from-magento-1-to-magento-2
Migration of your custom features
http://www.slideshare.net/mzeis/migrating-from-magento-1-to-magento-2
Is it worth it?
- Magento 1.x will be supported until 2018 - security paths will no longer be issued; no new features,
- Magento 2.x can be much more efficient and scalable (rewritten checkout and indexing, new MySQL cluster support, Varnish support, Full Page Caching even in Community)
- Magento 2.x is stable (learn from the trenches) - we create new sites ONLY on Magento 2.x - it’s great technology for, at least ,the next 5 years!
The cost of migration can be as high as 50-80% of new implementation and it will take from 8-16 weeks; it depends how customized your site is.
Redesign/UX changes should be merged with migration to maintain high business value/effort ration.
Case Study
Customer Experience Audit
HEADER & SLIDER
BEFORE BEFORE BEFOREAFTER AFTER AFTER
BRAFINDER CHANGE LANGUAGE
BEFORE AFTER
PRODUCT PAGE
ERROR 404
BEFORE AFTER
BEFORE AFTER
CHECKOUT
Mobile device conversion rate has increased 103%. Mobile traffic has increased 26%.
103%
Bounce rate has dropped by 40%.
40%
Conversion Rate has risen by 30%.
30%
The number of orders has increased by 37% comparing year to year during Black Friday and
Cyber Monday
37%
Magento 2: What you should be careful about
- Lack of recent and updated developer’s documentation,
- Finding a solution is easy. Finding the best solution isn’t,
- Check the quality of ready-made modules and themes twice!
- Problems with backward compatibility within minor releases (2.0 vs. 2.1),
- Developers need far deeper JS experience (Knockout.js),
- Lack of particular payment / shipment extensions - but the marketplace is growing rapidly
Divante UK286C Chase RoadLondon, N14 6HFUnited Kingdom(+44) 20 [email protected]
Divante Sweden
Divante HQ
Divante NLDivante UK
Divante HQ17 Dmowskiego Street50-203 WroclawPoland(+48) 733 355 [email protected]
Divante HollandRivium Quadrant141-181, 2909 LCCapelle aan den IJsselThe Netherlands(+31) 657 625 [email protected]
Divante SwedenErik Dahlbergsallén 15115 20 [email protected]
