What to Do When Your Agency Hosts Your Website: Getting Control of Hosting, Domain and DNS

If your agency hosts your website, you probably control fewer of the five assets than you assume: domain registration, DNS, hosting, CMS admin, and the analytics properties. Each is held separately, and an agency can hold all five. Check the registrant of record first. That one field decides whether leaving costs a phone call or a quarter.

By Avi Vatsa, CEO, Exchange Four Agency. Avi leads the team that installs and runs AI-leveraged revenue systems for owner-led companies. His background spans law, technology, and marketing; he also co-founded Dialora, an AI voice-agent platform for automated lead capture and booking. (Marketer of the Day #1411)

Which assets does your agency actually hold?

"My agency hosts my website" is usually shorthand for something much larger. Hosting is one line item. The thing that strands owners is the stack underneath it.

The pattern that hurts most isn't malice. An agency registers the domain during the original build because it's faster than waiting on the client, bills it back at cost, and the registrant field never gets corrected. Four years later the relationship ends, and the asset the entire business depends on sits in a vendor's account.

Why does an agency-held website get expensive when you leave?

Because you end up doing the migration yourself, on your own time, under deadline pressure, while leads keep arriving. That's not speculation about what could happen. It's the documented complaint pattern.

A G2 reviewer, writing about an agency relationship that ended badly, put it plainly: "the inability to help solve issues... made it so we ended up doing much of the transition ourselves." Another review in the same pattern cited "constantly changing project managers and the issues with communication." The transition is where the account manager you finally trained up stops returning email.

There's a second cost that never appears on an invoice. Vendor-management research puts coordination overhead at 8–15% of annual vendor spend in hidden internal labor, with businesses reporting roughly 30% higher total spend across multiple point-solution vendors versus one integrated partner. A stranded migration sits squarely inside that number — your hours, your weekend, no line item.

And the measurement side quietly breaks too. An industry survey distributed via Businesswire found 71% of brands frustrated demonstrating marketing ROI effectiveness. When the GA4 property belongs to the departing agency, that frustration becomes permanent: you lose the baseline you'd need to prove whether the next vendor is better or worse. The monthly numbers an owner should demand are worthless without the history behind them.

What should you check today, before anything is wrong?

Do this while the relationship is good. It's a five-minute conversation now and a legal matter later.

1. Run a WHOIS lookup. If privacy protection is on, you'll see the proxy, not the holder. Ask the registrar or the agency directly: who is the registrant of record?
2. Log into your registrar. Not the agency's panel. Yours. If you've never had a login, that's the finding.
3. Confirm the billing card on the domain is yours. Expired domains that were on a vendor's card do not renew quietly. They drop.
4. Check your CMS role. Administrator or editor? Editor means you cannot add users, export, or remove anyone.
5. Check GA4, Search Console, Tag Manager, and Google Business Profile for ownership. "Owner" is a specific permission level. Granted access is not ownership.
6. Find out where email is actually routed. MX records often live with the same DNS the agency controls. Moving a site badly takes email down with it.
7. Ask for the host name and the backup location in writing. Not a promise to provide backups — the name of the provider and the current location.

If any of those checks surfaces a surprise, you've found the same gap the rest of the agency red-flag list covers: a vendor holding something whose value is entirely yours.

What order should you move things in?

Order matters more than speed. Done backwards, you take your own site offline.

1. Create your own accounts first. A registrar account and a hosting account in the company name, billed to the company card. Nothing moves until there's somewhere to move it to.
2. Take ownership of analytics and Search Console. This is non-disruptive and preserves history. Do it before any tension exists.
3. Document current DNS. Screenshot or export every record — A, CNAME, MX, TXT, SPF/DKIM. This is the single most skipped step and the one that breaks email.
4. Migrate hosting. Copy the site to your new host, test it on a staging URL, and confirm forms, payments, and tracking all fire.
5. Change the DNS, not the domain. Lower TTL first, then repoint. Traffic moves with near-zero downtime when the destination is already live and tested.
6. Transfer the domain last. Request the authorization (EPP) code, unlock the domain, and initiate the transfer at your new registrar.

Does the 60-day lock apply to me?

Often, yes, and it catches people mid-exit. Under ICANN's Transfer Policy, a Change of Registrant triggers a 60-day lock on transfers to another registrar unless the prior registrant opted out, and registrars may deny a transfer within 60 days of an initial registration or a prior transfer.

The practical consequence: if you "fix" the registrant name during a dispute, you may lock yourself out of moving registrars for two months. Move the hosting and DNS first. Those have no lock. Then handle registration on its own clock.

What if the site is on the agency's proprietary platform?

Then you're not migrating a website. You're rebuilding one, and you should price it that way before you sign anything else.

Proprietary builders — agency-owned page systems, white-labelled CMS products, custom frameworks with no export — mean your content exists but your site does not travel. Ask one question before signing: on the day this ends, what file do I receive, and what does it open in? "We'll export your content" means a spreadsheet of text, not a working site.

This belongs in the paperwork, not in goodwill. Contract terms worth reading before you sign should name the IP assignment, the export format, and a transition window with a defined end date.

What does a clean arrangement look like going forward?

The agency manages the stack. You own it. Those are not in conflict, and any agency treating them as the same thing is telling you something.

Riggs Eckleberry, Chairman of OriginClear, described the standard this way of the team he works with: "They know exactly how to connect marketing execution to real business outcomes." An agency focused on your outcome has no reason to hold your domain hostage, because the leverage it wants is the revenue number, not the nameserver.

Set it up at the start. Our onboarding checklist for week one covers what to grant, what to keep, and the access that should never leave your building. If you're already mid-relationship and planning an exit, switching agencies without losing a quarter sequences the whole move.

The test is simple. If your agency disappeared tomorrow — no warning, no reply — could you still log in, still publish, still renew the domain? If the answer is no, that's not a hosting arrangement. That's a dependency, and it's billed to you either way. If a website rebuild is part of the work, how to protect your search traffic when an agency rebuilds your website covers the URL map and the redirects to ask for.