— Magento (@magento) September 6, 2018
Although the news is extraordinarily simple and obvious, it raises many disputable questions among Magento users.
In this post, we’ll try to cover all the things and risks you care so much about.
And the first question we address is how actually the end of life can affect your business.
- How M1EOL affects my business? Why so early?
- Determine your Magento version and plan migration
- Three Magento Migration blocks
- Major Magento 2 migration risks
How M1EOL affects my business? Why so early?
On September 6, 2018, Magento started slacking the support for Magento 1. This means the number of security patches and fixes is minimum until unraveling completely. Check the proof. If you take no steps further, you compromise vulnerable business data that may include information about your clients as well.
The next question you may ask is why Magento made the announcement about the M1EOL 2 years before the actual date. The answer is simple, the company wants to save their clients leaving more time for migration. How to make this right? Surely, at least you need to inform them in advance.
Moreover, together with Magento, we invite you to consider Magento 2 migration not just a business-saving step but a golden opportunity to innovate your approach to many business things. Who knows, maybe all those features we saw in Magento 2.3 release are what you need.
And this is what we are going to talk about in the next part: Magento 2 migration is a necessary evil or the opportunity. We want to help you determine your Magento version and plan a riskless migration.
Determine your Magento version and plan migration
We, as an active contributor to Magento Community life and development, will go online too on April 9, 2019. So, be proactive – monitor the news on our blog.
As we’ve already said, determining your Magento version is the first step you need. Imagine you’re in June 2020, your Magento 1.9.0 (or other) lacks support, your vulnerable business data went away to wide spaces of the global network, your 3rd-party extensions refuse to work and the sore eventually closes. Is that how you see your business future? I’m sure it’s not.
To reassure you, we’ll spell out a few Magento 2 pros below:
- Highly customizable checkout – one step closer to almost checkout-less process;
- Better search options and simple checkout make the contribution to bringing more mobile traffic, even without a special mobile version of your website;
- Faster catalog and checkout pages loading speed;
- Support for up to 250K orders per hour and up to 2M page views.
BONUS: Data Migration Tool
Okay, what do we do next?
Plan Magento 2 migration carefully to avoid all the known risks.
Three Magento Migration blocks
#1. Your Magento 1 themes
Unfortunately, you can’t migrate your current theme directly to Magento 2. However, you have at least three alternatives, they are:
- development of a custom theme;
- new Magento 2 theme;
- default Luma theme.
#2. Your Magento 1 extensions
The first thing you should do is to understand the functionality you need in Magento 2. Then compare the list of requirements with the vanilla options you get with the second version. Maybe the number of extensions will be much fewer than it used to be before.
The good news is that (a) most of Amasty Magento 1 extensions have already been upgraded to Magento 2. Also, (b) the problem with the incompatibility of 3rd-party extensions from multiple vendors was well solved in Magento 2. Thus, if you run several modules that try to rewrite the same functionality at once, now they rather overlap the core code than override. Moreover, (c) extensions installation/update have been simplified to become cheaper. This is largely due to HTML5, CSS3, Require.js, etc. technologies presented in the new platform version.
#3. Your customizations for Magento 1
Right here the migration gets a little more complicated. However, Magento has taken care of this too offering Code Magento Toolkit. What is it like? It’s a kind of converter that includes special scripts to transform custom Magento 1.x code into its Magento 2 equivalent. It will spare you most conversion actions, though not some manual work. Thus, you’ll still have to edit some files manually to meet Magento 2 requirements.
Major Magento 2 migration risks
Choosing the wrong time
Avoid launching Magento 2 migration on holidays or sales periods. The process directly impacts your website performance. You shouldn’t rely on the skills of an executor, but rather on common sense and your statistics. Choose a lull to solve any glitches in the most cost-effective manner.
Setting unclear priorities
Before getting to work, you need to involve a good analyst who will check your website and tell you what pages bring the biggest revenue. And you need to make sure all the website pages perform smoothly during/after migration. Pay special attention to these ‘golden pages’, as they may cost you a fortune if anything goes wrong. Those very pages that sell best need special attention and higher priority.
Giving insufficient attention to SEO
After migration, you may come across crawling failure. As you know, crawling performs the current URL structure of your website for the web pages being later indexed and added to Google search. So, when you change the structure while migrating to Magento 2, all the old addresses should lead to new ones via 301 redirects. Without successful crawling, your website pages risk being unindexed, and thus, staying unavailable for users.
No data backup. Data loss
One more showing that can influence your website SEO along with crawling and speed is a mess in data. For ease of reference, let’s imagine that Magento 1 data was messed up during migration to Magento 2. As a result, product descriptions, tags, metadata got confused. Will this influence your website position in Google search? Unfortunately, it will. In this case, you risk decreasing traffic flow to your site. And to make matters worse, without data backup, you’ll lose the previous shape of your pages forever.
Insufficient post-migration testing
Right after Magento 2 migration is over, it’s time to test each and every pixel to detect shortcomings and bugs promptly. Insufficient testing poses higher risks to your time and budget.
All-in-all, if you migrate from a supported Magento 1 version (starting 1.7), you are unlikely to face any troubles. It all boils down to setting the data migration tool correctly.
However, some migration-related tasks require more time. They are as follows:
- Module data migration;
- Specific choice of extensions.
Are you up to these challenges on your own?
Recently, we’ve run a poll on whether our customers need such a service from Amasty.
The majority agreed they did.
So, if you skipped the poll but need our help, drop us a line below and stay tuned!
Planning your migration? Pick the mods you need for your Magento 2 store: