Move to SrvYard without starting from a blank page.
Your old panel knows things the server does not: deploy scripts, daemons, scheduled jobs, domains. The server knows what is really running. SrvYard reads both, shows you what it found, and changes nothing until you say so.
# what the import does
source ploi | vito
token read-only, checked with one read call
kept encrypted for an hour, deleted when you finish
env files only if you ask, only for the sites you tick
scripts shown next to their translation, never run
scan no changes to the server
old panel untouched
01Two halves
use both, in this orderDrafts from a read-only token
Paste a read-only API token for Ploi or VitoDeploy. SrvYard lists the servers it can see, reads the ones you tick, and shows a plan: servers, sites, daemons, scheduled jobs, databases and firewall rules, each with its own tick box. Deploy scripts appear beside their translation into SrvYard’s own, so you can see what changed.
Nothing is installed by this step. Servers wait for access, and sites say they need provisioning.
Read what is actually on it
Connect the server, then scan it: web server and PHP configuration, processes, background workers, cron, databases (metadata only), certificates, firewall, application folders and git remotes. You choose what the scan may read. Private keys, database passwords and password hashes are never read. Then you confirm each site and SrvYard takes it over.
This half works for any panel, because every panel drove an ordinary Ubuntu machine.
02Where you come from
a page per panelServers, sites, deploy scripts, queue workers, cron jobs and databases from a read-only token.
Your own VitoDeploy, read through its API.
No API import: connect the server and scan it.
No API import: connect the server and scan it.
Anything that is an Ubuntu machine with Nginx and PHP can be scanned and adopted.
03What is never copied
because no panel API will give it to you| Item | What happens |
|---|---|
| Passwords and private keys | Not readable through any panel API. Connect the server with SrvYard’s own key instead. |
| Environment files | Read only if you switch it on, and imported only for the sites you tick. Key names alone can be read without the values. |
| Deploy scripts | Saved as drafts. They run on the server only at a deployment you start. |
| The old panel | Never written to. Delete the token there when you are done. |
04Check this before you start
Room on your plan
Imported servers and sites count against your plan’s limits. Hobby holds one server and three sites.
A fresh server where you can
Provisioning installs and configures software and can overwrite what is there. For a busy server use the scan, which changes nothing.
Your own DNS and webhooks
Git webhooks and DNS records are yours to move. Do it per site, after the first deploy works.
05Migration questions
answers from the docsCan I migrate from Ploi or VitoDeploy?
Yes. A read-only token lets SrvYard draft your servers, sites and settings, and you then connect the real server and adopt its sites. Nothing is changed in the old panel. See Migrate from Ploi or VitoDeploy.
Can I move over from another panel?
Yes. SrvYard can read Ploi or VitoDeploy with a read-only token and turn what it finds into drafts, then scan and adopt the real server. Nothing is changed in the old panel or on any server. See Migrate from Ploi or VitoDeploy.
Can I manage a site that was not created in SrvYard?
Yes. A read-only scan finds the sites on a connected server and registers them where they are, without moving or restarting anything. You then take over one capability at a time, and every step can be rolled back. See Adopt a site that is already on your server.
Will SrvYard change a server that already has sites on it?
It can. Provisioning installs and configures software and may overwrite what is there, so use a fresh machine where you can. For a busy server, use the Import / migrate page, which scans without changing anything. See Adopt a site that is already on your server.
Can I move a site to another server?
There is no one-click move. You build the site on the new server, check it, then switch DNS, which avoids downtime if you follow the order in the article. Remember to switch off queue workers and the scheduler on the old one. See Delete, rename or move a site.
Import one site. Keep the old panel running until it works.
Free: 1 server, 3 sites, 100 deploys a month. Read the docs first if you prefer.