So you've been using Coolify (or Portainer, or any other agent-based tool) and you're ready to try something that installs nothing on your server. This guide walks through migrating your applications to DeployOS a native desktop app (macOS + Windows), not a CLI or a web panel running on your box.
Why Migrate?
Before we dive in, here's what you gain:
- Zero resource overhead no agent process running on your server, ever
- True portability DeployOS talks to any server over plain SSH; move servers without reconfiguring an agent
- One license, unlimited servers no per-node pricing games
- Nothing left behind uninstall the app and your server is exactly what it was: Docker, your reverse proxy, your containers
Prerequisites
- The DeployOS desktop app (download) free tier works with no card
- SSH access to your target server (key or password)
- Your existing Docker Compose setup on that server
Step 1: Add Your Server
Open DeployOS Servers Add Server, and paste the IP + your SSH key (or password). DeployOS connects directly over SSH; nothing is installed yet.
Step 2: Scan Instead of Wiping
This is the part that's different from a clean migration: you don't have to tear Coolify down first. Click Scan on the server card and DeployOS runs Discover & Adopt it inventories what's already running (Docker version, reverse proxy, every compose project, any databases it can detect) and tells you exactly what it found, without touching anything.
If Coolify's own proxy already owns ports 80/443, DeployOS's bootstrap step recognizes that and skips installing a second one it won't fight Coolify for the ports mid-migration.
Step 3: Adopt Your Apps
From the Discover screen, either adopt individual containers one at a time or use Adopt everything to import every compose project (and detected database) on the server as a managed DeployOS app in one click. Nothing is rebuilt or restarted during adoption DeployOS just starts tracking what's already running.
Step 4: Cut Over for Real
Once an app is adopted, edit it to point at its GitHub repo (adoption can't know your repo URL, so this field starts blank) and DeployOS takes over future deploys: push to your branch and it rebuilds, health-checks the container on its real port, and re-publishes the proxy route automatically correcting the route if the app ends up listening on a different port than expected.
When you're ready to fully retire Coolify's agent, remove it from the server. DeployOS never depended on it.
What About Databases?
If DeployOS's scan detects a database container it doesn't yet have credentials for, the Databases page lets you set them so backups and the in-app SQL browser work. From there, on-demand or scheduled backups (with optional offsite S3-compatible push) run the same way for every engine Postgres, MySQL, MongoDB, Redis, MSSQL.
Moving to a Different Server Entirely
If you're not just migrating tools but also moving to a new box, DeployOS's Move to another server action transfers an app containers, volumes, and data included and re-resolves the correct route on the target automatically.
Next Steps
Once you're on DeployOS, the rest of the toolbox is there whenever you need it: one-click rollbacks (last 3 builds cached, no rebuild), a 9-step App Doctor that explains what's broken in plain English, scheduled backups, and 250+ one-click app templates for everything else you might want to self-host.
Your server, your keys, nothing installed but Docker and your proxy. Welcome to DeployOS.