Skip to main content

magento 1.9 to magento 2.X migration process using migration tool

According to the official Magento documentation, migration to the Magento 2 consists of four different stages:
  1. Theme Migration
  2. Extension Migration
  3. Customizations
  4. Data Migration

Theme Migration

Magento 2 introduces new methodologies and technologies for delivering enhanced shopping and store experience to the merchants and users. Developers can take advantages of new ways of creating awesome Magento 2 themes or modify the current ones to make them compatible with the Magento 2 standards. You should keep in mind that you cannot directly migrate your Magento 1 theme to Magento 2.
You have to create a new theme for Magento 2 and make it responsive for the best user experience. 
If you wish to avoid all this hassle, buy and install a Magento 2 theme from the Magento Marketplace or from other reputed sources.

Extension Migration

Extensions are essential components that provide new features and extend the functionalities of your Magento store. The next step in Magento migration process is to install the desired Magento 2 extensions available on Magento Marketplace.
Remember that, Magento 1 extensions will not work on Magento 2. You will experience severe compatibility issues while integrating Magento 1 extensions into Magento 2.
Only install the relevant extensions that are available and required for your Magento 2 stores. The Magento developers, community and development agencies are still working hard on porting Magento 1 extensions to Magento 2.
Customization
In many cases, the custom code used by your Magento 1 store is compatible with Magento 2. Magento offers a Code Migration Toolkit that helps you in this process. It should be noted here that due to structural differences in the two platforms, This Magento migration may require additional work to make sure that the custom code successfully integrates with the Magento 2 store.
To know more about the integration, visit the GitHub repository of Magento Code Migration Toolkit.

Data Migration

The last action you need to perform during Magento migration process is moving your Magento 1 settings and data to Magento 2. Magento provides a Magento 2 Data Migration Tool which makes the migration process hassle free. This fantastic tool helps in migrating critical data (products, categories, orders, store configurations & settings, etc.) to Magento 2.
To perform a successful data migration, follow these guidelines:
Step 1 : Installing data-migration-tool
                composer config repositories.magento composer https://repo.magento.com
                composer require magento/data-migration-tool:<version>
                NOTE : where <version> is either an exact version of magento  or next significant release.
                                EX : composer require magento/data-migration-tool:2.1.0
Step 2 : Configure Data Migration Tool
·         contains configuration and scripts for migrating from Magento 1 Community Edition to Magento 2 Community Edition
Path : <Magento 2 root dir>/vendor/magento/data-migration-tool/etc/ce-to-ce
·         contains configuration and scripts for migrating from Magento 1 Community Edition to Magento 2 Enterprise Edition
Path : <Magento 2 root dir>/vendor/magento/data-migration-tool/etc/ce-to-ee
·         contains configuration and scripts for migrating from Magento 1 Enterprise Edition to Magento 2 Enterprise Edition
Path : <Magento 2 root dir>/vendor/magento/data-migration-tool/etc/ee-to-ee
if you are performing data migration from Magento 1 CE to Magento 2 CE, navigate to the “<Magento 2 root dir>/vendor/magento/data-migration-tool/etc/ce-to-ce/<Magento 1.x version>” directory and rename “config.xml.dist” to “config.xml”.
Step 3 : open config.xml in your favorite code editor and specify the following :
<source>
<database host="localhost" name="Magento1-DB-name" user="DB-username" password="DB-password"/>
</source>
<destination>
<database host="localhost" name="Magento2-DB-name" user="DB-username" password="DB-password"/>
</destination>
<options>
<crypt_key>Magento1-Encrypted-Key</crypt_key>
</options>
In the above code, <source> has the database information of Magento 1 and <destination> has the relevant information of Magento 2. <crypt_key> is mandatory to fill in. It is the encryption key of Magento 1 which can be found in “<Magento 1 root dir>/app/etc/local.xml”  file in <key> tag.

Step 4 : Migrate Settings :
                Command : php bin/magento migrate:settings --reset <path to your config.xml>
where <path to your config.xml> this would be vendor/magento/data-migration-tool/etc/ce-to-ce/<Magento 1.x version>/config.xml. I have used --reset argument in the above command which forces the Data Migration Tool to start from the beginning.
Step 5 : Migrate Data :
                Command : php bin/magento migrate:data --reset <path to your config.xml>
Step 6 :  Migrate Success Test the Magento 2 store completely

Comments

  1. Unknown26 October 2018 at 05:55

    thank for your artical, it is very useful for my code

    ReplyDelete
  2. Web Developer17 July 2020 at 03:24

    Migration to Magento can be confusing for some non-technical users. Read more to learn about an easy procedure for Magento 2 migration.

    ReplyDelete

Post a Comment

Popular posts from this blog

magento 1 extension converted in to magento 2 process

Simple Install =================================== Download as a zip below link. unzip and upload it to your public_html or other rootdoc directory. https://github.com/magento/code-migration. login to your server via shell switch to the code-migration-develop directory by running following command   cd code-migration-develop Run command following command in root directory of this toolkit composer instal Before running the migration, the following directories need to be prepared: ===================================== * `<src>` - Directory that contains custom Magento 1.x code that is intended to be migrated. The code must follow the Magento 1.x directory structure.   Magento1.x core files must not be included. * `<dst>` - Empty directory for the toolkit to put the generated Magento 2 code to * `<m1>` - Directory that contains: * Vanilla Magento 1.x codebase, and * Custom Magento 1.x code same as...
11 comments
Read more

Magento 2 product collection Filtering multi-select attribute values

  If you have multi-select attribute of product like below If you want filter value for this option Use below syntax to get product data: ->addAttributeToFilter('store_model', array('finset' => $params['store_model'])) finset key is used for multiselect attribute filter. $objectManager = \Magento\Framework\App\ObjectManager::getInstance(); $products = $objectManager->get('Magento\Catalog\Model\Product')         ->getCollection()         ->addAttributeToSelect('*')         ->addAttributeToSelect('store_brand')         ->addAttributeToSelect('store_model')         ->addAttributeToSelect('store_year')         ->addAttributeToFilter('store_brand', array('finset' => $params['store_brand']))         ->addAttributeToFilter('store_model', array('finset' => $params['store_model']))         ->ad...
6 comments
Read more

Magento Debug HEADERS ALREADY SENT error

When you  receiving the following error in  system.log file: app\code\core\Mage\Core\Controller\Response\Http.php:44  [1] \www.pawan.com\lib\Zend\Controller\Response\Abstract.php:727  [2]  \www.pawan.com\app\code\core\Mage\Core\Controller\Response\Http.php:75  [3]  \www.pawan.com\app\code\core\Mage\Core\Controller\Varien\Front.php:188  [4]  \www.pawan.com\app\code\core\Mage\Core\Model\App.php:304  [5]  \www.pawan.com\app\Mage.php:596  [6]  \www.pawan.com\index.php:81 if you have no idea what file is causing this. Here is the steps to debug. That error is thrown from Mage_Core_Controller_Response_Http -> sendHeaders(). This function calls the super class function that actually does the check to see whether or not headers have already been sent, Zend_Controller_Response_Abstract -> canSendHeaders(). The Zend_Controller_Response_Abstract class handles, among other things, sending response header...
6 comments
Read more