Moving a site to new hosting scares many people: what if the site disappears, Google rankings fall and email stops working? In fact it is a well-established procedure. The risks are real only where it is done blindly. Below is a plan that gets everything through without downtime or losses, and a list of the traps people fall into most often.
In short: make a full copy of the site; move the files and database to the new server and check the result before switching the domain; lower the DNS TTL in advance; keep page addresses, SSL and redirects; after switching, check the server responses and Search Console. Migration with us — from 700 UAH and usually takes 1–2 days.
Why move a site at all
- The site is slow, and the cause is weak hosting (server response time over 600–800 ms).
- More expensive plans without real benefit, or the opposite — more capacity is needed.
- Frequent outages and downtime, and support does not respond.
- A change of owner, team or the country where the servers are located.
- A separate environment is needed for testing and backups.
What can go wrong
| Risk | How it shows up | How to avoid it |
|---|---|---|
| Site downtime | The page does not open for hours or days | Check the new server before switching the domain |
| Email loss | Emails do not arrive after a DNS change | Move the mail records (MX) separately and check sending |
| Broken SSL | The browser warns “not secure” | Issue the certificate on the new server in advance |
| Changed page addresses | Rankings drop, 404 errors appear | Keep the URL structure or set up 301 redirects |
| Site duplicates | Google sees two copies | Block the test copy from indexing |
| Data loss | Orders and comments disappear | Make a backup right before the move |

A step-by-step plan without downtime
- A full backup. Files, database, settings, mailboxes. Keep the copy separately from the old hosting.
- An inventory. Write down where the domain is registered, where the DNS records point, which services are connected (email, CRM, forms, analytics).
- Lower the TTL. A day before the move, set the DNS record TTL to 300 seconds so that changes spread quickly after the switch.
- A new environment. Create the site on the new hosting: the same PHP version, the same extensions, the same database settings.
- Copying and checking. Move the files and database, update the paths in the configuration. Review the site on the new server via a temporary address or the hosts file: all pages, forms, payments, email.
- SSL and redirects. Issue the certificate, check the redirect from http to https and from www to the main address.
- Freeze changes on the old site. Orders, comments, requests: so that nothing is lost after the final copy.
- Switching DNS. Change the domain records to the new server. Do not turn off the old hosting for a few more days.
- A check after switching. Open the key pages, send a test request, check the notification email, speed and server responses.
- Monitoring. For two to three weeks, watch errors and positions in Search Console.
How to make sure SEO has not suffered
- Page addresses remain the same. If something changed, 301 redirects from the old to the new URL are set up.
- Search Console: no spike in 404 errors or server unavailability.
- Sitemap and robots.txt are available and do not block the site from indexing (a typical mistake after moving a test copy).
- Speed is no worse than before, and ideally better.
- Structured data, meta tags and headings are in place.
Email and domain: what people forget
Often the email runs on the same hosting as the site. If you move only the site, and change DNS carelessly, emails may disappear. So determine in advance where the email lives, and keep the MX records, or move the mailboxes separately. The domain stays where it is registered; only the DNS records change.
How much it costs and how long it takes
Moving a site to new hosting or a new domain without losing search rankings costs from 700 UAH with us. For a typical site it takes 1–2 days including checks; large shops need more time because of the product and order database. If you also want to speed up the site or update PHP during the move, these tasks can be combined — we wrote separately about the reasons a site slows down. All WordPress services are collected on the service page, and you can leave a task description in the brief.
What to check within 15 minutes after the move
- Open the home page and five key pages on both a computer and a phone.
- Send a test request from each form and make sure the email arrives.
- Make sure the HTTPS padlock is shown and there are no security warnings.
- Send an email to and from your work mailbox to make sure email works.
- Open /sitemap.xml and /robots.txt: they should open and not block indexing.
- Check Search Console: are there any new errors?
A typical forgotten detail is email. The site was moved perfectly, and two days later it turns out that emails from clients were not arriving. That is why we test it in the first hour.
Frequently asked questions about the move
Will the site disappear during the move?
No, if you follow the plan: the old site keeps working while the new one is prepared and checked. Switching the domain takes a few minutes, and full DNS propagation takes up to several hours.
Will page addresses change?
They should not. We keep the URL structure, and where changes are unavoidable, we set up 301 redirects.
What to do with email?
Check where it runs, then move it separately or leave it unchanged. After switching, send test emails in both directions.
After how long can the old hosting be switched off?
Usually 5–7 days after the new one has been running stably, so you have a fallback and do not lose late emails or requests.
Shall we discuss your task?
Tell us what you need and we'll name the cost and timeline. We work directly.