Migrations

Moving day, without the moving.

Leaving a host feels risky, so most people stay unhappy where they are. We remove the risk: your site is copied, staged, tested, and cut over while the old one keeps serving — and it costs nothing with any plan.

Moving manifest

№ 0042

from
your current host
to
a beacon node · our metal
cost
$0 with any plan
downtime
none
your job
forward one login

handled with care, end to end · fragile: treat as someone's livelihood

The move plan

Five steps, one careful week

Watch your site travel as you read — from the grey box you're leaving to the copper one that's waiting.

old host

beacon-0642

step 01 of 05 — listen & audit

  1. 01

    Listen & audit

    day 0 · your site stays put

    You hand us one login; we inventory everything — files, database, cron jobs, redirects, email records, the plugin nobody remembers installing. You get a written move plan before anything is touched.

  2. 02

    Copy & stage

    days 1–2 · your site stays put

    A complete copy lands on your beacon node behind a private staging URL. Your live site keeps serving from the old host, untouched, while the new one takes shape beside it.

  3. 03

    Test like a pessimist

    days 2–4 · your site stays put

    Forms, checkout, logins, redirects, feeds, SSL — everything gets clicked, submitted, and measured. You get the staging link too; nothing cuts over until you've seen it work.

  4. 04

    The cutover

    day 5 · minutes, not hours

    DNS TTL was quietly lowered days earlier, so the flip propagates in minutes. Both servers answer during the change — whichever one a visitor reaches, they see your site. That's the whole zero-downtime trick.

  5. 05

    Watch & retire

    days 5–35 · heightened watch

    Seventy-two hours of extra-close monitoring, then we help you cancel the old host. A frozen copy of the old environment is archived for thirty days — a parachute nobody has needed yet.

Zero downtime, explained

No magic. Just overlap.

“Zero downtime” sounds like marketing until you see the mechanics. It comes down to three unglamorous habits done in the right order.

01

Parallel running

Old and new servers hold identical copies of your site through the entire cutover. There is never a moment when nobody is answering.

02

The TTL trick

Days before the move, we quietly shorten your DNS time-to-live from hours to minutes. When the record flips, the internet notices almost immediately.

03

Rollback in one move

If anything looked wrong, pointing DNS back at the old host is a single change — and the old environment stays frozen for thirty days, just in case.

Migration FAQ

The questions everyone asks

Asked by every client before their move. Answered here so you can worry about none of it.

Yes. Your old host keeps serving until the very end, and during the DNS change both servers answer with the same site. Visitors never hit a gap — the worst case is that some see the new server a few minutes before others.

Unhappy where you're hosted?

Tell us where your site lives and what's been bothering you. You'll get a move plan and a date — the rest is our job.

Ember $19 · Forge $39 · Foundry $79 — per month, no contracts