When is the best time to migrate to Magento 2? A few years ago. The second best time for Magento migration is now!
The necessity to upgrade to Magento 2 is more urgent than ever. On June 30, 2020, Adobe officially ended support for the Magento 1 release line for both Magento Enterprise (Commerce) and Magento Community (Open Source).
What does it mean to the ecommerce business owners? If you don’t migrate Magento 1 to 2, you shouldn’t expect any official patches or security updates. Upgrading to the latest release is a great opportunity to experience the most up-to-date version that offers new functionality, better performance, and advanced built-in security options.
Having successfully performed more than 40+ migration projects, Elogic team has covered all the information you may require to avoid unwanted expenditures and data losses during migration. In this guide, we’ll outline the clear roadmap to a successful Magento 1 to 2 migration.
Let’s jump-start your Magento migration!
Magento 2 delivers a modern, scalable ecommerce solution for businesses of all sizes. It also offers unmatched flexibility and customizations. Compared to its former edition, Magento 2 can process more orders per hour on the same hardware with faster server response times, which provides customers with a stress-free experience.
The list of Magento 2 advantages can go on and on, but you have to know only one thing. By staying with Magento 1, you not only risk customer data, but also lose your competitive edge because new features and innovations will only come out for a new platform version.
According to a ServiceNow study, 57% of cyberattack victims reported that their breaches could’ve been prevented by installing an available patch. And 34% of those respondents were aware of the vulnerability before they were hacked.
The vendor is no longer supporting any official security patches for Magento 1. If you had mixed feelings before, it’s time to embrace change, because otherwise, you’ll be a sitting duck for hackers.
Obsolete platforms cease to produce and support new features. A merchant can surely start writing custom extensions and modules to save the store on an old platform. But not until ecommerce architecture becomes a bundle of calls to backlog and legacy code resembling a bowl of spaghetti that slows down the back-office processes and affects website traffic.
Because Magento 1 will no longer be supported, a merchant will have less room for innovation and less possibility to beat competition. Replatforming to Magento 2 will address this issue and give the opportunity to outgrow and outperform even your past self!
The latest Magento version comes supercharged with user-friendly, versatile features. Now that Adobe and Magento are working together, we’ll see closer integrations with marketing and sales platforms.
Related article: Magento 1 vs Magento 2: The Reasons To Upgrade To Magento 2
Our aim is zero downtime, but there will be some downtime (a matter of minutes). The process is fairly straightforward and a matter of following an established checklist.
Just to be on the safe side, you can prepare and send out an email to your customers to inform them of the day and time your site will be unavailable. Monitor the time with the least activity on your website and schedule the risky parts of migration for then. It might be inconvenient for your technical guys, but will surely slip your audience’s attention. Just imagine their surprise when they see a beautiful, brand-new store next time they visit you!
Yes, you can migrate almost everything. With the help of the automated Data Migration Tool, you can migrate orders from Magento 1 to Magento 2 as well as products, customers, settings, store configurations, and promotions.
The only option to get the rest zoomed over is to do it manually. Manual migration is required for:
To take advantage of the architectural advances in Magento 2, developers need to manually port custom code and extensions to Magento 2.
You must manually create credentials for SOAP, XML-RPC, and REST in Magento 2.
Media assets include, for example, images for products, categories, WYSIWYG editor, and so on. You must copy these manually from the <your Magento 1.x install dir>/media directory to the <your Magento 2 installdir>/pub/media directory.
Layout updates implemented in Magento 1.x cannot be used in Magento 2. You must migrate the following manually: XML in CMS category pages in the Magento Admin; Layout updates specified in widget instances.
We sometimes get this question, and the TL:DR is — given the fact that you’re not a Magento developer, you’ll need to find a reputable Magento 1 to Magento 2 migration service provider.
The Magento 2 Data Migration Tool is meant to help you efficiently and securely transfer data such as product, customer, and order data, store configurations, and promotions. It is one of the key components of the migration process and is intended to ensure minimal downtime so you can get up and running quickly.
However, the databases that need to be transferred may not be structured properly. For example, if you have customized data fields, the databases have to be adjusted and in some cases, rebuilt, to guarantee the transfer goes smoothly. There are also other parts to the migration process, like migrating themes, extensions, and custom code.
Plus, there are lots of things that can go wrong. That’s where Magento experts can be invaluable — they can go through your site, perform an audit, migrate settings, and determine the scope of work needed to get everything working properly. The data migration tool is powerful, but only in the hands of certified Magento developers.
Magento 2 migration includes four components: data, extensions and custom code, themes, and customizations.
Before any code is written, the stakeholders, internal team, and external team have to sit down and map out the process so everyone is on the same page. The more details you write down, the more time you’ll save on development and post-deployment.
With our clients, we split up planning into three stages:
It is highly recommended to perform each step of migration and develop all related projects in a separate environment (on an allocated server) so that your current store can continue operating without downtime.
At this point, we prepare a test development environment and install the default Magento 2 platform (Open Source or Commerce), and configure the version control system (Git/SVN) to make sure everything is ready to run the project. It’s important to involve a good DevOps engineer at this step.
This is where we take our migration plan with the mapped extensions and install the corresponding Magento 2 extensions (if applicable). At this point, we also develop custom extensions or additional features, such as Magento credit card payments, one-step checkouts, custom ERPs, etc.
A very important step in the process because it’s the bulk of the information that you need to transfer. As we mentioned before, Magento includes an automated tool for transferring only the data existing in Magento by default: (everything except files, layouts, media, custom code, and control access configurations).
The themes for the older and newer version of the platform are incompatible. It is possible to copy your current theme, but this will require some elbow grease, and we highly recommend updating the design because so many more features are available in Magento 2.
If time is a concern, we also suggest using a default theme available in the Marketplace.
After finalizing and testing the design, we set up the hosting server according to the new system requirements for Magento 2. Once we optimize the server for Magento, we can perform a final database synchronization so no orders or customers get left behind in migration.
Once you’ve tested the final version and ensured everything works, the store is ready to launch.
This is the last step of migration — launch day.
If everything was done correctly and according to the plan, your engineering team will perform a smooth transition to the new store so you can start selling and shipping products right away.
The full workflow breakdown of migrating from Magento 1 to 2:
Planning and auditing go a long way in mitigating any risks.
The available tools allow you to migrate customers from Magento 1 to Magento 2, including accounts, passwords, orders, etc, in an encrypted format. That’s why data security should be one of the last things on your mind.
Apart from that, there are some pitfalls you should be aware of. We describe these pitfalls in more detail in our article — 7 Major Pitfalls You May Face with Magento Migration.
Here’s a brief look:
There’s no end in sight if there is no definition of done — there have to be requirements for a successful migration. Involve all of your stakeholders and make sure the internal and external teams are working together.
Magento 2 is a brand-new platform, which means you will have to invest a fair amount of money to get the most out of it. Let’s find out the cost to upgrade!
The cost of redesigning your store will vary depending on the complexity of the design. For example:
We’ve compiled an in-depth article on website redesign costs where we categorized redesign into components and did the math.
Magento has already deleted all M1 extensions from the marketplace. Thankfully, most extensions are available for M2 so you won’t have to waste time searching for new options. This makes the process considerably easier.
This is a set of extensions we installed for a client to give an idea of what you may end up paying.
|One Step Checkout||$299|
|Abandoned Cart Email||$149|
|SMTP Email Settings||$259|
|Admin Actions Log||$249|
|Follow up email||$299|
|Automatic Customer Group Switcher||$259|
|Magento 2 Google Analytics||$99|
|Out of Stock Notification||$229|
|Magento 2 Mega Menu||$179|
Many clients prefer to fully customize their merchant experience with optimized solutions for their needs. Our team has worked on projects to customize out-of-the-box tools and open-source extensions. You can take a look at our portfolio to read the details for each case study.
Do you have custom coding for modules or extensions on your existing Magento 1 store? If you want it to work the same way in Magento 2, it has to be refactored or rewritten.
This isn’t a money grab for developers — a lot has changed since Magento 1.x. Magento 2 supports PHP 7, new caching technologies, and a host of other things. You’ll save more in the long run by optimizing the performance.
A lot longer than you think.
It’s difficult to say exactly how long it will take without evaluating and planning. This is why the timing is so vital. If you start planning too late, you’ll be caught between a rock and a hard place. So start planning ASAP.
We’re always available to help guide you through the migration process, so please feel free to contact us with any questions.
Here’s the breakdown of each stage of migration:
|Creating a migration plan||3 weeks|
|Preparing a testing environment||1-2 days|
|Installing extensions and custom development||3 weeks|
|Data migration||1-2 days|
|Launching plan and additional database synchronization||1-2 days|
|Magento 2 store launch on a live server||1 week|
|Total migration time||Approximately 2-3 months|
Please keep in mind that this is a rough estimate. If you run a small business, migration can be way faster, and on the opposite end of the spectrum, large businesses may require twice as much time to migrate.
Both Magento Open Source 2 and Commerce 2 have significant improvements over Magneto 1. But since you’re migrating, why not migrate to Magento Commerce? Is Magento Commerce that much better?
Earlier this year, Adobe commissioned Stax, a global strategy consultancy, to evaluate how merchants benefited by migrating from Magento Commerce 1 and other competitive solutions to Magento Commerce 2.
We’ll let the numbers do the talking.
Also, when you upgrade to Magento Commerce, you can replace custom code with third-party extensions. But again, your choice will depend on your needs.
To get a better understanding, take a look at our Magento Commerce vs Open Source Edition Comparison. You can also consider the cloud-hosted version of the platform — Magento Commerce Cloud.
Hopefully, after reading this article you have a better understanding of what’s involved with Magento 2 migration. To reiterate: