
Switching website agencies without taking your site down
By Leonel Rocha · Product Designer
· 6 min read
Before telling your current agency, list everything the site uses and whose name it's in: domain, hosting, code, database, email, Google Search Console, Analytics and plugin licenses. Ask for a full copy and the logins in writing, get the site running with the new provider, and only then switch the DNS. Finally, remove the old agency's access from every account.
Before telling your current agency, list everything the site uses and whose name it's in: domain, hosting, code, database, email, Google Search Console, Analytics and plugin licenses. Ask for a full copy and the logins in writing, get the site running with the new provider, and only then switch the DNS. Finally, remove the old agency's access from every account.
- 11.334
- new vulnerabilities in the WordPress ecosystem in 2025, 91% of them in plugins, according to Patchstack
- 46%
- of these flaws had no developer fix when they were disclosed, according to Patchstack
- 39,5%
- of all websites use WordPress, according to W3Techs in October 2026
The agency that runs your company's site takes a week to swap a banner. Or the maintenance contract went up and nobody can say what's included. Or you're rebuilding the site with another provider and need to get everything out. Either way, the question is the same: how to switch without your site, email and Google ranking dropping along the way.
You can do it without a single minute of downtime. What breaks a switch is almost never technical. It's the wrong order: telling the agency before knowing what to ask for, changing the DNS before the new site is ready, forgetting email, or leaving old logins open. This guide shows the sequence that avoids those mistakes.
Before giving notice, take inventory
The first step happens quietly, while the current contract is still in force. List everything that makes the site work and note, for each item, whose name it's in and who has the password:
- Domain: the site's address, registered with Registro.br if it's a .br.
- DNS: the zone that points the domain to the server and to email. It often sits with the agency's hosting, not at Registro.br.
- Hosting: the server the site runs on.
- Code and database: the site files, the admin panel and the content.
- Business email: if it's on the same hosting, moving the site affects email.
- Google Search Console, Google Analytics and Google Business Profile: who owns each one.
- Pixels and ad tags: Meta, Google Ads, Tag Manager.
- Licenses: theme, paid plugins, fonts, stock images.
If you find you've lost access to any of these, especially the domain, sort that out before any conversation. The step-by-step is in our guide to recovering your site's domain and hosting.
The licenses nobody remembers to ask for
WordPress runs 39.5% of all websites and 58.3% of sites with an identifiable content management system, according to W3Techs in October 2026. If an agency built your company's site, there's a good chance it's on WordPress, with a paid theme and plugins.
This is where many switches stumble. Agencies often use their own premium theme or plugin license across all clients. When you leave, that license stays with them. The site keeps working, but stops getting updates.
This is no small detail. Patchstack's State of WordPress Security in 2026 report counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025, 42% more than the year before. 91% were in plugins and 9% in themes. WordPress core had only 6, all low priority. The same report says 46% of flaws had no developer fix when disclosed and that the weighted median time to first exploitation was 5 hours.
In other words: a plugin without an active license is a plugin that will fall behind. During the inventory, ask item by item: “whose name is this license in?” Anything in the agency's name, you rebuy in yours or replace with another component.
What to request from the agency, in writing
With the inventory ready, send a formal request. By email, dated, referencing the contract. Ask for:
- A full, recent copy of the site files and database.
- An export of every DNS zone record, including email.
- Admin access to the site panel, hosting and domain registration, if they're in your name.
- Transfer of ownership of everything in the agency's name that should be in yours.
- Your email added as owner in Google Search Console, Analytics and Tag Manager.
- A list of paid plugins, themes and services, with the license holder for each.
- Integration passwords: forms, payment gateway, CRM, email marketing.
Respect the contract's notice period. A polite, complete, written request is usually honored. A rushed request after an argument usually stalls.
The right order for the move

The rule that keeps the site from going down is simple: the site must be working in the new place before the address points there.
- Put a copy on the new server. The new provider installs the site and database and checks it page by page on a test address.
- Recreate the DNS zone. Every record, one by one: the site's, the email ones, and the verification records for Google and other tools.
- Lower the TTL a few days ahead. TTL is how long the internet caches the old address. A low value makes the switch faster.
- Switch the DNS on a slow day. According to Hostinger, propagation usually takes up to 24 hours and, in rare cases, up to 72. During that time, some people see the old site and some see the new one. Since both work, nobody sees an error.
- Keep the old server running for a few days. Only cancel the old hosting after confirming that traffic, forms and email are reaching the new place.
If, besides switching providers, you're changing page URLs or rebuilding the site, there's one more step: redirects. Without them, you lose the ranking you've earned on Google. We cover this in the guide on migrating your site without losing Google rankings.
Close the doors left open
The switch is only done when the old agency no longer has access to anything. This is the most forgotten step, and not out of bad faith: nobody remembers every account.
Review and remove the agency from the site panel, the old hosting, Registro.br, Analytics, Tag Manager, ad accounts and integrations. Then change every password, including the ones you think only you had.
Google Search Console has a detail that catches many people. Google's official help explains that removing an owner cuts access immediately, but their verification token stays on the property. If you don't delete that token, the removed person can verify the property again. So after removing the user, check the list of unused tokens and delete the ones that belonged to the agency.
What this means for you
Switching agencies is a business decision, not a technical emergency. Treated that way, it fits on a list:
- Inventory before giving notice.
- A written request listing everything to hand over.
- Licenses rebought in your name.
- Site running in the new place before the DNS switch.
- Old access removed and passwords changed at the end.
The most important point applies to your next contract too: domain, hosting, code and Google accounts always in your company's name and tax ID, from day one. Whoever runs the site can change. The owner doesn't.
How we do it at the Studio
When a site comes to us from another provider, the price is fixed after discovery, and the deadline is written into the contract.
In our projects, the code, files and logins are in the client's name. That goes for the sites we build in our own code, like the Studio's own site, amandanutri.com.br and conversaovisual.com.br. If you ever want to switch providers, you don't depend on our goodwill.
If your site is stuck with an agency that doesn't answer, or you just want to switch safely, our project rescue page shows how we take over sites and systems built by others, without starting from zero when there is no need.
Common questions
Do I need to tell the agency before hiring another?
No. Ideally, you hire the new provider, take inventory and request access while the old contract is still active. Give notice within the contract's notice period, in writing, along with the list of what needs to be handed over.
Does the site go down during the switch?
It doesn't have to. If the site is already running on the new server before the DNS switch, visitors see either the old site or the new one, never an error page. DNS propagation usually takes up to 24 hours and, in rare cases, up to 72.
The agency says the theme and plugins are licensed to them. Now what?
This is common with WordPress sites: the agency uses its own premium theme or plugin license across many clients. When you leave, you need to buy a license in your name or replace the component. Without an active license, the plugin stops getting security updates.
Can company email stop working during the switch?
It can, if the email records aren't copied to the new DNS. Before switching, list every record in the current zone, including email, and recreate each one at the new provider.
Sources
Related service
Systems and apps
Systems, SaaS and iOS and Android apps from diagnosis to launch, with design, code and AI on the same team
News Responsivo
Get the next article in your inbox
Cost, timelines, AI and behind the scenes of shipping products. No spam.


