Migration
Moving a DreamHost VPS to Canadian hosting
A VPS migration is safest when it is treated as a controlled cutover instead of a one-time file copy. The goal is to know exactly what runs on the old server, reproduce it, test it privately, and keep a rollback path until the new server is proven.
Inventory the old VPS first
Record the operating system, CPU and memory use, disk consumption, websites, databases, users, mail services, cron jobs, certificates, firewall rules, background services, application versions, and DNS records. Check for anything stored outside the obvious web directories.
Size the replacement from real usage
Do not copy a plan name blindly. Measure memory use, CPU load, disk use, database size, traffic, and growth. A replacement can have different hardware as long as it has enough resources for the workload and an appropriate amount of headroom.
Build the new server before moving DNS
Install the operating system and required services, create users, configure the firewall, restore application data, and test using a local hosts-file override or a temporary hostname. The public domain should continue pointing to the old VPS during this stage.
Use an initial copy and a final sync
Large data sets are easier to move in two passes. Copy the bulk of the files first, then perform a shorter final synchronization immediately before cutover. Databases should be dumped or replicated using a method appropriate to the database rather than copied while live files are changing.
Lower DNS TTL before cutover
Lowering the relevant DNS TTLs ahead of the move can reduce how long old answers remain cached. Change only the records needed for the migration, and keep a record of the original values.
Verify before deleting anything
After DNS changes, test the website, logins, forms, background jobs, outbound mail, certificates, database writes, and external integrations. Keep the old VPS available until you are satisfied that traffic has moved and no data is still being written there.