Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.

Commit 0de6794

Browse files
authored
Merge pull request #5132 from atwixfirster/migration-tool-updates1
magento/devdocs#: Data Migration Tool. Updates Content.
2 parents 9d653b6 + 2342063 commit 0de6794

File tree

2 files changed

+34
-45
lines changed

2 files changed

+34
-45
lines changed

guides/v2.2/migration/migration-migrate-data.md

Lines changed: 17 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,9 @@ See the [First steps]({{ page.baseurl }}/migration/migration-migrate.html#migrat
1919

2020
To start migrating data, run:
2121

22-
bin/magento migrate:data [-r|--reset] [-a|--auto] {<path to config.xml>}
22+
```bash
23+
bin/magento migrate:data [-r|--reset] [-a|--auto] {<path to config.xml>}
24+
```
2325

2426
where:
2527

@@ -35,49 +37,23 @@ To force the Data Migration Tool to run from the beginning, use the `--reset` ar
3537

3638
## Possible consistency errors {#migrate-command-data}
3739

38-
While running, the Data Migration Tool may report inconsistencies between Magento 1 and Magento 2 databases, and display messages like this:
39-
40-
```xml
41-
Source documents are not mapped: <EXTENSION_TABLE>
42-
```
40+
While running, the Data Migration Tool may report inconsistencies between Magento 1 and Magento 2 databases, and display messages like the following:
41+
42+
- `Source documents are missing: <EXTENSION_TABLE_1>,<EXTENSION_TABLE_2>,...<EXTENSION_TABLE_N>`
43+
- `Destination documents are missing: <EXTENSION_TABLE_1>,<EXTENSION_TABLE_2>,...<EXTENSION_TABLE_N>`
44+
- `Source documents are not mapped: <EXTENSION_TABLE_1>,<EXTENSION_TABLE_2>,...<EXTENSION_TABLE_N>`
45+
- `Destination documents are not mapped: <EXTENSION_TABLE_1>,<EXTENSION_TABLE_2>,...<EXTENSION_TABLE_N>`
46+
- `Source fields are missing. Document: <EXTENSION_TABLE>. Fields: <FIELD_1>,<FIELD_2>...<FIELD_N>`
47+
- `Destination fields are missing. Document: <EXTENSION_TABLE>. Fields: <FIELD_1>,<FIELD_2>...<FIELD_N>`
48+
- `Source fields are not mapped. Document: <EXTENSION_TABLE>. Fields: <FIELD_1>,<FIELD_2>...<FIELD_N>`
49+
- `Destination fields are not mapped. Document: <EXTENSION_TABLE>. Fields: <FIELD_1>,<FIELD_2>...<FIELD_N>`
50+
- `Mismatch of data types. Source document: <EXTENSION_TABLE>. Fields: <FIELD_1>,<FIELD_2>...<FIELD_N>`
51+
- `Mismatch of data types. Destination document: <EXTENSION_TABLE>. Fields: <FIELD_1>,<FIELD_2>...<FIELD_N>`
52+
- `Incompatibility in data. Source document: <EXTENSION_TABLE>. Field: <FIELD>. Error: <ERROR_MESSAGE>`
53+
- `Incompatibility in data. Destination document: <EXTENSION_TABLE>. Field: <FIELD>. Error: <ERROR_MESSAGE>`
4354

4455
See the [Troubleshooting]({{ page.baseurl }}/migration/migration-troubleshooting.html) section of this guide for more information and recommendations.
4556

46-
<!--
47-
48-
When you migrate data, the Data Migration Tool verifies that tables and fields are consistent between Magento 1 and Magento 2. If they are inconsistent, you will see an error message that lists the problematic tables and fields, for example:
49-
50-
Source fields are not mapped. Document: <document_name>. Fields: <field_name>
51-
52-
**Possible reason for error:** some database entities belong to Magento 1 extensions that do not exist in the Magento 2 database.
53-
54-
Below are the possible ways to handle these errors.
55-
56-
### Fix errors: Install corresponding Magento 2 extensions
57-
58-
Visit [Magento Marketplace](https://marketplace.magento.com/){:target:"_blank"} to find the latest [extension](https://glossary.magento.com/extension) versions or contact your extension provider.
59-
60-
### Fix errors: Ignore entities
61-
62-
You may tell the Data Migration Tool to ignore the problematic entities.
63-
64-
To do that, add the `<ignore>` tag to an entity in the `map.xml` file, like this:
65-
66-
```xml
67-
<ignore>
68-
<field>sales_order_address_id</field>
69-
</ignore>
70-
```
71-
72-
{: .bs-callout .bs-callout-warning }
73-
Before ignoring entities, make sure you don't need the affected data in your Magento 2 store.
74-
75-
### Verify fixes
76-
77-
To know if the issues have been resolved successfully, run the Data Migration Tool again.
78-
79-
-->
80-
8157
## Next migration step
8258

8359
[Migrate changes]({{ page.baseurl }}/migration/migration-migrate-delta.html)

guides/v2.2/migration/migration-troubleshooting.md

Lines changed: 17 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -38,9 +38,22 @@ This message appears because the Data Migration Tool runs internal tests to veri
3838
To ignore database entities, add the `<ignore>` tag to an entity in the `map.xml` file, like this:
3939

4040
```xml
41-
<ignore>
42-
<field>sales_order_address_id</field>
43-
</ignore>
41+
...
42+
<source>
43+
<document_rules>
44+
...
45+
<!-- Ignore `sales_flat_invoice_grid` table -->
46+
<ignore>
47+
<document>sales_flat_invoice_grid</document>
48+
</ignore>
49+
<!-- Ignore `address_id` field of `sales_flat_order_address` table -->
50+
<ignore>
51+
<field>sales_flat_order_address.address_id</field>
52+
</ignore>
53+
...
54+
</document_rules>
55+
</source>
56+
...
4457
```
4558

4659
{: .bs-callout .bs-callout-warning }
@@ -108,7 +121,7 @@ This configuration adds a hash-string to the conflicting records of [URL](https:
108121
### Mismatch of entities
109122

110123
```xml
111-
Mismatch of entities in the document: <DOCUMENT>
124+
Mismatch of entities in the document: <DOCUMENT> Source: <COUNT_ITEMS_IN_SOURCE_TABLE> Destination: <COUNT_ITEMS_IN_DESTINATION_TABLE>
112125
```
113126

114127
#### Explanation

0 commit comments

Comments
 (0)