Migrate From Magento 1 to Magento 2

Mo May 21, 2023

Migrate_From_Magento_1_to_Magento 2

Hello Everyone! This is Mo. Today’s blog deals with the Migration of Magento 1 to Magento 2.


    Are you still running your eCommerce Store with Magento 1, to notify you that Adobe officially

announced the termination of Magento 1 support, the eCommerce store needs to be

maintained by us, hope you all are aware of this. 


    Migrating your store from Magento 1 to Magento 2 will give you access to multiple great

features and enhancements like better site performance, advanced SEO, improved checkout,

strong security, and marketing automation.


In this blog, we are going to explain how to migrate your Magento 1 to Magento 2


A QUICK OVERVIEW OF THE MIGRATION PROCESS

We will divide the complete process into 3 parts namely pre-migration, migration, and

post-migration.


Pre-migration: In this step, we need to have a clear idea about the data and the content,

also the manual labor work.


Migration: This is the major step in this process we need to set up a Magento 2 environment

then we need to move themes, extensions, plugins, data, and content from Magento 1 to

Magento 2.


Post-Migration: In this step, we need to synchronize the order, product, and customer data

from Magento 1 to Magento 2.

MAGENTO 2 DATA MIGRATION

    Magento 2 data migration is the critical part and we need to have enough technical knowledge and need to react quickly in case of loss of database assets like the customer, order, and product data. or the block content etc.

    Data migration from Magento 1 to Magento 2 is not just the process of copying the data from Magento 1 and pasting it into Magento 2 so we will explain to you the process of how to do the data migration from Magento 1 to Magento 2

Data Migration Tool             

            Install the data migration Tool in your Magento directory 


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

            Where <version> must match the version of the Magento 2 codebase.

     For example, for version 2.1.2, enter:


           $ composer require magento/data-migration-tool:2.1.2 

           Now we need to   configure the data migration tool

  • Magento Open Source:

    <your Magento 2 install dir>/vendor/magento/data-migration-tool/etc/

opensource-to-opensource: Configuration and scripts for migrating from

Magento Open Source 1 to Magento Open Source 2

  • Magento Commerce:

    <your Magento 2 install dir>/vendor/magento/data-migration-tool/etc/

opensource-to-commerce: Configuration and scripts for migrating from

Magento Open Source 1 to Magento Commerce 2


<your Magento 2 install dir>/vendor/magento/data-migration-tool/etc/

commerce-to-commerce: Configuration and scripts for migrating from

Magento Commerce 1 to Magento Commerce 2


In this blog, We are going to explain configure migration in the vendor folder

  • Log in to the Magento server and move to the following dire

$ <your Magento 2 install dir>/vendor/magento/data-migration-tool/etc/

<migration edition>/<ce or version>

  • Create the config.xml from the provided sample

       $ cp config.xml.dist config.xml

  • Open the Open config.xml in a text editor.
<source>

   <database host="127.0.0.1" name="magento1" user="root" password="pass"/>

</source>

<destination>

   <database host="127.0.0.1" name="magento2" user="root" password="pass"/>

</destination>

<options>

   <source_prefix>magento1</source_prefix>

   <crypt_key>f3e25abe619dae2387df9fs594f01985</crypt_key>

</options>


The tag must contain a value present in the app/etc/local.xml file on your Magento 1

instance


    Where magento1 is the database that contains Magento 1 data and magento2 is the

database that contains normal Magento 2 setup

MAPPING FILES

    The Data Migration Tool uses Mapping files to enable you to perform custom database

mapping between your Magento 1 and Magento 2 databases, including changing table names,

changing field names, ignoring tables or fields, adapting or transferring data of a field to

Magento 2 format.

    Mapping files for supported Magento versions are located in subdirectories of

<your Magento 2 install dir>/vendor/magento/data-migration-tool/etc

To use the mapping files:

  • Copy them from <your Magento 2 install

<dir>/vendor/magento/data-migration-tool/etc/<migration edition>/<ce or version>/ to

<your Magento 2 install dir>/app/code/Vendor/Migration/etc/<migration edition>/<ce

or version>/ and remove the .dist extension.

  • Update the path to the newly copied file in the <options> node of config.xml. 

The updated path should be one of the following:

  • The absolute file path, e.g. /var/www/html/app/code/Vendor/Migration/etc/opensource-to-opensource/1.9.4.1/map.xml

  • magento/data-migration-tool module relative file path: etc/opensource-to-opensource/1.9.4.1/map.xml

  • Magento root-relative file path: app/code/Vendor/Migration/etc/opensource-to-opensource/1.9.4.1/map.xml


The <Magento 2 dir>/vendor/magento/data-migration-tool/etc and

<Magento 2 dir>/vendor/magento/data-migration-tool/etc/<ce version>

directories contain the following configuration files:

MIGRATION USING DATA MIGRATION TOOL

  • Migrate Settings

First, we will migrate the settings from Magento 1 to Magento 2

For Migrating settings, run:

 $ bin/magento migrate:settings [-r|--reset] [-a|--auto] {<path to config.xml>}


Forexample, if you migrating settings from Magento 1.9.3.4 opensource to Magento 2. x.x commerce


$ bin/magento migrate:settings -r -a 

vendor/magento/data-migration-tool/etc/opensource-to-commerce/1.9.3.4/config.xml

Note: run $ bin/magento cache: clean and check your home page if you found that your

home page is going for 302 then connect to your database and select your Magento 2

database and check for the offload row in the core_config_data table if you found an offload

then delete it. delete from core_config_data where path like "%offload%";

  • Migrating Data

Now in this step, we will explain how to transfer the Magento1 Data to Magento 2.

For Migrating data, run:


$ bin/magento migrate:data [-r|--reset] [-a|--auto] {<path to config.xml>}


ForExample,


if you migrate data from Magento 1.9.3.4 opensource to Magento 2. x.x commerce


$ bin/magento migrate:data -r -a 

vendor/magento/data-migration-tool/etc/opensource-to-commerce/1.9.3.4/config.xml


Tip: migrating data is more time-consuming when compared to migrating settings so 

Instead of running 


$ bin/magento migrate:data -r -a 

vendor/magento/data-migration-tool/etc/opensource-to-commerce/1.9.3.4/config.xml


Run the same command with some modification


$ bin/magento migrate:data -r -a 

vendor/magento/data-migration-tool/etc/opensource-to-commerce/1.9.3.4/config.xml >

pub/media/data-migration.log &

So that you can run the process in the background if you need to know the status of your data migration check your data migration log file I,e data-migration.log

SEO PERFORMANCE AFTER MAGENTO MIGRATION

    Search engine optimization (SEO) can break your eCommerce business. Magento 2

has introduced many improvements to SEO, such as Auto-Generation and Schema.org

features.

    Auto-Generation is aimed to set templates for product metadata, and Schema.org could help

to boost the search engine ranking of your eCommerce store. Many merchants choose

Magento 2 specifically for its advanced SEO features.


    The loss of search engine traffic can harm the rankings in the SERPs (search engine results pages) and could cost you a pretty penny. If you don’t migrate

properly, the following problems can happen:


• Broken URLs

• Lost pages

• Duplicate content

• Redirects that don’t work


When any of these occur, your marketing strategies will be affected adversely, so to rank high

on Google again will be a daunting task.


Note:     Google Webmaster tools like Search Console and Analytics can help you to overcome SEO barriers and retain your rankings. With those tools, you can find all of the existing 404 error

pages and fix them by applying 301 redirects, and formatting all internal links based on the

Magento 2 rules, and sorting all canonical URLs to avoid duplicate content.

EXTENSIONS IN MAGENTO 2 ENVIRONMENT

    We cannot copy the same extensions that are running in Magento 1 store to Magento2.

Most of the Magento 1 extensions have been created for Magento 2, so its quite easy to

migrate settings and data but if Magento 1 extensions have been not created in Magento 2 we

need to find the Magento 2 Extensions That have similar features


TIME TO THINK ABOUT NEW DESIGN


    Migration is the perfect time to think of refreshing the design and to rethink about customer

experience. Just like extensions Magento 1 templates are incompatible with Magento.

The reason is that Magento 2 uses modern architecture and has different front-end and

back-end requirements, so it’s impossible to convert the code built into your Magento 1 theme.

 

Thank you for reading. Are you fascinated to know more about Magento,

What are you waiting for? Check out the other blogs in the Magento section and

follow us through Youtube and Instagram to know more about us.

Tags
Mo

Posted by Mo

Hello, everyone! This is MO, I am a techie by profession. A traveler with a love/hate relationship with food. I intend to share my experience with technology, food, travel, and many other topics on this website.

Post a Comment

0 Comments