Migration

What the flat fee covers

• Websites and application files, with permissions and ownership preserved
• MySQL/MariaDB and PostgreSQL databases, with a final sync at cutover
• Web server, PHP and cron configuration rebuilt on the new server
• Mailboxes when the old server hosts mail (IMAP sync)
• TLS certificates reissued on the new server
• A test pass on a temporary hostname before any DNS change

Moves that need application changes, version upgrades (for example PHP 7.4 to 8.3), or more than a handful of applications are quoted separately before work starts.

How a cutover is planned

1. Inventory. We list what runs on the old server: sites, databases, cron jobs, mail, firewall rules and anything listening on a port.
2. Lower DNS TTLs. At least 24 hours before cutover, DNS TTLs drop to 300 seconds so the switch propagates quickly.
3. Initial copy. Files and databases are copied while the old server stays live.
4. Test. You check the copy on a temporary hostname or through a hosts-file entry.
5. Cutover window. Writes pause briefly, a final database and file sync runs, and DNS moves to the new IPs.
6. Watch and keep the old server. We watch logs and error rates for the first day. Keep the old server for at least a week before cancelling it.

cPanel to cPanel

With cPanel on both ends, accounts move with cPanel's own transfer tool, which carries files, databases, mail and DNS zones together. That is why it is free with a three-month commitment to Essential or Pro Managed.

What we need from you

SSH or control panel access to the old server, access to your DNS provider (or someone who can make the changes on the day), and a cutover window when a few minutes of read-only time is acceptable. Never send passwords through our website forms; we will set up a secure way to exchange credentials.

For a do-it-yourself move, our migration guide covers the same steps.