What needs to move
Check moving from Linode by inventorying compute instances, attached storage, firewall/network configuration, DNS, images, backups, object dependencies, and application secrets before rebuilding in the target environment.
Migrate from Linode
Plan the server, storage and application services that need to move. Check DNS, address changes and backup access before cutover.
Hosting options
Help moving websites, databases and email. We agree on the scope and cutover details before the move.
See Migration help →02Tell us what you need to host and when it needs to be ready.
See Ask about your project →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →Your requirements
Check moving from Linode by inventorying compute instances, attached storage, firewall/network configuration, DNS, images, backups, object dependencies, and application secrets before rebuilding in the target environment.
Copy the site or application to the new host and test it privately. Check logins, forms, database writes, scheduled jobs, email and any external integrations.
Choose when to stop or synchronize new writes. Include orders, uploads and mail that arrived after the first copy. Avoid letting both systems accept independent changes.
Save the old DNS and routing settings. Switch traffic after the final tests, monitor the result and keep the old service until the agreed rollback period has passed.
Field guide
A Linode account spreads a workload across compute instances, attached volumes, NodeBalancers, firewall rules, DNS zones and sometimes object storage or managed databases. List each service and what it holds before exporting. Application data moves as database dumps and file copies taken from the running system, while images and backups stay useful mainly as rollback copies.
Configuration profiles and private addresses are the traps. A Linode can boot different disks and kernels from saved profiles, and services often talk over the private network or a shared configuration. Record which profile and disk the live system uses, map private connections between services, and rebuild those links deliberately at the destination before traffic follows.
Write down the active configuration profile, boot disk and attached volumes. Backups of the wrong disk waste the whole export window.
Collect environment files, API tokens and database credentials into the move notes. Rebuilds stall when a secret exists only on the old server.
Export any zones held in the Linode DNS Manager. The full record set, including mail and verification records, goes into the new zone.
Planning
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.