Move your site
without the downtime
The same four steps we have used for hundreds of migrations, written out so you can see exactly what happens and when.
The four steps
Nothing changes for your visitors until you say so.
1. Copy everything
We take a full copy of files, databases and mailboxes onto our servers. Your current site keeps running and serving customers throughout.
2. Verify on a preview URL
You open the site on a preview address and check the pages, forms, checkout and email that matter to your business.
3. Switch DNS
Once you approve, the DNS record points at the new server. We lower the time-to-live in advance so the change takes effect quickly.
4. Final sync
Anything added during verification — orders, posts, uploads — is synced again so nothing is lost in the handover.
What to prepare before you start
Having these three things ready is the difference between a one-day move and a one-week one.
A short checklist
Most delays in a migration come from access, not technology. If you can gather the following before we begin, the copy step usually completes the same day.
- Access to the current hosting control panel, or a recent full backup
- Access to the DNS records for the domain — at the registrar or wherever they are managed
- A list of anything that runs outside the website: cron jobs, payment webhooks, API integrations
- One person who can confirm the preview site looks right and approve the switch
Risks we plan around
The three things that most often go wrong elsewhere, and how we prevent them.
Where migrations usually fail
Losing orders placed during the switch is the most common failure, and it is entirely avoidable — that is the reason for the final sync after DNS changes rather than before.
The second is email. Moving website files while leaving mail records pointed at the old provider silently breaks delivery, so mail records are handled deliberately rather than assumed.
The third is the forgotten integration: a payment webhook or a scheduled job pointing at the old server address. We inventory those before the switch instead of discovering them from a customer complaint.
Migration questions
What customers ask before committing to a move.
How long does a migration take?
A typical WordPress or Laravel site is copied and verified within a day. The DNS switch itself is a few minutes of work, and a final sync afterwards catches anything added during verification.
Will my site go down during the move?
No. The old site keeps serving until you approve the switch. Because we sync again after DNS changes, visitors do not see an interruption and no orders are lost.
Do you move email as well?
Yes. Mailboxes and their contents are copied, and we help you update mail client settings so nothing is left behind on the old provider.
What do you need from me to start?
Access to the current hosting account or a recent backup, access to the DNS records for the domain, and a contact who can confirm the site looks right before we switch.
Ready to move?
Send your current hosting details and we will come back with a migration plan and a date, at no cost.