Rate this post

Magento will end support for Magento 1 by June 2020. That’s why many users are migrating their Magento 1 store to Magento 2 store. However, Magento 1 to Magento 2 migration can be a challenging project. During the migration process, you can come up against issues since this procedure is extremely unpredictable and related to several customizations. 

Magento has developed a Magento Data Migration Tool to assist you with transferring your data. It will help you recognize the differences in the database structure between Magento 1 and Magento 2 databases. Most of these differences are declared in map files. The Data Migration Tool uses map files to transform data into the Magento 2 store. When differences are not declared in map files, then the Data Migration Tool displays an error message and stops running.

While running, if some Magento 1 entities do not exist in Magento 2 database, the following error Source documents are not mapped in Magento 2 Migration might occur: 

Source documents/fields not mapped

1, Source documents are not mapped:  EXTENSION_TABLE 

For example, Source documents are not mapped: sales_order_address_id

2, Source fields are not mapped. Document: EXTENSION_TABLE. Fields: EXTENSION_FIELD

For example, Source fields are not mapped

Document: sales_flat_quote_item. Fields: orderspro_is_temporary?

Explanation:

In rare cases, the message might mention Destination documents or Destination fields instead of source ones.

This error occurs when the Data Migration Tool runs internal tests to verify consistencies between Magento 1 (source) & Magento 2 databases (destination). When you get this error, it simply complaints that some of Magento 1 tables don’t be mapped consistently in Magento 2 database. If you don’t need that unmapped data, then the solution is to ignore the data in the  map.xml (or  map.xml.dist ).

In order to ignore the database entities, you would just have to add the following code snippet into the source <document_rules> tag in the map.xml file:

For the following error:

Source fields are not mapped. Document: EXTENSION_TABLE

Fields: EXTENSION_FIELD

For example: Source fields are not mapped

Document: sales_flat_quote_item. Fields: orderspro_is_temporary?

You just need to add the following code inside the source’s <field_rules> tag in the map.xml file:

Also, the other solutions you can consider to solve these errors include:

  • Install the corresponding Magento 2 extensions. If the incompatible data comes from an extension that adds its 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.
  • Use the -a argument when running the tool to address errors and prevent migration from stopping.

We did it for our data migration project! Have you done? In case you come across some issues over the process, check out this official document from Magento to find out the solution. Hopefully, this post helps you save some of your time (and money).

Your Magento website needs a powerful Magento ERP for stock control.

DON'T MISS THE CHANCE!

magento erp

Magento 2 data migration document has ambiguous configuration - How to solve it
How to fix 500 internal server error in Magento 2?

Leave a Reply

Your email address will not be published. Required fields are marked *