Is it true that you are wanting to relocate from Magento 1 to Magento 2?
On the off chance that indeed, at that point you are in good shape.
Assuming No, at that point reconsider it.
The official help for the Magento 1.x forms will stop after 2020.
Here is a fascinating certainty
In excess of 250,00 locales use Magento, yet just 11,000 of them keep running on Magento 2.
In this way, don’t stress. You are not the only one. In this article, I will impart to you some snappy strides through which you can without much of a stretch update Magento 1 to Magento 2 utilizing the information relocation apparatus.
Please also read: magento 2 custom option
Why Migrate From Magento 1 to Magento 2?
The appropriate response is basic. You need to remain refreshed, not obsolete.
Magento has quit presenting any updates in its Magento 1 rendition.
Every one of the progressions done in Magento 1 must be rehashed in Magento 2 form, at whatever point you overhaul.
Magento 2 gives better outcomes, improved site execution, and drive separated omnichannel business experience.
What ought to be remembered before Magento Migration?
Before you overhaul Magento 1 to Magento 2, here are some fundamental viewpoints to consider:
Survey and break down what should be kept or expelled from the new Magento 2 site.
Ensure you have a full reinforcement of your Magento 1 store and the necessary database, documents, and envelopes.
Abstain from utilizing the live store for the movement procedure. Move the information from the cloned database of the Magento 1 store.
Check if your present expansions, custom code, and subjects are good with the Magento 2.
Move Magento 1 to Magento 2 out of 4 Easy Steps
Customizations Migration utilizing Code Migration Tool
Information Migration utilizing Data Migration Tool
Stage 1: Theme Migration
To redesign Magento 1 subject to Magneto 2, you need to check if Magento 1 topic is good with Magento 2 form or not.
On the off chance that Yes, at that point you can introduce a similar topic in Magento 2. This will make the procedure of relocation significantly simpler for you.
Assuming No, at that point you can either make a custom topic in Magento 2 or purchase and introduce a Magento 2 subject from Magento Marketplace.
Stage 2: Extension Migration
Once more, you need to check if Magento 1 augmentations are good with Magento 2 adaptation or not.
On the off chance that indeed, at that point you can coordinate similar augmentations in Magento 2.
Assuming No, at that point you need to include new expansions.
Stage 3: Customization Using Code Migration Tool
Magento 2 customization should be possible utilizing a Code Migration Tool.
It can hugely reduce the work engaged with the code relocation.
In any case, in the wake of running the toolbox, you may need to alter a portion of the produced records physically.
Stage 4: Data Migration Using Data Migration Tool
The last advance is to relocate information from Magento 1 to Magento 2. You can utilize Magento 2 Data Migration Tool for a smooth movement. With the assistance of this device, you can relocate basic information, for example, items, orders, classes, store settings and setups, and so forth to Magento 2.
Here’s a stage savvy manual for information movement:
4.1. Introduce Data Migration Tool through Composer
1. Prior to introducing this instrument, ensure the adaptation of both – Data Migration device and Magento 2 are decisively the equivalent. For instance, in the event that you are utilizing Magento v2.1.1, you should introduce the Data Migration Tool v2.1.1.
Don’t have a clue about your Magento adaptation?
Explore to the root catalog of your Magento 2 by means of SSH terminal and enter this direction:
- php bin/magento –version
2. Since you know the form of your Magento 2 store introduces the Data Migration Tool.
Note: Update the area of the Data Migration Tool bundle in the composer.json document in the Magento 2 root registry. To do this, run this direction:
- composer config repositories.magento composer https://repo.magento.com
- Composer require magento/data-migration-tool:<version>
Here, is your Data Migration Tool adaptation. For instance, for Data Migration device for Magento v2.1.1. You should supplant with 2.1.1
- Composer require magento/data-migration-tool:2.1.1
3. Enter your validation keys
Go to Magento Marketplace > Sign in > Click on My Access Keys
On the off chance that you as of now have keys, the open key is your username and the private key is your secret phrase. Else, you can make another key pair. Snap on “Make a New Access Key Button.”
4.2. Arrange Data Migration Tool
In the wake of finishing the establishment, you will locate the accompanying registries to contain mapping and design records for the Data Migration Tool:
- <Magento 2 root dir>/vendor/magento/data-migration-tool/etc/ce-to-ee
This incorporates design and contents for relocating from Magento 1 Community Edition to Magento 2 Enterprise Edition.
For Magento 1 Enterprise Edition to Magento 2 Enterprise Edition, utilize this direction:
- <Magento 2 root dir>/vendor/magento/data-migration-tool/etc/ee-to-ee
Note: Before relocating any information and settings, make a config.xml record in the pertinent registry.
- <database host=“localhost” name=“Magento1-DB-name” user=“DB-username” password=“DB-password” />
- <database host=“localhost” name=”Magento2-DB-name” user=“DB-username” password=“DB-password” />
- <source> : has Magento 1’s database information
- <destination> : has relevant information of Magento 2
- <crypt_key> : encryption key of Magento 1 which can be found in in <key> tag for <Magento 1 rootdir>/app/etc/local.xml file.
In conclusion, spare config.xml document.
4.3. Relocate Settings
Utilize the Data Migration Tool to relocate settings from Magento 1 to Magento 2.
This incorporates sites, stores, framework designs like expense settings, installment, shipping, and so on.
You ought to move the setting first. To begin with that, explore to your Magento 2 root index by means of SSH terminal and run this order:
- php bin/magento migrate:settings –reset <path to your config.xml>
Where <path to your config.xml> is vendor/Magento/data-migration-tool/etc/ce-to-ee/<Magento 1.x version>/config.xml.
Upon effective relocation, a message will be shown.
Must Read: Magento 1 versus Magento 2: Top 6 Differences You Must Know
4.4. Relocate Data
To relocate items, orders, lists of things to get, clients, classifications, evaluations, and so on pursue this direction:
- php bin/magento migration:data –reset <path to your config.xml>
On the off chance that on the off chance that, there’s a blunder during the movement, allude Magento’s Troubleshooting page.
Wrapping it up..
After the relocation has been done, run a test to guarantee the correct working of Magento 2.
Relocating from Magento 1 to Magento 2 isn’t simple, as it includes a ton of manual errands.
For issue free and safe movement, you can procure specialists to complete your activity.