layout | group | subgroup | title | menu_title | menu_node | menu_order | github_link | redirect_from |
---|---|---|---|---|---|---|---|---|
default |
migration |
A_Overview |
Best practices |
Best practices |
1 |
migration/migration-overview-practices.md |
/guides/v1.0/migration/migration-overview-practices.html |
- Migrate data from a replicated Magento 1 database instance
- Remove outdated and redundant data from your Magento 1 database (for example, you could remove logs, order quotes, recently viewed or compared products, visitors, event-specific categories, promotional rules, and so on)
- To avoid any unexpected issues or conflicts please follow steps described in General Rules for Successful Migration
- To boost performance you can set
<direct_document_copy>1</direct_document_copy>
option in yourconfig.xml
. In this case, Magento 1 and Magento 2 databases should be located in one MySQL instance, and the database account must access each database
We tested migration on the following system:
- Environment: Virtual Box VM, CentOS 6, 2.5Gb RAM, CPU 1 core 2.6GHz
- Database had 177k products, 355k orders, 214k customers
- Settings migration time: ~10 mins
- Data migration time: ~9 hrs (all data except URL Rewrites, ~85% of total data)
- Site downtime estimate: A few minutes to reindex and change DNS settings. Additional time required to “warm up” the page cache