MAGENTO

MIGRATION
EVERYTHING THAT MAGENTO STORE OWNERS/
DEVELOPERS NEED TO KNOW
 Overview

When Magento 2 was first released, many people doubt about its stability
and adaptability. Therefore, most of the e-commerce businesses choose to
keep running on Magento 1 instead of taking risks.
However, since Magento 2 continues releasing many update versions with
an array of attractive features and functions, better from time to time,
migrating website to Magento 2 has become a hot controversy than ever.

Magento Migration process is actually to

Build a new website on Magento 2
framework based on your Magento 1 site
 Why Migrating Magento 1 to 2?

More User-
Improved Enhanced Better Admin More Mobile- Continuous
friendly
Performance Security Interface friendly Improvements
Checkout
MIGRATION
PROCESS
4 Stages of Migration Process

Data
Migration
Extensions
Migration
Code
Migration
Theme
Migration
Theme Migration
Problem
You might want to continue using
Magento 1 design template since all of
your customers are too familiar with it.
However, its unfortunate that we cannot
migrate that theme to Magento 2.
Solution
Recreate your Magento 1
theme: Creating a new Magento 2
design template that looks the same
with your old version (based on your PSD
files).
Redesign the whole store: Why dont
you think this is a perfect time to refresh
your store? By hiring a creative team of
coders and designers, they will give you
a more appealing and modern
storefront but still stick on your brand
image.
Code Migration

Problem
In general, the majority of custom code
used by your Magento 1 store is
compatible with Magento 2. Therefore, to
transfer it to the new version, you are
optional to either rewrite or migrate the
code.
Solution
You need to create a detailed
migration plan and follow it strictly to
make sure that it meets the code
standard and data integrity
throughout the migration process.

The thing is that although Magento offers

some available code migration tools, it
still requires extreme work to ensure that
these tools are successfully installed in
your Magento 2 store.
Extension Migration

Problem
Most of the Magento 1 extensions are not
transferable to Magento 2 due to the
code conflicts.
Solution
Find those extensions with Magento 2
version: If your Magento 1 extensions have
already developed with the same functions in
Magento 2, you to can find and install them
in your new store.

Develop new custom Magento 2 extensions

for your store: In case there is no available
Magento 2 version for your current Magento 1
extensions, you can hire a Magento
extensions development agency to create a
new one with the same functionality.
Data Migration
Problem
Data Migration is the most crucial stage
of the migration process.
Though Magento allows us to transfer
several types of data from your Magento
1 to Magento 2, this work is very
complicated, which requires strenuous
attempt and massive undertaking.
Solution
If your internal developers do the
migration, be careful of data loss,
especially customer data.
Otherwise, you can turn to a
professional Magento agency to
ensure a smooth data transference.
Create Migration Plan

Step 1: Check the migration tool Step 2: Inspect your Magento 1 site

Make sure that the data migration tool has a

Review the existing extensions and decide
network connection to Magento 1 & 2
what to migrate to the new site
databases

Check whether these extensions has Magento

Open ports in your firewall
2 versions

Define which database assets from these

Disable Magento 2 cron jobs
extensions to migrate

Configure and map files

Create Migration Plan

Step 3: Make capacity plan Step 4: Set up & test Magento 2 site

Determine to design the new Magento 2 store

with more hardware or more advanced Set up Magento 2 system
topology with better caching tiers

Enhance migration performance by cutting

down network latency

Replicate Magento 1 database to create

redundancy in the event of unpredictable
issues
Create Migration Plan

Step 5: Start Magento 2 Step 5: Start Magento

Migration 2 Migration

Cease all activities in Magento 1 admin

(order management and shipping are Do bulk copy of database
excluded)

Stop cron jobs of Magento 1 Reindex Magento 2 indexers

Migrate settings and websites by

utilizing the Magento migration tool Examine the new site

Copy media assets from Magento 1 to

2
Create Migration Plan

Step 6: Deliver additional Step 7 : Scrutinize the new

updates site and go live

Update the customers, inventory, Start downtime and set Magento 1

orders site to maintenance mode

Stop incremental updates

Kick Magento 2 cron jobs off

Reindex all Magento 2 indexers

Conduct eventual verification

Finish downtime by changing DNS

and loading balancers
How Migration Works
Automatic Migration
Both Magento 1 core tables and any
custom tables that do not change
between Magento 1 and Magento 2 are
automatically migrated to Magento 2
with no action required.
Notes: Dont migrate Indexed data, Google shopping and Unsupported data in Magento 2 (poll,
tag, staging module, etc.)
Manually Migration
Extensions and custom code
Media (product images, WYGIWYS editor,
etc.)
Storefront design (CSS, Javascript,
templates, XML layouts)
Layouts (XML in CMS category pages &
Layout updates)
Web services credentials (SOAP, XML-
RPC, REST)
MAGENTO MIGRATION
COMMON ISSUES
1. Source documents/ fields
are not mapped

Source documents are not mapped:

<EXTENSION_TABLE>
Source fields are not mapped. Document:
<EXTENSION_TABLE>
Fields:
<EXTENSION_FIELD>
In rare cases, the message might mention Destination documents or Destination fields instead of source
ones.

Explanation
Some Magento 1 entities (in most cases, coming from extensions) do not exist in the Magento 2
database.
This message appears because the Data Migration Tool runs internal tests to verify that tables and fields
are consistent between source (Magento 1) and destination (Magento 2) databases.
1. Source documents/ fields
are not mapped

Possible solutions
Install the corresponding Magento 2 extensions from Magento Marketplace.
If the conflicting data originates from an extension which adds own database structure
elements, then the Magento 2 version of the same extension may add such elements to the
destination (Magento 2) database, thus fixing the issue.
Configure the Tool to ignore the problematic data.
To ignore database entities, add the <ignore> tag to an entity in the map.xml file, like this:
<ignore>
<field>sales_order_address_id</field>
</ignore>
Before ignoring entities, make sure you do not need the affected data in your Magento 2
store.
 2. Class does not exist but
mentioned
Class
<extension/class_name>
does not exist but mentioned in:
<eav_attribute.frontend_model>
; for
<attribute_id=196>

Explanation
A class from Magento 1 codebase could not be found in Magento 2 codebase during the
EAV migration step. In most cases, the missing class belongs to an extension.

Possible solutions
Install the corresponding Magento 2 extension.
Ignore the attribute that causes the issue.
For this, add the attribute to the ignoregroup in the eav-attribute-groups.xml.dist
Add class mapping using the class-map.xml.dist
 3. Foreign key constraint fails

Error message text

Foreign key
<KEY_NAME>
; constraint fails.Orphan records id: <id_1>, <id_2> from <child_table>.<field_id> has no
referenced records in <parent_table>

Explanation
There are missing database records in the parent_table to which the field_id of the
child_table is pointing to.

Possible solution
Delete the records from the child_table, if you do not need them.
To keep the records, disable the Data Integrity Step by modifying the Data Migration
Tools config.xml.
 4. Duplicates in URL rewrites

There are duplicates in URL rewrites:

Request path: towel.html Store ID: 2 Target paths: catalog/product/view/id/10
Request path: towel.html Store ID: 2 Target paths: catalog/product/view/id/12

Explanation
The Target path in a URL rewrite must be specified by a unique pair of Request path + Store
ID. This error reports two entries that use the same Request path + Store ID pair with two
different Target path values.

Possible solution
Enable the auto_resolve_urlrewrite_duplicates option in your config.xml file.
This configuration adds a hash-string to the conflicting records of URL rewrites, and shows
the resolution result in your command line interface.
 5. Mismatch of entities

Mismatch of entities in the document:

<DOCUMENT>

Explanation
The error occurs during the Volume Check step. It means the Magento 2 database record
count of the document is not the same as in Magento 1.
Missing records happen when a customer places an order during migration.

Solution
Run the Data Migration Tool in Delta mode to transfer incremental changes.
MIGRATION
SERVICES
Why hiring a Magento agency?

Internal Staff vs Magento Agency

Less professional

Take more time

Higher risk of data loss

during migration process

May cost even more

Less time to focus on more

important things

Magento 2 migration process takes a lot of time and effort since it is complex and requires plenty
of customizations. This is the main reason why you should find a reputable Magento migration
service provider to share your burden rather than do it yourself.
Where to find a reliable
Magento agency?

Founded in 2011, specialized in Magento development

Magento Certified Developers, 4-5-year experience on

Magento on average

Offer competitive pricing

Guarantee a smooth & data loss-free Migration process

with minimum lead time

World-class customer service 24/7/365 support

Website: https://www.tigren.com/
Email: info@tigren.com
Phone: (+84)1664988448