Dobble’s managed web hosting migration process is designed to reduce disruption, protect access and keep your business operating as normally as possible during the move. A hosting migration is not treated as a quick file transfer. It involves reviewing your current website, domain, DNS, hosting and, where relevant, email setup before any live changes are made.
The first step is usually an assessment of your existing environment. Dobble checks how your website is currently hosted, which DNS records are active, whether email is connected to the same domain, what third-party systems are involved and what access credentials are required. This matters because a poorly planned hosting change can affect more than the website itself. Incorrect DNS changes can interrupt forms, email notifications, SSL certificates, payment gateways, analytics, integrations or business email routing.
Where possible, Dobble prepares the new hosting environment before the final cutover. Backups are taken where practical, the new environment is configured, and the website is tested before DNS is changed. This preparation helps identify issues before they affect the live site. It also gives the team a clearer path for launch, rollback or troubleshooting if something unexpected appears during the migration.
For Dobble-built websites and applications, development and testing can occur in a secure staging environment before deployment. Where practical, clients may be given access to a password-protected staging website to review the site before it goes live. If access to the client’s domain is not yet available, Dobble can securely share staging access through a password-protected Cloudflare Tunnel. This means key stakeholders can review progress without exposing unfinished work publicly.
Your team’s access requirements are also considered. Depending on the project, this may include CMS access, domain access, DNS access, hosting access, email provider access, analytics access and third-party platform access. Dobble will advise what is required during onboarding or migration planning. Clients who request Genesis CMS access can be provided with a limited user account containing the permissions needed to manage website content, with access levels assigned at Dobble’s discretion to protect website integrity, security and functionality.
In most cases, a business does not need to stop operating while hosting is prepared. The goal is to keep the current website live while the new hosting environment is configured and tested. The final change usually occurs when DNS records are updated to point the domain to the new hosting environment. Dobble coordinates these DNS changes carefully to reduce propagation delays, but no provider can remove propagation entirely. Some users may see the old site while others see the new site for a short period, depending on internet caching, DNS provider behaviour and third-party systems.
Temporary interruptions can still occur, even with careful planning. Common causes include DNS propagation, registrar delays, external DNS providers, CDN services, email provider changes, cached records, payment gateway settings, third-party APIs or limited access to the existing host. Dobble is responsible for services and systems directly under its control, and may provide reasonable assistance diagnosing third-party issues where practical. Additional charges may apply where the issue falls outside the client’s SLA or agreed scope.
Dobble aims to maintain 99.9% monthly uptime for websites and hosting services managed on its infrastructure. This applies to the availability of Dobble-managed web server and hosting environments, measured monthly. It is not a promise of 100% uptime and excludes scheduled maintenance, emergency maintenance, third-party outages, client-side or ISP issues, force majeure events, client changes, misuse, third-party plugins or systems, and services not managed directly by Dobble. If uptime falls below 99.9% due solely to Dobble-managed hosting infrastructure, affected clients may request a service review and may be eligible for service credits where applicable under their SLA.
For hosting, maintenance, domain and email clients, Dobble provides support 24 hours a day, 7 days a week. Emergency support is available, with response times typically within 4 hours. For clients outside an SLA, emergency support is charged on an ad hoc basis, with quotes, predictions or capped timing supplied before work begins.
If you are planning to move hosting, the safest approach is to avoid rushed DNS changes and involve Dobble before cancelling your existing provider. A planned migration gives the team time to audit services, preserve access, prepare the new environment and reduce the risk of avoidable downtime.