Moving to launchroom
Move your apps from your old platform onto a launchroom server one at a time, later move launchroom to another machine, and add a home machine for builds.
Moving to launchroom happens in steps. Each step stands on its own, and your apps keep serving throughout.
Move your apps from your old platform
Install launchroom on a server and move one app at a time: deploy it, copy its variables, import its data, check it, then switch its DNS. Your old platform keeps serving each app until its DNS switches, so nothing goes offline.
Move launchroom to another machine
Once your apps run on launchroom, move launchroom itself with every app, database, volume and domain to another server, also to another CPU architecture. Nothing is lost and no backup storage is needed: apps switch without downtime, each database stops briefly while it is copied.
Add a home machine for builds
A machine at home, including a Mac, can join as a build server. It needs no port forwarding and builds for your other servers.
Concepts
The words launchroom uses for teams, projects, services, connections, environments, previews, staged changes, deployments and servers.
Move apps from another platform
Move apps one at a time from your old platform to launchroom without downtime. Variables, Compose apps, databases and files, then the DNS switch. Umami as the worked example.