Contact Information

Phone: 1.844.752.7737 (Toll Free)

Ontario Office Address (Headquarters)
74 Fraser Avenue, Suite 200
Toronto, Ontario, M6K 3E1

Austin Office Address
98 San Jacinto Boulevard, 4th floor
Austin, TX 78701


Contact Info
New York +(123) 456 -7890 184 Main Street Victoria 8007
Folow us on social

Magento 1 End of Life: What You Need to Know

If you don’t know now Magento 1 (M1), has come to an end as of June 2020. Magento 1.x will still be accessible and functioning by merchants and developers alike, will no longer receive official support from either Magento or Adobe. 

This change will affect a number of merchants across the Magento ecosystem. What this means is that merchants will now be forced to replatform to either Magento 2 (M2) or an alternate eCommerce CMS. 

This article will explore what Magento 1’s end of life really means for merchants, how Jasper can help with that transition, and how it will affect them in terms of:

  • Design
  • Extensions
  • Security
  • Hosting
  • Cost

Blog Article Contents

The Real Magento 1 End of Life Date

What other Dates Do You Need to Pay Attention to?

The M1 EoL Rumours

What Does This Mean for Your Magento 1 Store?

What Now? How can Jasper help?

The Real Magento End of life Date

The official Magento 1 end of life date is June 2020. 

As of June 2019, there are over 240,000 live Magento sites. Of those, more than 189,000 are still running on M1. We expect to see that number decrease in the coming months as merchants make the move to either M2 or other eCommerce CMS.

What other dates do you need to pay attention to?

Magento’s End of Life (EoL) date isn’t the only time frame you should be paying attention to. On December 31st, 2018, PHP 5.6 was deprecated.

PHP is the server-side scripting language that the Magento platform is written in. Since M1 previously only supported up to PHP 5.6, this would have meant a huge hit to the Magento community.

However, because M1 would be deprecated after the 5.6 EoL, Magento released a patch in September 2018 that enabled M1 sites to support up to PHP 7.2. 7.2 will go EoL in November 2020, providing an additional two years of security support compared to 5.6.

November 2020 will also see the deprecation of CentOS 6.x. Many M1 sites use this as the linux component of their LAMP stack. Its deprecation will signal a further lack of industry-wide support for the M1 platform.  

The M1 EoL Rumours

Speculation regarding the M1 end of life began in April 2017, when a presentation during Meet Magento Prague featured the line “Magento 1 End of Life: 17 November 2018”.

Immediately, articles and images began to appear, with influencers citing that the M1 EoL was sooner that many merchants hoped.

Of course, this information wasn’t correct. It was based on Magento executives previously speculating that Magento 1 would reach End of Life three years after Magento 2 was released. Magento 2 was released November 17, 2015, so it made sense that M1 would be deprecated in late 2018.

Since then, Magento has confirmed that the official end of life date is June 2020.

What does this mean for your Magento 1 store?


Whether you’re moving from M1 to M2, or to another application, you are going to have to go through (at least a partial) site redesign. Depending on how complicated your M1 site is, this can be a lengthy and expensive process.

Before launching into any redesign, it’s important to map out a plan for making your move. Detailed audits are important to ensure that you are able to maintain the same functionality and user experience. There are multiple audit checklists available to merchants and we will soon be releasing our own.


During your M1 audit, it’s important to look at the extensions and integrations you are running with your M1 store.

While extensions originally designed for M1 are not directly compatible with M2, more than 80% of the most popular M1 extensions have received updates, making them compatible. This will save many stores a lot of time and effort when re-platforming.

If moving to an alternate CMS, it’s going to be important to find plugins, extensions, or integrations that can replace existing functionality. In most cases, this will mean using a dev site for testing until you find the right solutions.

Often, the auditing process will reveal a number of extensions and integrations that are redundant. As a result, it’s important to review the value your extensions provide and ask whether you should continue to move forward with them.


In terms of security, the future of M1 is uncertain. It’s important to ensure that your site, its extensions, and its integrations will continue to receive updates. This will help patch security issues and stop you from falling foul of compliance regulations.

While members of the Magento community have said they will continue to support M1 after its official EoL, only time will tell for how long and how far this commitment will extend. As a result, many merchants are already making the move to alternatives.


Not much will change with your hosting post M1. However, since many merchants will be replatforming, they will likely need to request a change in how their hosting environment is optimized.

Due to the complex nature of Magento, hosting environments are often fine-tuned in terms of PHP, cache, and more. Making the move to an alternate will mean making changes to how those optimizations are done. This will be managed by your hosting provider.

Replatforming from M1 is also a good chance to upgrade your hosting infrastructure. Newer products such as BigCommerce offer more in terms of scalability, performance, and security. Moreover, with a higher capacity than classic solutions, you may also save some money. By bundling this with Jasper you can also get even more benefits with Jasper’s built-in M1 transition tool. 


The majority of costs associated with replatforming will come from auditing your existing M1 site and then developing your site for its new platform.

In addition to running a site-wide audit for extensions and integrations, a site redesign will likely be needed. The costs associated with this will vary depending on what application you replatform to and the extent of work required.

If you want to avoid the costs associated with M2 development, WooCommerce and BigCommerce are good alternatives. Due to running on WordPress, both have a large and relatively inexpensive developer communities.

What now? How can Jasper help?

With Jasper’s built-in transition tool, the process of migrating from M1 has never been so easy. This simplifies pulling your complete store data from your current Magento 1 environment.

  • Following which Jasper reviews and organizes the product data.
  • Finally, Jasper PIM pushes the product information to your new store.