Académique Documents
Professionnel Documents
Culture Documents
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.
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 Solution
You might want to continue using Recreate your Magento 1
Magento 1 design template since all of theme: Creating a new Magento 2
your customers are too familiar with it. design template that looks the same
with your old version (based on your PSD
However, its unfortunate that we cannot files).
migrate that theme to Magento 2.
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 Solution
In general, the majority of custom code You need to create a detailed
used by your Magento 1 store is migration plan and follow it strictly to
compatible with Magento 2. Therefore, to make sure that it meets the code
transfer it to the new version, you are standard and data integrity
optional to either rewrite or migrate the throughout the migration process.
code.
Problem Solution
Most of the Magento 1 extensions are not Find those extensions with Magento 2
transferable to Magento 2 due to the version: If your Magento 1 extensions have
code conflicts. already developed with the same functions in
Magento 2, you to can find and install them
in your new store.
Problem Solution
Data Migration is the most crucial stage If your internal developers do the
of the migration process. migration, be careful of data loss,
especially customer data.
Though Magento allows us to transfer
several types of data from your Magento Otherwise, you can turn to a
1 to Magento 2, this work is very professional Magento agency to
complicated, which requires strenuous ensure a smooth data transference.
attempt and massive undertaking.
Create Migration Plan
Step 1: Check the migration tool Step 2: Inspect your Magento 1 site
Step 3: Make capacity plan Step 4: Set up & test Magento 2 site
Notes: Dont migrate Indexed data, Google shopping and Unsupported data in Magento 2 (poll,
tag, staging module, etc.)
MAGENTO MIGRATION
COMMON ISSUES
1. Source documents/ fields
are not mapped
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
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
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
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?
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?
Website: https://www.tigren.com/
Email: info@tigren.com
Phone: (+84)1664988448