# How To Prevent Losing Revenue During Your Ecommerce Re-platform

To avoid losing revenue during an ecommerce re-platform, plan the migration in detail, launch outside peak retail periods, test thoroughly before and after go-live, crawl the old site and map old URLs to new ones with 301 redirects.

- Type: Guide
- Category: Ecommerce platforms
- Author: Nigel Poole, Managing Director, Matter
- Published: 2023-09-20
- Reading time: 3 minutes
- Web page: https://matterdesign.com.au/news/how-to-prevent-losing-revenue-during-your-e-commerce-re-platform

## Why re-platform an ecommerce website?

- An ecommerce re-platform can be a complex project.
- Because ecommerce and consumer trends keep changing, a re-platform can often be a positive move.
- With strong project planning, a capable team and a clear vision, re-platforming can bring more traffic, more sales and happier customers.
- A re-platform also carries risks, including lost revenue during the move from one platform to the next.

## How should a re-platform be planned?

- Moving to a new platform with different frameworks and architecture needs careful planning.
- A detailed migration plan is needed for a seamless transition.
- Matter recommends a migration checklist that can be cross-checked once the migration is complete.
- Work with the consultants or agency to set timelines for each part of the build.
- Consider API connectivity, systems integrations and third-party integrations.
- Put in place a project scope with a project timeline and resource requirements.

## When should a re-platform happen?

- Choose the timing once the process is planned and the timeline estimated.
- Avoid overlapping with significant retail periods, such as Christmas and Black Friday.
- Example: if the re-platform will take 12 weeks, do not start the build in September, or the go-live date may fall in a period of high website traffic.

## How should a re-platformed site be tested?

- Testing during the build and after go-live is an important part of a website migration.
- The agency should have a team dedicated to quality assurance.
- The merchant's own team should also check every function of the website from a user's point of view, especially the path through to purchase.
- Test first on a staging environment (UAT), before the site is live.
- Test again, stringently, once the site is live, because some functions can be affected by the move from staging to live.
- Use many testers, across multiple devices and multiple browsers.

## Why crawl the site before migrating?

- Crawling the site before a migration shows the current URL structure.
- If the URL structure will change, match old URLs to new URLs with 301 redirects.
- Example: product permalinks that include the product category, removed on the new site, so https://example.com/product-category/product-example becomes https://example.com/product-example
- Google's guidance on crawling: https://developers.google.com/search/docs/advanced/crawling/ask-google-to-recrawl

## How can a re-platform avoid 301 errors and protect search rankings?

- A 301 error message occurs on a page visit when the page has moved permanently to a new URL.
- Google penalises websites whose URLs are broken, which can affect the site's ranking on Google.
- One of the main risks of a re-platform is losing Google search position, which risks losing sales from unpaid search results.

Ways to prevent 301 errors:

- Keep content on the new website as close as possible to the content on the old website.
- Redirect all pages correctly with 301 redirects.
- Redirect all blog posts correctly with 301 redirects.
- Spot test from Google Search Console.
- Run a full URL test from the XML sitemap or Search Console.

## Summary

- Thorough planning before the migration and thorough testing after it help keep revenue loss to a minimum during a re-platform.
