Magento 2 Migration From A to Z

1
MAGENTO 2 MIGRATION FROM A TO Z
2
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

3
Why Migrating Magento 1 to 2?
4
MIGRATION PROCESS
5
4 Stages of Migration Process
6
Theme Migration

• Problem

• Solution

• 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.

• 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.

7
Code Migration

• Problem

• Solution

• 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.
• 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.

• 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.

8
Extension Migration

• Problem

• Solution

• Most of the Magento 1 extensions are not
  transferable to Magento 2 due to the code
  conflicts.

• 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.

9
Data Migration

• Problem

• Solution

• 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.

• 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.

10
Create Migration Plan
11
Create Migration Plan
12
Create Migration Plan
13
Create Migration Plan
14
How Migration Works

• Automatic Migration

• Manually 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.

• 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)

Notes Dont migrate Indexed data, Google
shopping and Unsupported data in Magento 2 (poll,
tag, staging module, etc.)
15
MAGENTO MIGRATION COMMON ISSUES
16
1. Source documents/ fields are not mapped

• Source documents are not mapped
• ltEXTENSION_TABLEgt
• Source fields are not mapped. Document
• ltEXTENSION_TABLEgt
• Fields
• ltEXTENSION_FIELDgt
• 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.

17
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 ltignoregt tag
  to an entity in the map.xml file, like this
• ltignoregt
• ltfieldgtsales_order_address_idlt/fieldgt
• lt/ignoregt
• Before ignoring entities, make sure you do not
  need the affected data in your Magento 2 store.

18
2. Class does not exist but mentioned

• Class
• ltextension/class_namegt
• does not exist but mentioned in
• lteav_attribute.frontend_modelgt
• for
• ltattribute_id196gt
• 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

19
3.  Foreign key constraint fails

• Error message text
• Foreign key
• ltKEY_NAMEgt
• constraint fails.Orphan records id ltid_1gt,
  ltid_2gt from ltchild_tablegt.ltfield_idgt has no
  referenced records in ltparent_tablegt
• 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.

20
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.

21
5.  Mismatch of entities

• Mismatch of entities in the document
• ltDOCUMENTgt
• 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.

22
MIGRATION SERVICES
23
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.
24
Where to find a reliable Magento agency?
Website https//www.tigren.com/ Email
info_at_tigren.com Phone [phone]