Switching to a different webshop platform
You move safely by first mapping out everything: products, customer accounts, orders and URLs. Then you test in a separate environment and set up 301 redirects before you go live.
A new webshop platform can make your webshop faster, cheaper to maintain or easier to extend. But a migration can also go wrong in all sorts of ways: old links that suddenly show an error page, customers who can no longer log in, or products with missing data. This article shows step by step how to prepare the switch, what to take with you and how to check that everything is right after going live.
Start by taking stock of what you have
Before you move anything, you need to know exactly what is on your current platform. Many business owners only think of products, but a webshop consists of more: categories, filters, customer accounts, order history, discount codes, content pages, integrations and settings for shipping and VAT. What you don't take stock of, you will forget to bring along later.
Make an overview in a spreadsheet with three columns for each item: what is it, where is it now and what is the plan in the new platform. That way you see immediately what you can export, what you have to rebuild and what you deliberately let go. You don't need to move an old promotion or a category without products.
A practical example: a garden products webshop only noticed after the migration that the advice pages for each product were in a separate plug-in. They were not in the standard export and so they were gone. A stocktake beforehand would have made that visible.
- Products with variants, images and attributes
- Categories, brands and filters
- Customer accounts and order history
- Content pages, blogs and terms and conditions
- Integrations with accounting, stock, carriers and payment methods
Choose the right moment and plan a trial migration
A switch works best at a quiet time. Avoid the weeks before your busiest period, such as the holidays or an annual sale. If something goes wrong, you want time to fix it without every hour of downtime costing a lot of revenue.
First do a trial migration to a test environment. Import part of your products and customers, look at the result and note what doesn't come across properly. Often it is about characters in product names, images that don't come along or variants that appear as separate products.
Then plan the real migration for a fixed day, with a clear order of steps. Agree who does what and who decides if a problem comes up. Especially if you work with an external builder, this prevents arguments at the moment it really matters.
Keep your findability with redirects
Search engines know your pages by their web address. If those addresses change and you don't arrange anything, your rankings disappear and visitors get an error page. A 301 redirect tells both visitors and search engines that a page has moved permanently to a new address.
Start by exporting all current addresses. You can do this with a crawl tool, your sitemap or the data from Google Search Console. Place that list next to the new addresses and link each old page to the best matching new page. A product that no longer exists you send to the relevant category, not to the homepage.
A common mistake is to redirect everything to the homepage. Search engines often see that as a weak link and visitors drop off because they don't find what they were looking for. So divide the work: first your most visited pages and products, then the rest.
Keep your address structure as similar as possible
The fewer addresses change, the fewer redirects you need and the smaller the risk. Check whether your new platform allows the same structure, for example the same category paths or product names in the address. Sometimes you can set this, sometimes you can't.
If it doesn't fit, accept the new structure, but record which old addresses go where. After going live, keep testing a sample of old links. Also check that redirects go straight to the final address and not via several steps.
Take texts, metadata and images with you
Besides addresses, your texts also contribute to findability. Page titles, meta descriptions, product texts, category texts and image alt texts should move too. If your platform names those fields differently, check during the trial import whether they end up in the right place.
Also pay attention to technical items that are often forgotten: canonical tags, the robots settings, a new sitemap and structured data such as product markup. A common mistake is that the test environment is blocked for search engines and that block accidentally stays in place at go-live.
After the migration, check that your images still load quickly and have not only been copied but also correctly linked. You only see missing images when you go through a large number of product pages, so look at a sample per category.
Make sure customers can keep ordering and logging in
Customer accounts are sensitive, because passwords are usually stored encrypted and cannot always be transferred. If that is the case with your platform, let customers set a new password on their first visit and explain that beforehand. Otherwise you get questions to customer service and customers abandon their baskets.
Send a short email before the switch about what changes and when. Also say whether order history is kept or, if it can't be, that it is not. If you want to be able to find old orders for returns or administration, keep an export or leave the old system readable for a while.
Test the whole ordering process yourself with real steps: choosing a product, using a discount code, seeing shipping options, paying with iDEAL and receiving the confirmation email. Also test a return and a newsletter sign-up. One broken payment method costs you orders straight away.
Go live and check the first weeks
At go-live your domain points to the new platform. Beforehand, lower the time-to-live of your DNS records so the change takes effect quickly. Don't switch off the old platform straight away, but leave it for a while so you can compare data and still retrieve something.
In the first days, check daily your error reports in Google Search Console, your analytics data and your orders. If you see a sudden drop in visitors or orders, first look for technical causes such as broken redirects, a block for search engines or a payment method that doesn't work.
Keep in mind that rankings can fluctuate temporarily after a migration, even if you do everything right. Search engines have to process your new pages again. So don't make hasty changes to texts or structure in the first weeks, otherwise you won't know what caused a change.
- Check error pages and redirects
- Compare visitors and orders with the same period before
- Test payments and emails again
- Submit your new sitemap to Search Console
More on Webshoptiger
Frequently asked questions
How long does it take to switch to a different platform?
That depends on the size of your range and the number of integrations. For a small shop, allow a few weeks of preparation and for a large shop several months.
Do I have to take all my old orders with me?
Not necessarily, but you must be able to find them for administration, warranty and returns. Otherwise keep an export or keep the old system available for a while.
Can I fully keep my findability?
You can't guarantee that, but with good redirects and carried-over metadata you limit the loss considerably. Temporary fluctuations in rankings are common.
What is the first step I can take?
Export a list of all your current addresses and take stock of what you have. With those two overviews you can plan the rest of the migration.