Quick answer: The short version of everything in the Migration Center: migration to Cloud2Y is free and assisted via support ticket, your site stays online during the move if you follow the parallel-run pattern, DNS is switched only after testing, and the old server stays alive for a few days as your rollback plan.
Overview
These are the questions we hear most in migration tickets, answered briefly with links to the full guides. If your question is not here, the migration checklist and common issues articles cover the rest — or just ask us.
Before you start
- For any real move, skim how the process works first — five minutes that prevents most surprises.
Step-by-step guide
- Is migration really free? Yes — assisted migration comes with your new Cloud2Y service; scope for unusual setups is confirmed in the ticket (how to request).
- Will my site go down? Not if you run old and new in parallel and switch DNS after testing — the zero-downtime pattern.
- How long does it take? A typical single site: copy and test the same day; DNS propagation adds hours. Large or many-site moves are planned in waves.
- Do I need to cancel my old hosting first? No — the opposite. Keep it until the new server has run cleanly for several days.
- What about my email? Mailboxes move with imapsync or to a mail provider — decide early (guide).
- What if something breaks after the switch? Point DNS back at the old server after reconciling new data — the rollback guide.
Common issues
- Asking for a migration without source access ready: credentials are the #1 delay — have SSH/panel logins at hand.
- Planning around the wrong bottleneck: data copies are fast; DNS caching and human coordination are what need lead time.
When to contact support
Open a ticket for anything specific to your setup — sizing the target server, planning a freeze window, or checking whether an exotic stack transfers cleanly. Pre-sales questions are welcome before you order.
Frequently asked questions
Does Cloud2Y migrate websites for free?
Yes, assisted migration is included with your new Cloud2Y service: engineers copy files and databases, verify the result, and you approve the DNS switch. Scope is confirmed per ticket.
Will visitors notice the migration?
With the parallel-run pattern, no: the old site serves traffic until the tested new server takes over via a DNS change, and even that propagates within minutes on a lowered TTL.
Should I cancel my old hosting before migrating?
Never before. Keep the old service through the move and several days past the switch — it is both your data source and your instant rollback if anything misbehaves.
What if my setup is unusual — custom services, huge data?
Describe it in a ticket before ordering. Pre-sales engineers will size the target server and tell you exactly how the transfer would run for your specific stack.
Related articles
- How the Cloud2Y migration process works
- How to request a free migration
- Migration checklist
- Common migration issues
Need a hand with your move? Contact Cloud2Y support →
