Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

Migrate from Linode

Move from Linode to DotMoose

Plan the server, storage and application services that need to move. Check DNS, address changes and backup access before cutover.

Hosting options

Compare the services for your project.

Your requirements

What does your project need?

01

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.

02

Test the destination

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.

03

Copy the final changes

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.

04

Switch traffic and retain rollback

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

Inventorying a Linode before the rebuild

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.

01

Profile and disk

Write down the active configuration profile, boot disk and attached volumes. Backups of the wrong disk waste the whole export window.

02

Secrets out early

Collect environment files, API tokens and database credentials into the move notes. Rebuilds stall when a secret exists only on the old server.

03

DNS Manager capture

Export any zones held in the Linode DNS Manager. The full record set, including mail and verification records, goes into the new zone.

Planning

Access, backups and handover

Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.

Free guide

Move from Linode to DotMoose: planning checklist

Use the detailed checklist to plan setup, access, migration and recovery with your team.

Download PDF →
Help choosing

Tell us about your project.

Send us the software you use, your storage needs and your launch or moving date.

Ask about hosting

We will handle the move. You check it first.

Your 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.

Start my free moveSee plans and prices
See pricesFree move