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

Commit e2ad765

Browse files
committed
Removed forced numbering class
1 parent 4d7c7b6 commit e2ad765

File tree

1 file changed

+0
-6
lines changed

1 file changed

+0
-6
lines changed

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

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -57,22 +57,16 @@ In such migration testing, follow these steps:
5757

5858
For example: the `enterprise_salesarchive_archive_orders` cron job moves old orders to archive. Running this job during migration is safe because the Delta mode takes the job into account and thus properly processes the archived orders.
5959

60-
{:start="4"}
61-
6260
1. Use the Data Migration Tool to migrate settings and websites.
6361

6462
1. Copy your Magento 1.x media files to Magento 2.x.
6563

6664
You must copy these files manually from the `magento1-root/media` directory to `magento2-root/pub/media`.
6765

68-
{:start="6"}
69-
7066
1. Use the Data Migration Tool to bulk copy your data from Magento 1 database to Magento 2 database.
7167

7268
If some of your extensions have data you want to migrate, you might need to install these extensions adapted for Magento 2. In case the extensions have a different structure in Magento 2 database, use the mapping files provided with the Data Migration Tool.
7369

74-
{:start="7"}
75-
7670
1. Reindex all Magento 2.x indexers. For details, see the [Configuration guide].
7771

7872
## Step 5: Make changes to the migrated data (if needed)

0 commit comments

Comments
 (0)