Sales promises "free migration, we handle everything." Go-live day: ticket rejected — "multisite not covered," "database over 2 GB out of plan," "custom cron on your side." You finish at midnight with rsync and an offline shop. Migration was free; scope was not.
"Free migration" is an acquisition lever with strict boundaries — designed for standard WordPress, not your Node.js SaaS with PostgreSQL and Redis queues. This inquiry maps what brochures actually include, what triggers surcharges, and what you must prepare regardless.
Usual scope: included vs out of plan
"Free migration" offers follow a recurring pattern. Understanding the boundary before signing avoids the Friday night surprise.
| Often included | Frequently out of plan |
|---|---|
| 1–10 WordPress sites | Custom apps, Docker containers |
| 1 MySQL database per site | PostgreSQL, MongoDB, DBs > 2 GB |
| FTP or cPanel → cPanel | VPS without matching panel |
| Help with A record | SPF, DKIM, DMARC for email |
| 3–5 business day timeline | Weekend or same-day urgency |
Request in writing maximum site count, allowed database size, email coverage, and guaranteed timeline. A confirmation email beats a landing page sentence.
Free means limited labor. Your responsibility remains data, application consistency, and DNS cutover.
Checklist before accepting free migration
Before signing, build a complete inventory. Without it, the host estimates — and underestimates — your complexity.
List all sites, databases, disk sizes, cron jobs, and TLS certificates. Document email accounts, volumes, and filtering rules. Lower DNS TTL forty-eight hours before cutover to speed rollback if needed. Keep a full backup on your side, not only at the future host — your safety net if migration fails mid-flight.
If staging is possible, test a restore there before go-live. One hour of testing avoids an all-nighter.
The summit: free covers the easy path, not your prod
Decide and move forward without blind spots
Send your full inventory before signing and request written confirmation of covered scope. Compare paid migration cost with the risk of a DIY overnight cutover — sometimes a few hundred euros avoids thousands in lost revenue. Prepare MX and email cutover separately if not included. To pick a host that can absorb your stack, browse our directory, comparator, and the inquiry on cloud exit.
Frequently asked questions
What does a free migration usually cover?
File transfer, one standard MySQL database like WordPress, basic DNS help, and a limited site quota. Large email, complex multisite, and custom apps are usually excluded. Get the exact list before scheduling the date.
Does migration include email?
Rarely end-to-end. Plan PST or mbox export, MX cutover, and DNS TTL reduction. Treat email as a parallel project, not a default included detail.
How much downtime should you expect?
One to twenty-four hours depending on TTL and sync. Clarify cutover window and rollback — free migration is not seamless failover.
Should you migrate yourself despite the free offer?
Yes if your stack is custom or databases exceed advertised limits. Test a full restore on the new server before shutting down the old one — the only proof migration will work on go-live day.
Free migration? Send your database size first — the answer matters more than the marketing badge on the pricing page.