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 legacy server

Move a legacy server to a new host

Document the software, services and data on your existing server. Test compatibility and recovery before moving a system you depend on.

Hosting options

Compare the services for your project.

Your requirements

What does your project need?

01

What needs to move

Check moving a legacy server where undocumented services, old runtimes, local mail, cron, hard-coded IPs, certificates, users, firewall rules, and hidden data paths make discovery more important than copying the filesystem quickly.

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

Discovering a legacy server before copying

Discovery matters more than copying on an old server. Nobody may know everything it runs, so start by listing listening ports, running services, user accounts, cron jobs for every user, and the data directories each service actually uses. Old machines often hold local mail spools, forgotten test sites and scripts that other systems still call.

Age breaks compatibility predictably. An old PHP or database version may have no equal at the destination, hard coded addresses hide in scripts, and certificates may be renewed by a forgotten cron job. Test each application against the destination runtime early, decide upgrade or isolate for anything that fails, and keep the old server running until callers confirm the switch.

01

Port and service scan

Record every listening port and the process behind it. Unknown services get identified before the copy, not after the old machine is gone.

02

Every user's cron

Dump cron tables for root and every user account, plus system timers. Legacy automation usually lives outside the main account.

03

Caller list check

Find other systems that call this server by address or hostname. Their owners get the new address before cutover, with time to update.

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 a legacy server to a new host: 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