Magento is a powerful platform that is capable of transacting many millions in revenue every year. However, a poorly-executed move to Magento can quickly wipe out years of gains—made by your investment of money or sweat equity.

In this article, we will discuss Magento 2 migration problems and how you can rectify them.

We have seen this happen way too often and have put together a guide for the most common problems that we have seen. A drop in sales is most often seen in one of two ways:

  • Poor user experience
  • Search engine problems

These problems fall into one of two categories:

  • It was an honest oversight, and usually small in nature.
  • Budget was a big issue and the new website had to be pared back.

Were you promised:

What your Google Analytics should look like...
But this is what you got?

But sadly, it looks like this...

Jump To Detailed Sections:

Overall picture:

If you are being forced to migrate to Magento 2 (due to the end-of-life for Magento 1), or are wishing to switch for an improvement in sales, you must realize you are moving a mature and stable website. This is a very costly process.

To reduce the overall bill, you work with your Magento agency to determine what is needed and what isn’t. You also likely decide that your old website looks outdated and it is quite inexpensive to install a brand new theme that will look beautiful.

You know that some features that you previously built to help customers find what they are looking for aren’t being moved. But, the migration is expensive and you just have to get it done without pulling out a loan.

You launch and the site tanks.

What then?

Real-life stories:

To help illustrate these problems, here are two stories that we have encountered. These seem to embody the majority of problems that we have seen.

Car parts merchant

A merchant in the auto parts industry invested 10’s of thousands of dollars into migrating from Magento 1 to Magento 2. Their old site was clunky and seemed hard to use. To save money, they used a theme from a 3rd-party theme vendor. Now, the site looks slick and cool—which is very fitting for a website selling car parts.

They came to us requesting an audit of their website.

Unfortunately, this is a story of a Magento migration gone bad. Year over year, revenue is down almost 50%. The visitor count is down 38%. The longer that you wait before taking action on such problems, the more likely that the damage is irreversible (ie, all growth becomes new growth which is more expensive).

What was wrong?

  • User experience was not considered. For example, on the old website, this merchant had tables to help customers find what they wanted. The new site contained massive and never-ending lists of products. Try finding your products there—good luck.
  • Major search engine optimization oversights.
Big transitions are scary for merchants. But worse is when those transitions go poorly.
Artisan commodity merchant

Yet another merchant came to us with a similar story. They sell candy made by a famous confectioner. Their website was the fastest-growing part of the business until they switched to Magento 2.

I want to make it clear that Magento 2 is not the problem. Magento 2 is an exceptionally capable platform. It can be customized, modified and transformed to meet just about any business need for any merchant.

This merchant launched on Magento 2. They came to us several months later needing guidance as to what to do. They are very technically capable but wanted direction on what is missing on the website.

Our audit turned up some major issues in the user experience area:

  • Important navigation features were difficult to find.
  • Font size decreased approximately 10%. The majority of revenue came from people who were 55 years old and up. This meant that customers were having a harder time reading text on the website.
  • The old website’s homepage gave helpful directions and a overview as to what products were sold. The new website only showed “new” products. While new products are exciting to the merchant, they usually aren’t as cool to visitors (unless you are Apple).
  • Product images are significantly smaller. While this might not seem like a big deal, for this merchant it is because eye-appeal is one of the biggest and most immediate selling points.
  • Poor details/information about fields in the checkout.

Revenue is down after a new migration—what do I do?

Ensure you can access the old website

When you go-live on the new website, you usually switch the DNS to point to the new website. Your hosting company or Magento agency should be able to help you get the old website up again.

Please make sure to add HTTP authentication (a username and password) to the old website. This prevents search engines from finding this duplicate content and possibly displaying it in search results. You should also add a robots.txt file disallowing all search engine spiders from accessing the page.

Use Google Analytics to begin understanding why this is happening

When we are investigating problems like this, the first thing we do is begin comparing similar data in Google Analytics reports.

  • Year over year
  • Month over month

It is important to match the starting and ending days of the week. For example, if your report period starts on a Sunday and ends on a Saturday, mirror that in the comparison date range (making sure that the number of days is equal). This is critical when looking at smaller ranges of time.

Every report that is discussed here needs to be evaluated in lieu of these date comparisons. This gives you an appropriate perspective of how this actually changed.

Traffic loss = revenue loss

If fewer customers are coming to your website, you will have fewer sales.

You might be excited that your conversion rate might be up. Conversion rate is nothing more than a ratio of visitors to number of sales. If you drop the number of visitors and are left with your loyal customers, of course, that number will look good.

There is a myriad of issues that could cause this. Episode #1 of our podcast, Actionable Insights, dives into one of the most common link here. This is very important and our podcast notes go into great detail about this.

If the old site had good SEO and the new site is struggling, something technical was probably not considered.

Most Magento 1 to Magento 2 migrations involve copying all data (products, categories, CMS pages, orders, etc.). This means that most of your hard work writing content for your website should carry over.

One thing that is often missed is ensuring that your content is formatted properly on the new website.

How do you determine where traffic is being lost?

Start with the Acquisition > Overview tab. Look through each of the channels:

  • Direct: people who type in your website’s address into their URL bar. This will rarely be lower unless your loyal visitors now dislike the new website.
  • Organic Search: people who click into your website from Google/Bing, etc. (are there any other ones that people actually use?).
  • Referral: people who are reading a blog or StackExchange, for example, and click into your website.
  • Email: people who click into your website from an email.
  • Social: people who navigate to your website from Facebook/Twitter/LinkedIn, etc.
  • Paid Search: the ones you pay dearly to get to come to your website: Google Adwords, Bing Ads, etc.

Organic Search is one of the biggest areas to focus your attention:

  • Do you notice an increase in the bounce rate? This means that there are on-site problems or a poor design that is not resonating with users.
  • Do you notice a decrease in visitors? This often points to missing redirects or massive content changes that Google does not understand. See episode #1’s note of our podcast, Actionable Insights (Link)
The #1 issue I see is that redirects are not in place for pages on the old website to pages on the new website. Again, see our podcast episode where talk in-depth about this.

Poor user experience = revenue loss

What Google Analytics metrics are important to evaluate:
  • Users: this is a no-brainer. If the number of people coming to the website is down, likely this is bad news for a website.
  • Bounce rate: this is how many people visit your website and immediately leave. High bounce rates mean irrelevant content or problems on the website. A bounce rate that has spiked up is dangerous for SEO as Google will begin to take notice that this page is no longer relevant for the intended audience.
  • Pages / Session and Average Session Duration: these metrics indicate how engaged a user is when they come to your website: do they click from page to page or spend a long time reading?

What Google Analytics reports are important to first evaluate:

I want to present my favorite reports for first beginning to understand why a Magento migration has gone poorly.

  • Investigate individual pages (Behavior > Site Content > All Pages). Which pages have taken the greatest hit in pageviews, increase in % exit or increase in bounce rate? This often points to design issues related to content styles that were not transferred with care.
  • Investigate which demographics (Audience > Demographics) are doing poorly. This is often due to general on-site “improvements” (like a beautiful new theme) that actually degrade the usage for visitors.
  • Investigate which geographies (Audience > Geo) are most impacted. This could be because the shipping policies are hard to find (the merchant is well-known in New York, but California visitors are leaving the website).

Compare the websites

Yes, you need to open two browser windows, #1 on your old website and #2 on your new website. Look through every critical page. What differences do you see? The closer you kept your website to the old design, the easier it will be to identify problems on the new.

Did you used to have special tools to help people browse your old website?

As presented in the overall picture above, you likely have a budget, and for many, it is a tight budget. You don’t have the money to spend on truly improving the new website (or at least making sure functionality doesn’t go backward), so you need to cut the ancillary features.

One of the biggest features I’ve seen cut is tools to help people find products on a website (what actually was helping drive sales on a website). This is often in the form of:

  • Wizards, tables or custom grids to provide context for locating a product.
  • Custom product page layouts.
  • Layered navigation (category side bar) features.
  • Buying guides or comparison tools.

If the problems with this list are content-related, that means that the agency did a poor job implementing this feature (usually thanks to budget constraint/pressure from the merchant or underbidding the project).

If elements of this list were present on the old website, and no longer on the new, this is often a contributing factor. Customers are no longer able to find products as quickly as they used to be able to find them.

Step through the website, one page at a time.

Focus on the high-value pages (ones with high traffic or revenue). At this point in the game, don’t diagnose—take notes and move on.

Slow down. You have likely used this new website for months now and are familiar with the intricacies of using it. Compare every element on the old site with the new site. This is not the time for optimization. Instead, focus on what is different?

Get help. Enlist your customers. You can bribe them with a $25 gift card. Watch them navigate the website (Google Meet is a great way to do this). Where do they stumble? As you get a trendline going of 4+ users having the same problems, take immediate action to get these problems resolved.

So, how do I get this fixed?

I wish we could now give you the steps on what to do. Unfortunately, there would be so many possibilities, we wouldn’t have a chance to concisely present them all to you.

The good news is that you just diagnosed the major problems on your website.

Getting these fixed involves talking with a qualified partner who can help you the best course of action.

Please feel free to get in touch with us to share your story. We promise to listen and sympathize.

SwiftOtter, Inc.
It relates to Magento 2.
Joseph Maxwell - president / senior developer at Swift Otter

President / senior developer at SwiftOtter - @swiftotter_joe