A nine-year-old website stopped being a business risk and became a quiet partner.

The challenge.

• The site was nine years old and hosted by whoever quoted the lowest price the week it launched. By the time we were brought in, no one inside the company even had the login to the host.
• There was no staging environment, so every content change went straight to the live site. The team held its breath each time.
• Backups were a maybe. If the site went down on a Friday, no one could say whether it would come back, or how far back.
• Plugins and WordPress core were years out of date, and a browser SSL warning had started turning visitors away. The site had quietly become a business risk that no one owned.
• When something broke, the team emailed a freelancer who replied when he replied. There was no name to call and no sense of when help would come.

What we did.

1. 1

   Migrated to managed WordPress on Kinsta, with no downtime on cutover.

   We moved the site to managed WordPress hosting on Kinsta (Google Cloud), planned the DNS cutover carefully so search rankings, redirects, and tracking carried over intact, and installed a valid SSL certificate so the browser warning was gone the same day. The public site never went dark during the move.

2. 2

   Stood up staging, daily backups, and uptime monitoring.

   Every change now goes to a staging copy first, gets reviewed, then ships to production. Kinsta takes automatic daily backups with one-click restore points, so a bad afternoon is reversible. Uptime monitoring watches the site around the clock and pages us before the client ever notices a problem.

3. 3

   Put core, plugins, and security on a fixed maintenance schedule.

   We brought WordPress core and every plugin current, then kept them current on a scheduled cadence rather than a panic. Updates are tested on staging before they reach the live site, so patching closes security holes without breaking the storefront pages the sales team relies on.

4. 4

   Gave them one team to call, with a 2-business-hour reply.

   Support runs through a single clear path: portal, email, or phone. We reply to every request within 2 business hours, the same senior team each time, people who already know this site. Over nine years that has covered content updates, new product pages, form fixes, and the occasional 'is this normal' question.

The outcome.

• Nine years on the same managed plan, with no emergency replatform and no scramble to rescue a site no one could log into.
• Uptime held at 99.95% across the last twelve months, with monitoring catching issues before staff or buyers saw them.
• Median page load dropped from 2.9 seconds to 1.1 seconds after the Kinsta migration, on the same content.
• Every support request answered within 2 business hours, by a team that already knows the site, so the marketing lead stopped being the site's de facto IT department.
• Daily backups and staging turned 'we hope it comes back' into 'we can restore it in minutes,' and the site moved from a standing risk to something the owner no longer thinks about.

Questions about this work.