How to migrate to Linode
Moving an existing site to Linode — what they handle for you, what you'll do yourself, and the safe order to do it in.
Migration Prep: Back Up and Lower TTL
Start with a full backup of your site files and database — Linode’s support won’t handle this for you (support is ticket/phone, no listed migration service). Lower your DNS TTL to 300 seconds at least 48 hours before cutover to minimize downtime.
Setting Up the Linode Instance
Spin up a Nanode 1GB instance ($5/month, 1 vCPU, 1GB RAM, 25GB storage) in the closest datacenter to your audience (options: Newark, Atlanta, Fremont, London, Frankfurt, Amsterdam, Singapore, Tokyo, Sydney, Mumbai, Toronto). No free SSL is included — factor in certificate setup time.
Transfer and Test
Upload your files via SFTP/SSH (no control panel mentioned; assume CLI). Import the database and update configuration files. Test thoroughly using the Linode’s temporary IP or a hosts file override. Our benchmarks show 3152ms TTFB and 11735ms fully loaded time on desktop — verify your site performs similarly pre-cutover.
DNS Cutover and Monitoring
Point your DNS to the Linode’s IP. With 100% uptime over 365 days, reliability is proven, but monitor for 72 hours. If issues arise, support requires a ticket or call — no live chat. Revert to backups if critical errors occur.