Website Migration to a New Host: What the Work Involves and What You Get

Website Migration to a New Host is a hosting & devops service from Livin Services: move your site to better hosting without a day of downtime or a week of broken email. You get current-state review and target architecture for website migration to a new host, provisioning with infrastructure as code where it fits and environment separation across development, staging and production, all of it written into a fixed scope before anyone starts work, and it usually takes 2 days–1 week.

This is the long version of that: what actually happens, what lands at the end, and how to tell the difference between website migration to a new host done properly and website migration to a new host done in a hurry.

What Website Migration to a New Host is for

Move your site to better hosting without a day of downtime or a week of broken email. That is the whole point of it, and it is worth being blunt about, because a lot of hosting & devops work gets sold on activity rather than on the thing it changes.

If none of the following sound like your situation, this probably is not the work to buy — and further down we say what to look at instead.

• Deploys happen at midnight because everyone expects breakage
• One person knows how the server is configured and they are on holiday
• The site goes down and you find out from a customer
• Your hosting bill grows and nobody can explain which service caused it

What you get

Every item below is written into the scope before anyone starts. Anything outside it is quoted separately rather than absorbed quietly, which is what stops a fixed price drifting.

• Current-state review and target architecture for Website Migration to a New Host
• Provisioning with infrastructure as code where it fits
• Environment separation across development, staging and production
• Deployment pipeline with rollback and health checks
• Monitoring, log aggregation and alert routing
• Runbook covering deploys, incidents and recovery
• A full copy staged and tested on the new host before anything changes
• DNS TTL lowered in advance so the cutover is minutes, not hours

What is different once it is done

• Website Migration to a New Host is in place and documented, so your team can change it without calling us
• Current-state review and target architecture for Website Migration to a New Host delivered against a written list you can check line by line
• Every account and credential in your name, with nothing on our infrastructure
• A clear record of where you started, so the effect of the hosting & devops work is measurable rather than a feeling
• One fixed price paid, with no retainer required to keep it working

How the work runs

1. We look at what you actually have

Before anything is quoted we go through your current rsync setup and whatever else touches it. Half the time this changes the recommendation — the thing you asked for turns out not to be the thing that is costing you.

2. The scope gets written down

Every line of Website Migration to a New Host that will be delivered, in plain English, with one fixed price and a date. Exclusions are listed as explicitly as inclusions, because the argument three weeks in is always about something nobody wrote down.

3. Build, in the open

You see move your site to better hosting without a day of downtime or a week of broken email take shape rather than being shown a finished thing at the end. If something we assumed turns out to be wrong, you hear it the day we find out.

4. Tested against real conditions

Current-state review and target architecture for Website Migration to a New Host is checked on real devices and real data, not just on the machine it was built on. A thing that works only in ideal conditions is not finished.

5. Handover, then it is yours

Documentation written for your team, every account already in your name, and a walkthrough. Typical end to end: 2 days–1 week. Nothing rolls over into a monthly fee you did not ask for.

The tools it runs on

rsync, Cloudflare, Certbot, MySQL.

We work in the tools you already own wherever that is sensible. Where we recommend adding something, you own the account from the day it is created — not us, and not a reseller.

What we check before calling it finished

• Every item in the Website Migration to a New Host scope ticked off against the written list, in front of you
• Tested on a real mid-range phone, not only on a desktop browser
• Checked against your existing rsync setup so nothing that already worked has quietly broken
• Provisioning with infrastructure as code where it fits verified end to end rather than assumed
• Keyboard navigation and screen-reader labelling checked on anything interactive
• Handover documentation read back by someone who did not build it

How long it takes

Usually 2 days–1 week. The date goes in writing with the scope, and the commonest reason it slips is not the build — it is access and approvals arriving late, which is why we ask for both up front.

Questions people ask before buying

What is Website Migration to a New Host?

Website Migration to a New Host is a hosting & devops service from Livin Services. In one line: move your site to better hosting without a day of downtime or a week of broken email. It's a defined piece of work with an agreed finish line, not an open-ended retainer, so you know what you're buying before you commit to it.

What is included in Website Migration to a New Host?

Website Migration to a New Host covers current-state review and target architecture for website migration to a new host, provisioning with infrastructure as code where it fits, environment separation across development, staging and production, deployment pipeline with rollback and health checks, monitoring, log aggregation and alert routing, runbook covering deploys, incidents and recovery, a full copy staged and tested on the new host before anything changes, dns ttl lowered in advance so the cutover is minutes, not hours and email, dns records and ssl verified after the move — the two things most migrations break. All of that gets written down before we start, so you know exactly what's landing and what isn't. Anything outside the list gets quoted separately — we won't quietly absorb it and we won't quietly bill for it either.

What is not included in Website Migration to a New Host?

Anything not named in the written scope. In practice that usually means ongoing management after handover, content and copy you have not supplied, third-party licence and subscription costs, and work in other disciplines — those are separate services with their own scopes. We list exclusions explicitly rather than leaving them to be discovered halfway through.

How long does Website Migration to a New Host take?

A typical Website Migration to a New Host engagement runs 2 days–1 week from kickoff to handover. That covers discovery and scoping, build or implementation, review with your team, and a final QA pass. Larger or multi-market builds extend this and we say so during scoping rather than after.

Can Website Migration to a New Host be delivered faster than 2 days–1 week?

Sometimes, if the scope is reduced rather than the care taken. We will tell you which parts can be deferred to a second phase to hit a date. What we will not do is compress testing and review to make a deadline look achievable — that moves the cost from the timeline to the month after launch.

How is Website Migration to a New Host quoted?

One fixed price against a written scope. Not an hourly rate. What moves that number is how many templates, integrations and awkward edge cases are involved — not how long we happen to take, which is our problem to manage, not yours. There's no price list because a real quote depends on your situation. Tell us what you need and you'll get a written scope and a fixed figure back, with anything that could change it flagged upfront rather than appearing on an invoice later.

What we need from you, and when

The commonest cause of a slipped date on this kind of work is not the build. It is access and approvals arriving late. So this is written down as plainly as our side of the deal:

• Access to rsync — Admin or collaborator access, created in your account so you can revoke it whenever you like. The single most common cause of a slipped date on Website Migration to a New Host is access arriving two weeks after kickoff
• One person who can decide — Not a committee. Someone who can approve a direction without escalating it. Where approvals need three people, we build that into the timeline rather than pretending it is free
• Whatever content the scope depends on — Copy, images, product data, brand assets — whichever apply. If you would rather we produced them, that is a separate scope and we will say so before you assume it is included
• An agreed definition of finished — We write down what "done" means for Website Migration to a New Host before starting, and both sides sign off on it. It is the cheapest thing you can do to avoid a dispute at the end

A note on access and approvals

Two practical notes. Send individual accounts rather than a shared login — individual access can be revoked per person at handover, and a shared password is the most common way a business quietly loses control of its own systems. And name one person who can approve decisions. Not a committee. A project with three approvers moves at the speed of the slowest one, and everybody ends up frustrated with the wrong party.

What we check before we call it finished

"Done" is the word that causes the most arguments in this industry, because it usually means something different to each side. Ours means all of the following are true, and you can hold us to the list:

• Every item in the Website Migration to a New Host scope ticked off against the written list, in front of you
• Tested on a real mid-range phone, not only on a desktop browser
• Checked against your existing rsync setup so nothing that already worked has quietly broken
• Provisioning with infrastructure as code where it fits verified end to end rather than assumed
• Keyboard navigation and screen-reader labelling checked on anything interactive
• Handover documentation read back by someone who did not build it

Note what is in there and what is not. There is no line about you being happy — not because we do not care, but because a definition of done that depends on a feeling has no end. If something is wrong against the scope, we fix it. If something outside the scope turns out to matter, we quote it as a line rather than absorbing it quietly, because absorbed work is how a fixed price stops being fixed.

The tools, and who owns them

rsync, Cloudflare, Certbot, MySQL.

Where you already own something that does the job, we use it. Where we recommend adding something, the account gets created in your name, on your billing, with your team as administrators from the first day — not ours, and not a reseller's. This is not generosity. It is the single thing that determines whether you have a supplier or a dependency.

The same applies to everything we produce. Source files, configuration, documentation, credentials: yours, handed over as we go rather than held until a final invoice clears.

Where this discipline actually stands

Infrastructure work is invisible when it is right, which makes it easy to under-buy and easy to oversell. Our rule is that nothing counts as done until it has been tested in the failure case, not the happy one: a backup that has been restored, a firewall run in monitoring mode first, an alert that someone has agreed to act on. And it all lives in your accounts, because a supplier holding your infrastructure holds your business.

What we will not do

Worth being explicit, because these are the promises you will hear elsewhere:

• We will not guarantee a commercial outcome. Move your site to better hosting without a day of downtime or a week of broken email is what the work delivers. What that turns into depends on your market, your pricing and your competitors as much as on us.
• We will not quote a number before understanding the scope. A price given in the first five minutes is a price with the risk padded in, and you pay for the padding.
• We will not take work we do not think will help. That has cost us enquiries and it will again.
• We will not hold your accounts, your data or your files as leverage.
• We will not add a tool where removing one would do. We say "remove this" fairly often, and it is always less to invoice for.

When website migration to a new host is not the right thing to buy

• You need it faster than 2 days–1 week. We will not compress website migration to a new host into a weekend by skipping the testing, and an agency that agrees to is telling you which corner they plan to cut
• You are not committed to rsync. Most of the value here comes from working properly inside rsync, so if you are mid-way through deciding whether to move off it, decide first — otherwise you are paying us to improve something you are about to replace
• What you actually want is move your site to better hosting without a day of downtime or a week of broken email guaranteed as an outcome. We will not sign that, because the result depends on your market, your pricing and your traffic as much as on the build. We guarantee the scope, the date and the quality of the work
• You want someone to take it away and report back monthly. This runs as a fixed piece of work with a written scope and a handover, not as a retainer — if you want a permanent hosting & devops function, hiring is usually cheaper than us

If any of those describe you, the useful thing is usually a conversation rather than a project. Tell us what you are trying to change and we will point at whatever we think the real lever is, including when that is something we do not sell.

How we would want to be compared

If you are getting other quotes, and you should, compare the scopes rather than the totals. Ask each supplier the same three things: what exactly is included and excluded, what does done mean, and who owns the accounts at the end. The answers separate suppliers far more reliably than a portfolio does.

And if someone else's scope covers the same ground for less, take it. We would rather you did that than start something on a number nobody is comfortable with.