Every day you see thousands of irresistible reasons why you should upgrade Magento 1 to Magento 2.

Plus, you might have received an alarming email saying that Magento 1 shops will no longer be PCI compliant after June 2020:

PCI DSS Requirements 6.1 and 6.2 address the need to keep systems up to date with vendor-supplied security patches to protect systems from known vulnerabilities.

PCI DSS 2.3.1, Requirements 6.1, 6.2

Prior to that, store owners focused on bailing out their shops from the tough times but this news from Visa and PayPal simply added fuel to the fire.

The Magento community is excited about the future of their online stores, will they still be able to accept payments? What should they do now? Mage One wrote an open letter to PayPal and Visa about the M1EOL (they haven’t received a reply yet):

So, what do you do with this now?

Have no time to read on? Subscribe to a free consultation on Magento migration and PCI compliance with our expert.

M1EOL: PCI Compliance can’t be ignored

Definitely, you can’t ignore this Visa and PayPal update on M1EOL, as drawing up the agreement with your payment processor, you promised to comply with PCI requirements. Ignoring them you jeopardize the work of your business.

What can you come through if ignoring?

worst-case scenario

Say, hackers found a breach at your store and your customers’ credit cards were compromised. This breach can cost your retail store because in this case, you will be obliged to
(a) hire a Qualified Security Assessor who will conduct a complete audit of this situation, which is very expensive,
(b) you’ll probably pay fines for the stolen credit cards data and
(c) pay for PCI forensic investigation, in case it’s required.
It can cost you everything. But it’s the worst-case and unlikely scenario.

high scenario

Payment processors run regular scans to detect stores that don’t meet their demands including outdated software. Thus, you’ll have to pay a monthly fee after your unsupported software is found or/and submit all the necessary documentation for convincing them that you still support your store software and don’t pose a threat to vulnerable data. It’s a very drawn-out and expensive procedure as well, though it isn’t so bad as the previous.

Okay, but PCI compliance is not the only problem.

You’ll hardly manage to keep your M1 store running not to mention its development. Besides the risk of being hacked, you’ll have difficulties with hostings, vendors, and companies of other 3rd-party products you now use. Far not all hostings will provide each shop with its isolated node to keep others safe from you. Far not all vendors will provide patches for their Magento 1 extensions.

However, there’s no reason to panic.

M1EOL will never be the matter of a single day.

Well-known hostings like Hypernode, vendors like Amasty and companies like Mage One, dedicated to the support of Magento 1 users providing them with necessary security patches, will help you get through.

We’ll continue supporting our Magento 1 customers. The detailed plan of services is now being approved and will soon be provided to you.

 

M1EOL: more reasons to upgrade to Magento 2

  1. M2 has upgraded the minimum versions of technology stack;
  2. M1 technology stack won’t support the latest versions of those technologies. Ignoring this, you risk to stay in the back of business racing;
  3. M2 goes with built-in FPC (full-page cache), you won’t have to install an extension. Your home, product, category pages will load in less than 0,75 seconds, which is twice faster than without the FPC;
  4. On the whole, M2 is claimed by the developers to be 20% faster than M1;
  5. In M2, you can do DB sharing and keep product info on a different server for faster browsing for the info on the users’ side;
  6. The same refers to the checkout, you can also keep the related data on a different server, making the checkout go smoother;
  7. Moreover, M2 has 2 checkout steps + Instant Purchase for repeating purchases where M1 has 6;
  8. In M1, to build a page, you need to load multiple JS. In M2, they switched from prototype JS to JQuery and Require JS, which reduces a page loading time;
  9. M2 removed bad code from the base;
  10. M1 code won’t be supported making it easy picking for hackers;
  11. M2 uses Composer to manage modules installation;
  12. Plus, M2 has released APIs that serve as an interface for modules, which solved problems with 3rd-party extensions incompatibility and other supporting issues;
  13. In M2, they’ve simplified the update to the latest versions and installation of security patches;
  14. After Magento 1.9 end of life, they won’t release security patches. This means you’ll compromise your business and clients’ vulnerable data;
  15. Magento 2.3 supports PWA Studio, and you can provide even better mobile experience to users;
  16. M2 has been written with automated test strategies in mind. Now your developers can test any customization on affecting the core functionality using test cases in MTF;
  17. M2 has a more native interface that was specially designed for non-technical users.

 

Where to start with Magento 1 migration?

Plan Magento 1 to Magento 2 migration

In brief: We advise you to divide the preparatory work into 3 bigger blocks:

  1. themes;
  2. extensions;
  3. customizations.

Align your work with the functions you need to replicate in Magento 2, eliminating the superfluous.

→ See no-risk migration plan or download it in PDF

Choose Magento 2 Open Source | Commerce | Commerce Cloud

In brief: The sure way is to identify your requirements and relate them to Open Source, Commerce, Commerce Cloud options. We recommend Magento 2 Open Source to developing businesses, startups, and small stores. Magento 2 Commerce and Commerce Cloud suit B2B enterprises and stores with high customer traffic, large product catalogs, wide global presence, or high business complexity.

→ See the comparison of Magento 2 Open Source vs. Commerce vs. Commerce Cloud or download it in PDF

Use Magento 1 migration service

In brief: You can take this migration test or use your good judgment, however, what we know from our own experience is that the process requires at least 3 months and a team of Magento experts.

The timeline for a migration can vary based on your eCommerce site, but a safe bet is to allow a minimum of 3 months.

How does our migration service work?

  1. Go see a list of works we can help you with;
  2. Shape your expectations;
  3. Fill in your contact data;
  4. And our specialist will get in touch with you within 24 hours.

We’re not going to scare you saying there’s no way out except migrating to Magento 2.

Having worked with Magento 1 and seen all the drawbacks, many retailers choose to switch to Shopify, WooCommerce, and other e-commerce platforms.

For what it’s worth, we are always open to help you.

Just drop a line about your current problem to this form and our specialist will contact you within 24 working hours to help with it.