Hardcraft

Back to services

Migrations and upgrades

Moving to new hardware, another provider or a newer OS release — with a way back.

A migration is mostly an exercise in preparation. The copying takes an hour; knowing exactly what runs and what it depends on takes the rest.

How it runs:

  • Inventory of services, dependencies and cron jobs
  • Trial migration to a test environment, including a measurement of real downtime
  • A runbook per step, with a rollback plan that has itself been tested
  • Execution in an agreed window, usually outside office hours
  • Aftercare: DNS TTL, certificates, mail reputation and monitoring adjusted

The same applies whether you are jumping from an end-of-life distribution to a supported release or moving between providers.

Is your infrastructure running the way it should?

Half an hour on the phone costs nothing and usually surfaces a few concrete improvements already.

Get in touch