Hosting and Server Migration

The scope we agree after our review can include a list of what must stay the same and what your site relies on, checking the new host can run your site and cope with demand, setting up server software and the database, files and storage, backups and restore tests, DNS and security certificates, caching and CDN, email and forms, scheduled tasks and connected tools, the final data sync, the switchover, speed checks before and after the move, close monitoring afterward and shutting down the old host.

We plan to keep downtime that visitors notice as short as possible, or avoid it, by using a test copy, a new setup that works with your site, controlled handling of new data, a final sync, careful DNS timing, monitoring and a rollback plan. We don't promise zero downtime in every case, because saved DNS answers, data being saved during the move, problems at the hosting company and outside systems can still cause some risk.

Yes, that is the standard limit for this service. We record your current web addresses, page responses, headers and content, then test them after the move. If your domain, web addresses, CMS (website editor) or what visitors see also changes, the project needs our bigger Website or CMS Migration service.

We compare server software and add-on versions, web server rules, database type and text sorting settings, file permissions and paths, how storage behaves, limits and hosting company features. Then we run typical public pages, admin tasks, uploads, forms, APIs and background tasks on the new server.

We find every place where new data comes in and, depending on how your site is built, use maintenance or read-only mode, live database copying, tracking of changes or copying changes in stages. The database and stored files get a final sync that is checked to match, plus a signed-off cut-off time. Moving live data with no downtime at all may need work on your app or database beyond a simple copy to a new host.

Yes, when recovery is in scope. We restore the agreed database, files, settings and passwords and keys into a controlled test area and run checks on the most important parts of your site. We record how long the restore took and anything that was missing. A backup job marked "successful" is not treated as proof that recovery works.

We check the main DNS zone and approved records, including the main domain, www, subdomains, IPv4 and IPv6, email, ownership checks, CAA, SRV, DKIM and DMARC where you use them. Automatic scanning tools can't be relied on to find everything, so the people who own your registrar, DNS, email and app must confirm the full list.

We identify which records will change, lower the relevant TTLs (how long DNS answers are saved) ahead of time where it makes sense, keep the old settings ready for rollback, change routing in a timed window and check from many DNS servers and from old and new server logs. We can't directly control saved DNS answers around the internet, so both servers stay monitored while the change spreads.

DNSSEC is a security layer that proves DNS answers are genuine. We check the DS record at your registrar, your DNS provider's keys and TTL settings. Depending on what the providers support, we either use a coordinated handover where both providers sign for a while, or remove the old DS record, wait for it to expire from saved answers, change nameservers and then turn on signing at the new provider. Changing nameservers while an old, mismatched DS record is still in place can make your domain stop working.

We list every domain name and both connections (from the browser to the CDN, and from the CDN to your server), install or issue the certificates needed, test certificate chains and strict checks, check redirects and mixed content (secure pages loading insecure files) and name who owns renewal. Certificates that only work between the CDN and your server may stop working if the CDN is later bypassed.

We map how pages, database results, browsers and the CDN cache content, plus cache rules, cookies, headers, what skips the cache, cache clearing, logged-in and personalized pages, images, proxy and server rules. We keep settings that have a good reason and test pages with and without the cache and after clearing it, rather than blindly copying every old rule.

We keep the DNS settings for your inbox email separate from website forms and automatic emails your site sends. Using approved accounts, we test sending a form, the queue or email service reply, delivery to the right place and what happens when an email bounces or fails. We can't guarantee emails land in the inbox rather than spam, and deeper email deliverability work is priced separately.

We list schedules and background tasks, decide the order to pause and move them, stop them from running on the old and new servers at the same time, move or finish waiting tasks where possible and test monitoring for both success and failure. Outside scheduling tools and automatic retries are included in our check of what your site relies on.

It can remove slowdowns caused by the hosting, but a move alone doesn't guarantee better Core Web Vitals (Google's measures of loading speed, responsiveness and visual stability). We compare speed with and without the cache, how the server and database behave, safe busy-time load, lab tests and any real visitor data available. Your site's code, content, visitors' devices and networks and outside tools still affect speed.

The step-by-step guide sets out health checks, limits for errors and service problems, who makes the decision and the settings to go back to. Where the tested setup allows it, we can send traffic back to the old server or restore the agreed earlier state. DNS changes and actions in outside systems may need extra time to spread or to be brought back in line.

Once DNS checks from many locations, old and new server logs, search engine access, key visitor journeys and outside connections meet the agreed limit. Required recovery records and logs must also be kept, and scheduled tasks, certificates, logins and hosting company services must each have approved steps for closing them down.

This page shows an example of one to four weeks of preparation, an approved switchover window and 7 to 30 days of monitoring. Timing depends on the size of your site and data, how often data changes, whether your software works on the new host, DNS and DNSSEC, certificates, caching, email, scheduled tasks, connected tools, recovery needs, hosting company limits and go-live windows. There is no single standard length.

Pricing follows the hosting and data work we find in our review: setting up the new host, database and files, DNS and certificates, caching and CDN, email, scheduled tasks, connected tools, monitoring, recovery, switchover support, any specialist needs and shutting down the old host. Your proposal states what you get, our assumptions, what is not included, timing and fee. New hosting and paying for old and new hosting at the same time, hosting plans, licenses, storage, data transfer, monitoring, email, specialist engineering and out-of-hours support are extra unless listed.