A server with Docker
Ubuntu or Debian, 1 GB of memory at least, 2 GB recommended.
Migrate from Plesk
A step-by-step guide to moving a WordPress site from Plesk to FlatRun: restore it into a fresh project, test it, then switch DNS. Most sites take under an hour.
Before you start
Ubuntu or Debian, 1 GB of memory at least, 2 GB recommended.
Take a full Plesk backup of every site, database and configuration before you start.
Note every domain and record. You will point them at the new server at the end.
Lower DNS TTLs a few days ahead so the switch takes minutes instead of hours.
Steps
Run the one-line installer, then open the dashboard and create the admin account.
Install FlatRunThis gives you a clean site to restore into.
A migration plugin moves files and database together. WPvivid's free version works; All-in-One WP Migration, Duplicator and UpdraftPlus do too.
The restore replaces the clean install with your site, including themes, plugins and uploads.
Point the domain at the new server on your machine only, with a line in /etc/hosts (or C:\Windows\System32\drivers\etc\hosts).
Update the A record, and AAAA if you use IPv6, to the new server. Once it resolves, enable SSL on the domain and FlatRun requests a Let's Encrypt certificate.
Keep the old server for a day or two, remove the backup files from both sides, and cancel the Plesk license once the site is stable.
Moving many sites? The project's Migration tab tracks each one: what is inventoried, what has been transferred, and when DNS was cut over.
Use the database service name as the host, not localhost, and check the credentials in the project's variables.
Open the project's terminal and run chown -R www-data:www-data /var/www/html.
Let's Encrypt needs the domain to resolve to the new server. Switch DNS first, then enable SSL.
Change the service's image in the project's Compose file to one with the extension, then redeploy.
Install FlatRun on the new server and start with one site.