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

← All guides

Migration

Website migration service: what a good move should include

Published August 2026 · 9 min read

The hard part of a website migration is not copying files. A good migration accounts for databases, DNS, email, SSL, redirects, scheduled jobs, runtime versions, hidden configuration, application writes, and the rollback path if the destination behaves differently under real traffic.

Inventory before quoting or copying

Count websites, domains, databases, mailboxes, storage, runtime versions, cron jobs, SSL, DNS records, redirects, control-panel features, external services, and traffic-sensitive application state. Unknown dependencies are the biggest source of migration surprises.

Build and test the destination before public cutover

The new environment should be able to serve the site through a private test path or hosts-file override. Verify dynamic features, administrator access, uploads, forms, database writes, certificates, and required outbound services.

Plan the final synchronization window

For sites that change while the copy is underway, decide how to capture new orders, uploads, comments, registrations, or content between the initial transfer and DNS change. A final database/file sync or short write freeze may be appropriate.

Keep the old environment long enough to prove the move

After DNS cutover, monitor logs, traffic, forms, email, and user reports. Retain the source and rollback details until resolver caches have transitioned and the new service has handled representative production use.

Next step

A website migration service should inventory the existing site, build the destination, copy files and databases, test privately, plan DNS, synchronize changes, verify mail, and retain rollback.

Plan a migration with DotMoose

Keep reading

Related guides.

Change email hosting without downtime: migrate mail without losing messages

Change email hosting without downtime by preparing destination mailboxes first, copying historical mail, preserving aliases and authentication, switching MX carefully, and synchronizing messages delivered during the transition.

Read the guide

How to move web hosting without downtime

Move a website and database with destination testing, final synchronization, controlled DNS cutover, and rollback while preserving separate mail routing.

Read the guide

Moving a DreamHost VPS to Canadian hosting

Inventory the server, copy it safely, test it, and cut DNS over with a rollback plan.

Read the guide

More migrations guides

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