Skip to content

E-commerce · Re-platforming

Auto Parts E-commerce Migration

Re-platformed a UK auto parts store onto Hostinger with zero downtime during cutover.

  • WordPress
  • WooCommerce
  • Hostinger
  • Migration
Year
2025
Role
Software Engineer
Type
E-commerce
Stack
6 technologies

Overview

A UK-based auto parts retailer needed to move their WooCommerce storefront off a host that had become slow and expensive to run. The catalogue was large and heavily interlinked — vehicle-fitment data, part numbers and category trees that all had to survive the move intact.

I handled the full migration end to end: auditing the existing install, provisioning and configuring the new Hostinger environment, moving the database and media library, and rebuilding the mail, caching and SSL configuration on the other side.

The riskiest part of any store migration is the cutover, so I staged the whole thing first: a full copy running on a temporary domain, checked page by page against the live site, with search-and-replace on serialised WordPress options rather than a naive database find/replace.

After DNS propagation I worked through the post-move debugging pass — broken plugin paths, permalink and redirect rules, checkout and payment gateway callbacks, and the transactional emails that quietly break on every host change.

The store went live on the new platform without a customer-facing outage, and the client kept their existing theme, plugins and order history exactly as they were.

The problem

Move a live, revenue-generating WooCommerce store to a new host without losing orders, breaking SEO, or taking the shop offline during business hours.

Tags

  • WordPress
  • WooCommerce
  • Hostinger
  • Migration

Responsibility

My role

Everything listed here was mine to deliver — there was no second developer to hand the awkward parts to.

01

Audited the existing WordPress/WooCommerce install and plugin surface

02

Provisioned and configured the target Hostinger environment

03

Migrated database, media library and serialised options safely

04

Staged a full pre-cutover copy and verified it page by page

05

Handled DNS, SSL, caching and transactional email on the new host

06

Post-launch debugging pass across checkout, permalinks and redirects

Tech stack

What it was built with

  • WordPress
  • WooCommerce
  • Hostinger
  • cPanel
  • MySQL
  • PHP

Result

Outcome

What actually changed for the client once the work shipped.

Cutover completed with no customer-facing downtime

Order history, customer accounts and SEO URLs preserved

Checkout, payment callbacks and transactional email verified live

Lower, more predictable hosting cost for the client

To add: real screenshots & metrics

  • Add before/after screenshots of the storefront and admin dashboard
  • Add the real page-load / TTFB numbers before and after the move
  • Add catalogue size (number of products, variations, media items)
  • Add the client name or a short anonymised descriptor, if permitted
  • Add the live store URL if the client is happy to be linked

Edit src/lib/projects.ts → this project's todo array, then delete this panel.

Similar problem?

Got a project that looks like this one?

If any of the above sounds like what you are facing, tell me about it — I have probably debugged something close before.

Available for workDhaka, Bangladesh · GMT+6