← All Quick Wins
Server Management

The Web Server Migration

Migrate an existing web server configuration to a new server (e.g. Apache or Nginx to Caddy), covering up to 5 domains, with HTTPS auto-renewal and a tested rollback plan.

We migrate your existing, live web server configuration to your chosen target server software — commonly Apache or Nginx moving to Caddy, though the reverse direction is equally supported. The new configuration carries forward HTTPS with auto-renewal, HTTP/3 where the target server supports it, and equivalent security headers, and covers up to 5 domains. A tested rollback plan is prepared before cutover, since migrating a live configuration means downtime risk if something is missed. A move to Caddy in particular tends to simplify the configuration meaningfully rather than just reproducing every line of an old Apache or Nginx config verbatim — the point of switching is a simpler config, and we scope the migration with that in mind rather than mechanically translating every directive. This is distinct from a fresh install on a server with nothing running yet; if that's your situation, The Web Server Install is the simpler, cheaper fit.

What's included

  • Migration of your existing configuration to the target server software
  • HTTPS with auto-renewal on the new configuration
  • HTTP/3 enabled where the target server supports it
  • Security headers carried forward and re-verified
  • Coverage for up to 5 domains
  • Tested rollback plan prepared before cutover

How it works

  1. 1

    Book it — pay the fixed price, tell us your target environment

  2. 2

    We deliver — an experienced specialist runs our standard workflow for this exact task; you can watch progress and ask questions

  3. 3

    Hand-off — you get the deliverables, documentation, and a walkthrough if you want one

FAQ

How fast is delivery?
Standard delivery is within 80 weekday hours (≈ 5 working days). Express delivery — within 48 weekday hours (≈ 3 working days) — costs 25% more.
What if the migration breaks something in production?
A tested rollback plan is prepared before cutover specifically to cover this. This is live-configuration work, so the rollback plan is not optional.
How many domains does this cover?
Up to 5 domains are included. Additional domains beyond that are quoted separately.
Will you replicate our old config line for line?
Not by default, especially when moving to Caddy — the point of that move is a simpler configuration, not a mechanical translation of every old directive. We scope what needs to be preserved and what can be simplified before starting.