The world and technologies do not stand still so, after lasting and successful Magento 1 epoch, it is the time for Magento 2. As you may know, the second version was unripe in the beginning so we from our professional point of view could not recommend migrating to it. However, versions 2.2 and 2.3 appear to be pretty much ready for production stores.
Even though Magento 1 and Magento 2 look alike at a first glance, they are completely different. In the terms of a standard migration, this results in the inability to migrate design themes, 3rd-party module's functionality, custom products, modifications, etc. You'd have to almost dump everything in your M1 store and begin from a clean slate with your basic Magento 2 instance that can only include some old data:
- Stores and their settings
- Products and attributes
- All orders
- All customers
- CMS pages and blocks
In other words, the default migration procedure can only transfer standard DB data. The next step involves installation of 3rd-party modules and custom development when needed.
I) System requirements check and installation of a clean Magento 2
We strongly recommend our customers to set up their new M2 server according to Magento 2 technology stack requirements since the environment used for Magento 1 is not compatible. In rare cases, we can resolve the main cause for such incompatibility, which is PHP7, by adapting Magento 1 to work with the newer PHP version. However, such work would entail additional preparation services, which you can request by contacting us.
II) Data migration from Magento 1 to Magento 2
Specifics: Magento 2 installation must be clean and not configured or tested in any way; from Magento 1, our part needs its DB and the 'media' folder with enclosed contents.
III) Migrated Magento 2 check
We check all pages types by opening them, resolve all sorts of problems like unexpected bugs, system fatal errors, log errors, conduct a SEO-check and fix of URLs with the help of URL Optimization after Migration. This is followed by a full backup of the migrated Magento.
IV) (Optional) M2 extension installation and/or custom development
Magento default functionality doesn't always suit your business. Fortunately, our experienced developers are able to carry out any kind of work to expand capabilities of your Magento in the terms of paid custom development services.
V) Incremental migration (delta) and going to live
III and IV migration steps usually take a certain amount of time while the production M1 web-shop lives its own life collecting new orders and customers. Syncing these changes is possible during this step. However, there are few restrictions for a delta migration procedure:
- New products from M1 can't be transferred, only changes in existing products
- New attributes from M1 can't be transferred
- New test orders in M2 must not be created
- New test customer accounts in M2 must not be created
For thorough tests, we urge our clients to create a copy of the migrated Magento 2 instance to avoid situations when a restoration from the step-III backup is inevitable.
After final tests and approval of the date to make the M2 website live, the procedure is as follows:
1. Enable maintenance mode for Magento 1
2. Conduct delta migration to sync changes like orders and customers
3. Working capacity check of the Magento 2
4. DNS change to point the production domain to a new location
The latter might take up to 60 minutes based on the DB size.