Prerequisite<\/strong>
\nInstall new Magento 2 environment in the server.
\nStop Magento2 cron Jobs
\nBackup the Magento 2 database.
\nCheck the data migration access to both Magento 1 and Magento 2 databases.<\/p>\n Installation, Configuration and Mapping<\/strong>
\nData Migration tool is not an extension, it is shell app which requires Magento2 Framework to work. We can get data migration tool from git hub only for community edition.<\/p>\nInstall from Github<\/strong><\/p>\n\n- composer config repositories.data-migration-tool git<\/li>\n
- https:\/\/github.com\/magento\/data-migration-tool-ce<\/li>\n
- composer require magento\/data-migration-tool:dev-master
\nAfter installation, the following directory contains mapping and configuration file<\/li>\n - <your Magento 2 install dir>\/vendor\/magento\/data-migration-tool\/etc\/ce-to-ce<\/em><\/li>\n<\/ul>\n
Configuration.<\/strong><\/p>\n\n- Choose the right folder based on the Magento versions.<\/li>\n
- Copy the config.xml.dist to config.xml<\/li>\n<\/ul>\n
<source>\u00a0\u00a0\u00a0 <database host=”127.0.0.1″ name=”magento11302″ user=”root” password=”pass”\/><\/source><destination>\u00a0\u00a0\u00a0 <database host=”127.0.0.1″ name=”magento2″ user=”root” password=”pass”\/><\/destination><options>\u00a0\u00a0\u00a0\u00a0 <crypt_key>f3e25abe619dae2387df9fs594f01985<\/crypt_key><\/options><\/em><\/p>\n\n- Source \u2013 Database details and its credentials of Magento 1.X,<\/li>\n
- Destination \u2013 Database Details and it credentials of Magento 2.X<\/li>\n
- crypt_key \u2013 Encryption key from Magento 1.X (local.xml).<\/li>\n<\/ul>\n
Mapping Files<\/strong>
\nData Migration tools uses mapping file to enable us to perform custom mapping between Magento 1 and Magento 2 which including changes in table name and field name, ignoring tables and fields and Transferring the table \/ field.
\nFollowing picture is an example of Map configuration file<\/p>\nMAP Steps<\/strong><\/p>\n\n- Based on the Configuration file chosen, copy the map.xml.dist to map.xml<\/li>\n
- Make necessary changes in Config.xml<\/li>\n
- Transferring most of data from Magento 1 to Magento 2<\/li>\n
- This step reads instructions from map.xml<\/li>\n<\/ul>\n
Areas:<\/strong><\/p>\n\n- Source – contains rules of source database<\/li>\n
- Destination – contains rules of destination database<\/li>\n<\/ul>\n
Options:<\/strong><\/p>\n\n- ignore – document, field or data type marked with this option will be ignored<\/li>\n
- rename – describes name relations between documents with the different name. In a case when destination document name is not the same with the source document – you can use rename option to set source document name similar to destination table name<\/li>\n
- move – sets rule to move specified field from source document to destination document. NOTE: destination document name should be the same with the source document name. If source and destination document names are<\/li>\n
- different – you need to use rename option for document that contains moved field<\/li>\n
- transform – is a option that allows user to migrate fields according to behavior described in handlers<\/li>\n
- handler – describes transformation behavior for fields. To call the handler you need to specify<\/li>\n<\/ul>\n
Run the Data Migration Tool<\/strong>
\nCommand
\nbin\/magento migrate: [-r|–reset] {}
\n– settings \/ data \/ delta.<\/p>\nThe Data Migration Tool saves its current progress as it runs. If errors or user intervention stop it from running, the Data Migration Tool resumes progress at the last known good state.<\/p>\n
Manual Migration (Media, Storefront design and ACLs)<\/strong><\/p>\nMedia<\/strong><\/p>\nAll media files (for example, images for products, categories, the WYSIWYG editor, and so on) should be copied manually from \/media to \/pub\/media.
\nHowever, do not copy .htaccess files located in the Magento 1 media folder.
\nMagento 2 has its own .htaccess that should be preserved.<\/p>\n
Storefront Design<\/strong><\/p>\n\n- Design in files (css, js, templates, XML layouts) changed its location and format<\/li>\n
- Layout Updates stored in database. Placed through Magento 1 Admin in CMS Pages, CMS Widgets, Category Pages and Product Pages<\/li>\n<\/ul>\n
ACLs (Access Control Lists)<\/strong><\/p>\n\n- You must manually re-create all credentials for web services APIs (that is, SOAP, XML-RPC, and REST)<\/li>\n
- You must manually re-create all administrative users and associate them with access privileges<\/li>\n<\/ul>\n
After Migration<\/strong>
\nStart Magento 2 CRON jobs
\nFlush all Magento 2 cache types<\/p>\n
![\"\"](\"https:\/\/www.sureshselvam.com\/wp-content\/uploads\/2017\/09\/M2-Data-migration.jpg\")
<\/a>