Migrating Magento 1.x to Magento 2.0

[email protected] Technologies Pvt. Ltd.

Shabbir ChallawalaSr. Consultant (PHP)

Presenters

Shikha BhadouriaMarketing Consultant

• Content & Inbound marketing• Branding

• 6+ Years of Experience in PHP • 4+ years of Experience in Magento • Executed projects in both Community and Enterprise

Edition

© 2016 KNOWARTH Technologies Pvt. Ltd. 3

Who We Are

160+Members’ Team

Among50 FastestGrowing Startups in India (SiliconIndia)

90+Project Served in last

Two Years to 40+ Clients Delivered on Time, within

Budget

DELIVERING EXCELLENCEthrough One-stop-solution

approach

Thought Leaders7 Books

Authored & Reviewed

Worked on Projects forPortal, E-Commerce, Digital Marketing, UX/UI, ERP, Mobility, Product Engineering, Cloud Computing and RIMS

20 Mostpromising IT Companiesin INDIA (CIO Review)

© 2016 KNOWARTH Technologies Pvt. Ltd.

Worldwide Customers

4

Canada

USA

Norway

IndiaMiddle East

Australia

France

USACalifornia | Georgia | Florida | New York

AustraliaSydney | Melbourne

Middle EastDubai

EuropeUnited Kingdom | Norway | France

Magento Services at KNOWARTH

Magento Theme Development

Magento Integration

Services

Magento Performance Optimization

MagentoSupport

MagentoMigration

ModuleDevelopment

KNOWARTH's Ecommerce Product - Commercium

Fashion Store Restaurant Auto Store

Home Decor Store

Kids Store

Other core Technology Services

7

Custom Application Development

Cloud Hosting & management

Remote Infrastructure Management

Services

Enterprise Portal Development

ERPSolution

UI / UX Design & Development

Portal Performance and Assessment

Tuning

Mobile Application Development


Our Partners

8© 2016 KNOWARTH Technologies Pvt. Ltd.


Features Of Magento 2

9

Enhanced and Advanced coding Architecture

More extensive APIs Upgrading Magento become easy Enhanced checkout flow Easier checkout process Support Full page caching out of

box Less preprocessor based UI library Improved indexing Performance Toolkit Built-in support for Varnish cache

© 2016 KNOWARTH Technologies Pvt. Ltd. 10

Why Migrate to Magento 2.0

BetterCheckout

Built-in supportfor varnish

Revamped admin interface

Performance Improvements

Use of Advanced technology stack

Magento will stop giving support to

Magento 1 after 2018


Who Should Upgrade

11

Merchants who wants to keep their Website up-to-date with latest Magento version

Merchants who wants to take Benefit of added features of Magento

Merchants who is having performance issues with the current Magento website


Migration Process

Migration Process

Migrating Extensions

Migrating Themes

Migrating Custom Development

Migrating Settings

Migrating Sales Info, Catalog, Customers, Promotional Info, CMS Pages

Migrating Code Migrating Database


Magento’s Migration Process does not Includes Migrating Media Migrating Store Front Design (Css Files, Js Files,

Static Images) Migrating ACL (API Roles and Permission) Migrating Admin Users

Migration Process


Migration Steps

14

Customization, Extension Integration, Migration Dry Run

Step 1

Start Migration Process & Stop Admin Activity

Step 2

Stop Crons on Magento 1 Site

Step 3

Test Magento 2 Site

Step 8

Point Your DNS to Magento 2 Site And Site is Running

Step 10

Start Incremental Updates

Step 7

Run Indexes andFlush Cache

Step 5

Copy Media Files andCss, Js File data onMagento 2 Store

Step 4

Test Magento 2 Site

Step 6

Stop Incremental Update, cache and Re-index

Step 9


Prerequisite for Migration

15

Downloading Code Migration Tool Download code migration tool from https://github.com/magento/code-migration to your web

root directory Apply composer install command to inside code-migration folder to update and download

dependency Migrating from Magento 1.x to 2.0 has been made easy by the tools provided Before we start the migration we should download those tools

https://github.com/magento/code-migration


Downloading Code Migration Tool source directory containing code to be

migrated. source directory should not have core files and

must be in magento's directory structure destination directory where converted code will

be copied magento1 directory containing magento's

vanilla version and custom code that need to be migrated

directory containing magento 2 vanilla version




17

Downloading Data Migration Tool Need to setup magento 2 system no need to start

cron jobs Collect DB details of both Magento 1.x and Magento

2.x system get the version of your magento2.x and Magento

1.x The versions of the Data Migration Tool and your

Magento software must exactly match.



18

go to the root directory of magento 2 and apply commands as shown below. Command 1:

composer config repositories.data-migration-tool git https://github.com/magento/data-migration-tool

Command 2: composer require magento/data-migration-tool:<version>

<version> is the version of your magento 2.x system

https://github.com/magento/data-migration-tool



19

go to vendor/magento/data-migration-tool/etc/<migration edition>/<ce or version> rename config.xml.dist to config.xml and open the file update db info for source and destination


Migration Extensions

20

Find out if extension provider has created module in m2

If any change in db schema of m2 module then need to add it in data migration configuration file (map.xml)

If m2 version of extension is not available then need to migrate module manually or through code migration tool


Code Migration Tool

21

Code migration has been divided in four steps

Directory Structure Migrate

MigratingLayout

MigratingConfiguration

MigratingPHP Code


Code Migration Tool

22

After configuring code migration tools, below command need to be run for migrating php bin/migrate.php migrateModuleStructure <src> <dst> .


Code Migration Tool

After configuring code migration tools, below command need to be run for migrating php bin/migrate.php migrateModuleStructure <src> <dst> .

It will create module structure at destination to allow code migration in next steps) php bin/migrate.php convertLayout <dst>


Code Migration Tool

This will convert layout files as per magento 2 standard, individual xml for each action) php bin/migrate.php convertConfig <dst> . This step will convert configuration to magento 2, it will create separate files for events, routes, system

configuration etc. php bin/migrate.php convertPhpCode <dst> <m1> <m2> . (This is final step and will copy business logic from m1 version to m2 version, basically convert syntax of mage class to class path as per m2 standard)


There are no default tools available for theme migration

Theming in magento 2 is completely different then magento 1 as magento 2 is using less pre-processors and modularise structure of template

Will require frontend developer to migrate theme to m2

Theme Migration


Data Migration Tool

26

Migrating Data is divided in three parts:

Migrating Settings

Migrating Data

Migrating Delta


Data Migration Tool

27

Migrating Settings Some settings are ignored, some settings path need to be

renamed, some setting requires changing value like encrypted data as key changes in magento2.

vendor\magento\data-migration-tool\etc\ce-to-ce\setting.xml file contains information of settings changes

If any other custom settings has been generated, it will transfer

automatically to the magento2 as migration process run. Need to

add in ignore list if do not want it in magento2

Changes made in other core settings will be automatically be

transferred to magento2

Command to run Setting migration

Configuration which has not been modified in magento 1.x will

not be migrated. they may be different in magento 2

php bin/magento migrate:settings --reset D:\xamp\htdocs\

m2\vendor\magento\data-migration-tool\etc\ce-to-ce\

1.9.2.1\config.xml .


Data Migration Tool

28

Migrating Data If any custom column added need to add it in map.xml for ignoring it or transforming it to

magento2. You can rename document (table), rename field using field_rules =>move or transform using

handlers. For custom logic, you may have to write custom handlers php bin/magento migrate:data --reset D:\xamp\htdocs\m2\vendor\magento\data-

migration-tool\etc\ce-to-ce\1.9.2.1\config.xml .


Data Migration Tool

29

Migrating Delta While migrating live sites, there are some data which

keep updating throughout day like order information, customer information etc

So to migrate those changes which has been made post migration, magento provide Delta migration


Benchmarking

177kProducts

355kOrders

214kCustomers

Performance Results Settings migration time: ~10 mins Data migration time: ~9 hrs (all data except URL Rewrites, ~85% of total data) Site downtime estimate: A few minutes to reindex and change DNS settings. Additional

time required to “warm up” the page cache

KNOWARTH’s Migration Projects Executed

6000Products

1000+Orders

570Customers

Online Grocery Store

2500Products

250Customers

Online Art Gallery

100+Orders

42categories

Email us: [email protected]



THANK YOU

KNOWARTH Technologies Pvt. Ltd.INDIA: 11, Aryan Corporate Park, Nr. Shilaj Railway Crossing, Thaltej, Ahmedabad – 380059, Gujarat, INDIA

USA: One Commerce Center, 1201 Orange Street #600, Wilmington, DE – 19899

Email: [email protected] | Website: www.knowarth.com

mailto:[email protected]

http://www.knowarth.com/

https://plus.google.com/+KnowarthTechnologies

https://www.facebook.com/knowarth

https://twitter.com/KNOWARTH

http://www.linkedin.com/company/knowarth-technologies