PayPal and Visa recommend migrating to M2. Why should you do this and how to migrate safely?
Published: 2020-06-01 09:53:13

Magneto 1 End of Life is set for June 30, 2020: stores on M1 will still work, but Adobe won’t support them and won’t release any updates.
 
PayPal and Visa made press releases about this. They recommend migrating to M2.

What’s the deal?
From June 30 stores on M1 will not comply with the PCI. This is an agreement that defines what payment processors must do to accept payments safely. Drawing up the agreement with their payment processors, stores promised to comply with PCI requirements.
PCI DSS Requirements 6.1 and 6.2 state that companies must “develop and maintain secure systems and applications by installing vendor-supplied security patches”. Adobe will no longer release such patches for M1.
What are the risks?

As the security holes will not be patched anymore, hackers can steal vulnerable data. Stores will have to pay fines, conduct a complete audit of the situation, and pay for PCI forensic investigation.
Stores will have to pay a monthly fee if payment processors find out that they use unsupported software. They will have to convince payment processors that they support the store software and don’t pose a threat to vulnerable data.

To avoid the risks, PayPal and Visa recommend migrating to M2.
We offer a safe migration service
If you decide to migrate, take a look at our M1 to M2 migration service. Migration is a complicated process as M2 has a different data structure and a different set of default features.
We know the differences between M1 and M2 and migrate stores correctly. The process takes 3 steps.

We’ll transfer regular data
Regular data is all the information about customers and products: customers and products themselves, orders, invoices, categories, and attributes.

Difficulties. The data can be transferred with errors if you’ve changed the data structure, added new types of data, or used extensions that affected data. Parts of data can be corrupted, users and their orders will be mixed up. It’s easy to miss such errors, but they will affect the store in the future.

How we solve them. Our developers see whether there’ve been changes to the data and understand where the errors might be. After the migration, we will manually check that the data is transferred correctly and set it up the same way as at your M1 store.
We’ll transfer extensions and their data
You’ll need to transfer the extensions you use and the data they store. For example, you use our Reward Points extension. It charges store credits for purchases and stores information about the amounts of store credits.
Difficulties. You will need to find the equivalent extensions for M2 and thoroughly compare their functionalities. For some extensions there will be no equivalents, for some the functionalities will differ.
If the equivalent extensions don’t have the “export/import” function (you export data from the M1 mod and import it to the M2 mod), you will need to transfer the data manually. It will take lots of time and there is a risk of making mistakes.
How we solve them. First, we’ll help you find the equivalent extensions for M2 so that all the necessary functions remain. We will install the mods on your website and check if everything works properly.
Then we will create a custom script for your website. It will transfer the data automatically. After the script has worked out, we’ll review the result manually. This way we guarantee we will transfer data in full and correctly.

See our Partners page for a list of system integrators and e-commerce solution provider

If you are interested in our <a href="https://www.axtongroup.com/services/magento-2-0-development/">magneto migration service </a> just reply to this email or drop me a line at
info@axtongroup.com or Contact +1 610 209 3937
Website:<a href="https://www.axtongroup.com">https://www.axtongroup.com</a>