FAQ

Can we keep using our current website and email while Dobble builds a new site?

In most cases, yes. Dobble usually builds and tests new websites in a secure staging environment while your existing website, domain and email keep operating. Access to your domain, hosting, DNS, email and current website may be needed, and launch is planned carefully to minimise disruption, although DNS propagation and third-party issues can still cause temporary interruptions.

Yes. In most website development projects, Dobble’s aim is to let your existing website, domain and business email continue operating while the new website is planned, designed, built and tested. The usual approach is not to work directly on the live website. Dobble develops and tests websites in a secure staging environment before deployment, so your current online presence can remain available while the new site is prepared.

This staging environment gives Dobble a controlled place to build the new website, test functionality, optimise performance and review the structure before anything is made public. Where possible, clients can review a password-protected staging website, often on a staging subdomain such as staging.yourdomain.com.au. If access to the client’s domain is not yet available, Dobble can securely share staging access through a password-protected Cloudflare Tunnel.

For most businesses, this means you can keep trading, receiving enquiries and using your existing website while the new site takes shape. It also gives your team time to review page layouts, content, calls-to-action, forms, mobile layouts and other project details before launch. Dobble’s process is designed around client review, refinements and approval before deployment where practical.

Access is an important part of reducing disruption. During onboarding, Dobble may need access to your current website, hosting provider, domain registrar, DNS records, analytics tools, email-related DNS settings and any third-party platforms connected to the website. The exact access required depends on the project. For example, a standard website rebuild may need domain and hosting access, while a more complex website may also require API credentials, CRM access, booking system access, payment gateway settings or other business tools.

Dobble handles access and migration planning carefully because website, email and domain services are often connected through DNS. A small change to DNS can affect the website, email delivery, SSL certificates, website forms or third-party services if it is not planned correctly. This is why Dobble audits existing services before migration where applicable, prepares the new environment, takes backups where possible and coordinates DNS changes to reduce disruption.

When the new website is ready and approved, Dobble performs final testing before launch. The launch process may involve moving files, changing DNS records, updating hosting settings, configuring SSL, checking redirects, testing forms, submitting sitemaps and confirming analytics or tracking setup where included in the project scope. The goal is to make the changeover as smooth as possible.

That said, no responsible developer should promise that every migration or launch will be completely interruption-free. Temporary issues can occur due to DNS propagation, third-party hosting providers, domain registrars, DNS providers, internet caching, email providers or services outside Dobble’s direct control. Dobble plans migrations to minimise downtime, but some external factors cannot be fully controlled.

If your email is hosted separately, such as through Microsoft 365 or another third-party provider, Dobble will consider the email setup when planning domain and DNS changes. Correct handling of MX, SPF, DKIM and DMARC records is important for keeping business email working and supporting deliverability. Dobble cannot guarantee uninterrupted email availability or inbox placement because email services depend on third-party providers and receiving mail systems, but it can configure and manage the technical foundations properly.

If your current website is hacked, unstable, extremely slow or already offline, the approach may be different. Dobble may recommend a technical audit, repair work, malware removal, hosting review or temporary stabilisation before or alongside the rebuild. This helps reduce business risk while the long-term website development project is underway.

The best way to reduce disruption is to involve Dobble early, provide accurate access details, avoid making uncoordinated DNS or hosting changes during the project, and review staging work promptly. If you are planning a rebuild and want to keep your current website, domain and email running during development, Dobble can assess the setup and recommend a practical launch plan. Discuss Your Website Development Project to get started.

Ready to start?

Let's build something that works for your business.

Get a tailored quote or send us your question — the team is here to help.

Get started Ask a question

Keep exploring

Tap to call
Enquire now

Ask Dobble

Ask a question

Send us your question and the Dobble team will get back to you.

Prefer to talk to us directly?

Get in touch

Contact us

Tell us about your project and the Dobble team will be in touch shortly.

Prefer to talk to us directly?