Transfer your website to a new agency: move it safely, with no downtime

Transferring your website to a new agency is possible without downtime or ranking loss, provided you first secure ownership and access and treat the switch as a migration. The biggest risks are not in the technology, but in who holds the keys: the domain, the hosting, the CMS and your Google accounts. Whoever has those in order switches calmly. Whoever does not gets stuck with a supplier or, in the worst case, loses their site. In this guide we walk through the full transfer playbook, from taking stock of your access to the final cut.

This is BOFU material: you have probably already decided that it is time to switch. If you want to step back first and understand the entire build process, read the B2B website development guide.

What does transferring your website actually mean?

Transferring your website means moving four separate things that often sit with different parties: your domain name, your hosting, your website files and code, and the access to management and measurement environments. Many companies think “the website” is one thing, but in practice it is a set of accounts and contracts that each have to move separately.

So it is not a matter of forwarding one file. A new agency needs access to your CMS, your hosting environment, your domain management and ideally your analytics and Search Console. If one link is missing, the transfer stalls. That is why every good switch starts with an inventory: map out what exists, where it sits and in whose name.

Who owns your domain, code and website?

Ideally, you, the company, own everything. In practice that is far from always the case, and that is exactly where transfers go wrong. Some agencies register the domain in their own name, host your site on their account and keep the code up their sleeve. That makes you dependent.

So run through these three ownership questions:

• The domain: is the domain name registered in your company’s name as the holder, or in the agency’s name? This is the most important point. Whoever owns the domain effectively controls your online presence and your email.
• The code and files: do you have a right to the source code, or is your website locked inside a closed environment of the agency? For custom work this depends on your contract. On standard platforms the content is usually exportable, but custom templates or plugins are not always.
• The hosting: is the hosting account in your name with your payment details, or does the agency invoice the hosting on to you? A hosting account of your own makes you far more agile.

If you find surprises here, you immediately know where your negotiating room lies. An agency that works honestly will never hold your domain or data hostage. Even so, prevention is better: lock down ownership before you start a new partnership. It is also a matter of building trust, in both directions.

Which access do you need to secure before you switch?

Arrange all critical access before you cancel the contract with your current agency, never after. Once the collaboration formally ends, it becomes harder to get cooperation. So make a list first and make sure everything sits on an account that you manage.

The minimum checklist:

• Domain registrar: your own login with the party where your .be or other domain is registered, with your company as the holder.
• DNS management: access to the DNS records, because they steer your traffic and email. This often sits with the registrar, sometimes separately.
• Hosting: administrator access to the server or hosting platform where the site runs.
• CMS: an admin account in WordPress, Webflow or whatever platform you use, not just an editor role.
• Google Analytics and Search Console: administrator access on a company account. This is your historical data and your SEO monitoring; you never want to lose it in a switch.
• Email and any integrations: your business email is often tied to the same domain, and forms or CRM connections have to come along.

Where possible, put everything on email addresses of your own company domain, not on the personal address of one employee or of the agency. That way you do not lose access if someone leaves.

How do you transfer your .be domain safely?

A domain transfer runs via a transfer code that you request from your current registrar or directly from the registry. For .be domains, DNS Belgium sends that code to the email address of the registered holder. You pass the code to the new registrar, and with a valid code the transfer is carried out immediately.

Two points of attention. One: first check that the domain’s holder details are correct and in your company’s name, because the transfer code goes to that address. Two: never let your domain expire during a switch. A forgotten renewal date is one of the few ways to genuinely lose your domain and your email. So plan the transfer well before the expiry date.

Important: moving a domain changes nothing about your website itself. Your traffic follows the DNS records. Only adjust those at the moment your new environment is ready, so visitors always land on a working site.

How do you move the site without losing rankings?

Treat the actual move as a migration, not as a simple copy. If your domain and your URL structure stay identical and you only switch builder or hosting, the risk to your SEO is small. If a URL structure, platform or domain also changes along the way, the risks pile up and you need a redirect plan ready.

The core comes from the same playbook that applies to any move. Take a baseline measurement of your rankings, traffic and best-converting pages. Map out all your existing URLs. Test the new site in a shielded environment before you go live. And set up airtight 301 redirects if addresses change. The full steps are in our guide on website migration without losing rankings and, specifically for the design, in maintaining rankings after a website redesign.

If you are switching agencies because you want a new site at the same time, this runs together with a website redesign process. In that case, keep the two decisions clearly separate in your head: switching supplier and rebuilding your site are not the same thing, and you do not necessarily have to do them at once. If, during the transfer, you also move to a different CMS, follow the step-by-step plan for a CMS migration to switch platforms safely.

How do you prevent downtime during the switch?

Make sure the new environment works completely before you shut down anything on the old one. The golden order is: build or copy the site to the new hosting, test everything thoroughly, and only then adjust the DNS. That way a working site is always ready and visitors notice nothing.

Plan the definitive cut for a quiet moment, for example outside office hours or in your low season. After the switch, keep an eye on your error messages, your 404s and your email delivery. Compare your figures with the baseline measurement, so you can tell a normal, temporary dip from a real problem. And only cancel with your old supplier once everything is confirmed to be running, not before.

One last, honest note: not every switch has to be a big project. If you only move the hosting and the rest stays the same, this is sorted within a day. Only when domain, platform and design change at the same time does it become a real undertaking for which you are best off calling in professional guidance.

The short summary

Switching web agencies is not about technology but about control. Make sure your company owns the domain, the hosting, the code and the Google accounts, and arrange that access before you cancel. Treat the move itself as a migration with a baseline measurement and redirects, only make the cut once the new environment is confirmed to work, and never let your domain expire. Do that, and you switch calmly and without putting your hard-earned rankings or leads at risk.

We are a small, senior B2B team that works platform-agnostically and tells you honestly what a transfer requires in your situation. We walk through the switch step by step with you, so you lose nothing along the way.

Get in touch with us