Magento – Migration from magento 1.9.2 to magento 2.3

For Data migration from Magento 1 to Magento 2.

Your first step is Setting migrate,

command is:

php bin/magento migrate:settings /var/www/html/{{magento2}}/vendor/magento/data-migration-tool/etc/ce-to-ce/{{magento1 version}}/config.xml

All System -> Configuration settings are migrated in setting migrate. After completion of setting migrate, You need to check in Magento 2 Stores -> Configuration setting.

In migrate setting, From your database table, core_config_data have affected.

All Magento 1 settings are migrated to magento 2.

Thanks.

All these table names and fields which are not "standard" need to be either ignored or mapped in your version of the map.xml.dist configuration files.

The first error line Source documents are not mapped: is about tables which exist in your m1 but m2 knows nothing about, created by extensions.

The next set [ERROR]: Source fields are not mapped. Document: sales_flat_creditmemo (etc) are about attributes (fields) which were created in sales_flat_creditmemo, sales_flat_invoice etc. by extensions, which again m2 knows nothing about.

It's a very long list (and it's only the first, linked to orders, there will be more, regarding customers, products etc.) so you might want to think whether you are using all of these extensions and whether you need it all migrated. The more you can ignore the better for you.

Things that you are not yet ready to migrate (eg:module not existing yet), or will not migrate go in '' tags

<document_rules>
    <ignore>
        <document>easybanner_*</document>
    </ignore>
</document_rules>

<field_rules>
    <ignore>
        <field>sales_flat_order_item.xero_rate</field>
    </ignore>
</field_rules>

Things that will migrate also need to be defined in the xml files too, with transformations if needed. Of course for tables and fields linked to an extension, you need to know if the extension has made it to m2 and if it has changed.

This is going to take you a while and trial and error! I suggest you start by ignoring everything then slowly "move" the things you need to migrate

For things like navigation, banners etc. you might decide to just "rebuild" on m2 rather than fight to migrate.

Ready? It all happens in map.xml.dist (applies across the board) and the more "specialised" map-eav.xml map-customer.xml etc. Each has a document_rules and a field_rules section, and yes, every single one of the names in these long error lists will need to be in there either defined or ignored.

<document_rules>
    <ignore>
        <document>easybanner_*</document>
    </ignore>
</document_rules>

<field_rules>
    <ignore>
        <field>sales_flat_order_item.xero_rate</field>
    </ignore>
</field_rules>