cancel
Showing results for 
Search instead for 
Did you mean: 

Migration from 1.9.3.1 to 2.3.2 Error: Record structure does not contain field path

Highlighted

Migration from 1.9.3.1 to 2.3.2 Error: Record structure does not contain field path

I am running a migration from 1.9.3.1 to 2.3.2. I copied the database from my Magento 1.9 store to a new database on the same server my Magento 2 install is on. I created a new empty database and configured the data migration tool.

 

<database host="localhost" name="magento1" user="*****" password="*****" />
    </source>
    <destination>
        <database host="localhost" name="magento2" user="*****" password="*****" />
    </destination>

 

 

I haven't changed anything in config.xml other than the crypt key.

 

I have had a few different error messages come up while trying to run:

 

# bin/magento migrate:settings -a -r public_html/magento2/vendor/magento/data-migration-tool/etc/opensource-to-opensource/1.9.3.1/config.xml

 

I have made it past a few different errors getting the data migration tool configured correctly with my databases and now it starts fine.

 

Now it throws up this error:

[2019-08-07 17:46:08][INFO][mode: settings][stage: integrity check][step: Settings Step]: started
100% [============================] Remaining Time: < 1 sec
[2019-08-07 17:46:08][INFO][mode: settings][stage: integrity check][step: Stores Step]: started
100% [============================] Remaining Time: < 1 sec
[2019-08-07 17:46:08][WARNING]: Source documents are not mapped: core_store,core_store_group,core_website                                   
[2019-08-07 17:46:08][WARNING]: Destination documents are not mapped: store,store_group,store_website                                       
[2019-08-07 17:46:08][INFO][mode: settings][stage: data migration][step: Settings Step]: started
0% [>---------------------------] Remaining Time: < 1 sec
[2019-08-07 17:46:08][ERROR]: Record structure does not contain field path                                                                  
In Settings.php line 101:
                         
  Data Migration failed  
                         

migrate:settings [-r|--reset] [-a|--auto] [--] <config>

I'm not sure what is going wrong. Any help would be much appreciated!

11 REPLIES 11
Highlighted

Re: Migration from 1.9.3.1 to 2.3.2 Error: Record structure does not contain field path

Hi @hayden_holbrook,

 

Is you bin/magento global?

From where are you running bin/magento since public_html/magento2/vendor/magento/data-migration-tool/etc/opensource-to-opensource/1.9.3.1/config.xml?

 

Shouldn't be?

 

bin/magento migrate:settings -a -r vendor/magento/data-migration-tool/etc/opensource-to-opensource/1.9.3.1/config.xml

Highlighted

Re: Migration from 1.9.3.1 to 2.3.2 Error: Record structure does not contain field path

Damian,

 

I a running it from there since I have another store farther up in the file structure. Is that causing the problem?

 

Hayden

Highlighted

Re: Migration from 1.9.3.1 to 2.3.2 Error: Record structure does not contain field path

I tried running it with the shortened file path and got the same error.

Highlighted

Re: Migration from 1.9.3.1 to 2.3.2 Error: Record structure does not contain field path

Hi @hayden_holbrook,

 

Is it possible to share the XML (change the passwords and username at least) to see if evertyhing is ok?

Highlighted

Re: Migration from 1.9.3.1 to 2.3.2 Error: Record structure does not contain field path

<?xml version="1.0" encoding="UTF-8"?>
<!--
/**
 * Copyright © Magento, Inc. All rights reserved.
 * See COPYING.txt for license details.
 */
-->
<config xmlns:xs="http://www.w3.org/2001/XMLSchema-instance" xs:noNamespaceSchemaLocation="../../config.xsd">
    <steps mode="settings">
        <step title="Settings Step">
            <integrity>Migration\Step\Settings\Integrity</integrity>
            <data>Migration\Step\Settings\Data</data>
        </step>
        <step title="Stores Step">
            <integrity>Migration\Step\Stores\Integrity</integrity>
            <data>Migration\Step\Stores\Data</data>
            <volume>Migration\Step\Stores\Volume</volume>
        </step>
    </steps>
    <steps mode="data">
        <step title="Data Integrity Step">
            <integrity>Migration\Step\DataIntegrity\Integrity</integrity>
        </step>
        <step title="EAV Step">
            <integrity>Migration\Step\Eav\Integrity</integrity>
            <data>Migration\Step\Eav\Data</data>
            <volume>Migration\Step\Eav\Volume</volume>
        </step>
        <step title="Customer Attributes Step">
            <integrity>Migration\Step\Customer\Integrity</integrity>
            <data>Migration\Step\Customer\Data</data>
            <volume>Migration\Step\Customer\Volume</volume>
        </step>
        <step title="Map Step">
            <integrity>Migration\Step\Map\Integrity</integrity>
            <data>Migration\Step\Map\Data</data>
            <volume>Migration\Step\Map\Volume</volume>
        </step>
        <step title="Url Rewrite Step">
            <integrity>Migration\Step\UrlRewrite\Version191to2000</integrity>
            <data>Migration\Step\UrlRewrite\Version191to2000</data>
            <volume>Migration\Step\UrlRewrite\Version191to2000</volume>
        </step>
        <step title="Log Step">
            <integrity>Migration\Step\Log\Integrity</integrity>
            <data>Migration\Step\Log\Data</data>
            <volume>Migration\Step\Log\Volume</volume>
        </step>
        <step title="Ratings Step">
            <integrity>Migration\Step\Ratings\Integrity</integrity>
            <data>Migration\Step\Ratings\Data</data>
            <volume>Migration\Step\Ratings\Volume</volume>
        </step>
        <step title="ConfigurablePrices step">
            <integrity>Migration\Step\ConfigurablePrices\Integrity</integrity>
            <data>Migration\Step\ConfigurablePrices\Data</data>
            <volume>Migration\Step\ConfigurablePrices\Volume</volume>
        </step>
        <step title="OrderGrids Step">
            <integrity>Migration\Step\OrderGrids\Integrity</integrity>
            <data>Migration\Step\OrderGrids\Data</data>
            <volume>Migration\Step\OrderGrids\Volume</volume>
        </step>
        <step title="Tier Price Step">
            <integrity>Migration\Step\TierPrice\Integrity</integrity>
            <data>Migration\Step\TierPrice\Data</data>
            <volume>Migration\Step\TierPrice\Volume</volume>
        </step>
        <step title="SalesIncrement Step">
            <integrity>Migration\Step\SalesIncrement\Integrity</integrity>
            <data>Migration\Step\SalesIncrement\Data</data>
            <volume>Migration\Step\SalesIncrement\Volume</volume>
        </step>
        <step title="Inventory Step">
            <integrity>Migration\Step\Inventory\Integrity</integrity>
            <data>Migration\Step\Inventory\Data</data>
            <volume>Migration\Step\Inventory\Volume</volume>
        </step>
        <step title="PostProcessing Step">
            <data>Migration\Step\PostProcessing\Data</data>
        </step>
    </steps>
    <steps mode="delta">
        <step title="Customer Attributes Step">
            <delta>Migration\Step\Customer\Delta</delta>
            <volume>Migration\Step\Customer\Volume</volume>
        </step>
        <step title="Map Step">
            <delta>Migration\Step\Map\Delta</delta>
            <volume>Migration\Step\Map\Volume</volume>
        </step>
        <step title="Log Step">
            <delta>Migration\Step\Log\Delta</delta>
            <volume>Migration\Step\Log\Volume</volume>
        </step>
        <step title="OrderGrids Step">
            <delta>Migration\Step\OrderGrids\Delta</delta>
            <volume>Migration\Step\OrderGrids\Volume</volume>
        </step>
        <step title="SalesIncrement Step">
            <delta>Migration\Step\SalesIncrement\Delta</delta>
            <volume>Migration\Step\SalesIncrement\Volume</volume>
        </step>
        <step title="Inventory Step">
            <delta>Migration\Step\Inventory\Delta</delta>
            <volume>Migration\Step\Inventory\Volume</volume>
        </step>
    </steps>
    <source>
        <database host="localhost" name="magento1" user="*****" password="*****" />
    </source>
    <destination>
        <database host="localhost" name="magento2" user="*****" password="*****" />
    </destination>
    <options>
        <map_file>etc/opensource-to-opensource/1.9.3.1/map.xml.dist</map_file>
        <eav_map_file>etc/opensource-to-opensource/map-eav.xml.dist</eav_map_file>
        <eav_document_groups_file>etc/opensource-to-opensource/eav-document-groups.xml.dist</eav_document_groups_file>
        <eav_attribute_groups_file>etc/opensource-to-opensource/eav-attribute-groups.xml.dist</eav_attribute_groups_file>
        <log_map_file>etc/opensource-to-opensource/map-log.xml.dist</log_map_file>
        <log_document_groups_file>etc/opensource-to-opensource/log-document-groups.xml.dist</log_document_groups_file>
        <settings_map_file>etc/opensource-to-opensource/settings.xml.dist</settings_map_file>
        <customer_map_file>etc/opensource-to-opensource/map-customer.xml.dist</customer_map_file>
        <customer_document_groups_file>etc/opensource-to-opensource/customer-document-groups.xml.dist</customer_document_groups_file>
        <customer_attribute_groups_file>etc/opensource-to-opensource/customer-attribute-groups.xml.dist</customer_attribute_groups_file>
        <delta_document_groups_file>etc/opensource-to-opensource/deltalog.xml.dist</delta_document_groups_file>
        <order_grids_document_groups_file>etc/opensource-to-opensource/order-grids-document-groups.xml.dist</order_grids_document_groups_file>
        <map_document_groups>etc/opensource-to-opensource/map-document-groups.xml.dist</map_document_groups>
        <class_map>etc/opensource-to-opensource/class-map.xml.dist</class_map>
        <tier_price_map_file>etc/opensource-to-opensource/1.9.3.1/map-tier-price.xml.dist</tier_price_map_file>
        <stores_map_file>etc/opensource-to-opensource/map-stores.xml.dist</stores_map_file>
        <!--
        In case bulk_size=0 it will be auto-detected for every document.
        -->
        <bulk_size>0</bulk_size>
        <!--
        Set direct_document_copy = 1 for better performance.
        NOTE: 'source' and 'destination' databases MUST be placed on the same MySQL instance
        and 'destination' user MUST be granted with 'SELECT' permissions on 'source' database
         -->
        <direct_document_copy>0</direct_document_copy>
        <source_prefix />
        <dest_prefix></dest_prefix>
        <auto_resolve_urlrewrite_duplicates>0</auto_resolve_urlrewrite_duplicates>
        <log_file>migration.log</log_file>
        <progress_bar_format>%percent%% [%bar%] Remaining Time: %remaining%</progress_bar_format>
        <upgrade_customer_password_hash>1</upgrade_customer_password_hash>
        <edition_migrate>opensource-to-opensource</edition_migrate>
        <edition_number>1.9.3.1</edition_number>
        <init_statements_source>SET NAMES utf8;</init_statements_source>
        <init_statements_destination>SET NAMES utf8;</init_statements_destination>
        <crypt_key>********</crypt_key>
    </options>
</config>
Highlighted

Re: Migration from 1.9.3.1 to 2.3.2 Error: Record structure does not contain field path

Hi @hayden_holbrook,

 

I compared your XML with one of mine (from another version) and the only thing (that shouldn't be a problem, but is different was this line:

 

<dest_prefix></dest_prefix>

Can you try with:

<dest_prefix />

Can you check that?

Highlighted

Re: Migration from 1.9.3.1 to 2.3.2 Error: Record structure does not contain field path

Hi @hayden_holbrook 

 

I have read all the conversation about migration.
How to installed migration tools?. using composer or from Github.

If you have used a manual, you can try from the composer. Also, compare the table from fresh Magento 1.9.x.x which has an integrity issue. It may be the table modify in Magento 1.9.x.x.

 

Thanks,
Siddiqui

 

Highlighted

Re: Migration from 1.9.3.1 to 2.3.2 Error: Record structure does not contain field path

Siddiqui208,

 

I installed via composer.

 

I will try with a fresh 1.9.x.x and see if I can get that to work. Thanks for the suggestion!

 

Hayden

Re: Migration from 1.9.3.1 to 2.3.2 Error: Record structure does not contain field path

Damian,

 

I have tried with that change and I still get the same error. I wish the error message would tell me a bit more about where the problem is occurring.

 

Thanks,

Hayden