How to Fire Your Website Agency Without Losing Your Site

Most people don’t realize they don’t actually own their website until they try to leave. Then the agency goes quiet, or starts talking about “transition fees,” and suddenly you’re negotiating for something that was supposed to be yours all along.

How to Fire Your Website Agency the Right Way

The process of leaving an agency isn’t complicated once you know what to ask for. The problem is that most business owners don’t know the full list, so they walk away missing pieces and end up stuck. An agency can hold your site hostage without technically doing anything wrong — they just don’t hand things over unless you ask for them specifically.

Before you send any email, take stock of what you currently have access to. Can you log into your domain registrar (GoDaddy, Namecheap, Google Domains, wherever your domain lives)? Can you log into your hosting account independently? Do you have credentials for your CMS (WordPress, Squarespace, Webflow, whatever they built on)? Write down what you can access and what you can’t. That gap is exactly what you need to close.

What You Actually Need to Ask For

Domain ownership. Your domain name is arguably the most valuable digital asset your business has. If the agency registered it on your behalf, it might be sitting in their account, not yours. You need a full transfer to a registrar account you control. This isn’t a file they send you — it’s an account transfer that requires an authorization code (sometimes called an EPP code or transfer key). Ask for it explicitly.

Hosting credentials or a full site export. If they host your site on their own servers, you need either login credentials to that hosting account or a complete export of your site files. For WordPress sites, that means a zip of the wp-content folder plus a database export (.sql file). For custom-built sites, you want the entire codebase and any environment configuration files. If they built on a website builder platform they manage, ask whether you can be transferred to your own account on that platform or whether you need a rebuild.

CMS admin access. You should have your own administrator account on whatever platform runs your site — one that isn’t owned by them. If they built in WordPress, you need a user account with full admin rights and they should either remove their own admin access or at minimum hand over those credentials too.

Database backups. The database is where your content lives: blog posts, product listings, customer records, form submissions, everything. Ask for a full database backup file. A competent agency will have these. If they say they don’t, that’s its own problem worth knowing about.

Third-party service logins. Think about every tool connected to your site. Google Analytics, Google Search Console, any email marketing integrations, payment processors, ad pixels. Make sure you have owner-level access to all of these under your own accounts, not just access granted through their account.

The Email to Send

Keep it professional and specific. Here’s a template you can adapt:

---

Subject: Website Asset Transfer Request

Hi [Name],

I’ve decided to move in a different direction for our website going forward. I’d like to arrange a smooth handover of all website assets. Please provide the following:

1. Domain transfer authorization code (EPP code) for [yourdomain.com], or confirmation that the domain is already registered under my account
2. Full website file export, including all themes, plugins, and custom code
3. Database backup (.sql or equivalent)
4. WordPress/CMS admin login credentials, or confirmation that my existing login has full admin access
5. Login credentials for our hosting account, or migration assistance to a new host of my choosing
6. Confirmation that I have owner-level access to our Google Analytics and Google Search Console properties

Please send these by [date 7-10 business days out]. Let me know if you have any questions.

Thank you, [Your name]

---

That’s it. No lengthy explanation, no apology. Be specific, set a deadline, and put it in writing so there’s a record.

What to Do If They Stall or Don’t Respond

Some agencies will drag their feet, especially if they feel blindsided. Give them the timeline you specified in your email. If that passes without a response, send one follow-up referencing the original email and your deadline. If they’re still unresponsive, check your contract — most service agreements have clauses about deliverables and ownership. If the domain is in their account, you can escalate to the registrar directly with proof that you’re the business owner (invoices, business registration documents). Registrars like GoDaddy and Namecheap have dispute processes for exactly this scenario.

If they’re holding content or code hostage and your contract says you own it, that’s a legal matter. Most agencies won’t push it that far — the reputational damage isn’t worth it — but knowing your contract language gives you leverage to move the conversation forward.

A Real Example: What “Owning Your Site” Actually Looks Like

When we worked with Indiana Photo Booth, a photo booth rental company out of Indianapolis, one of the first things we did was make sure they owned everything from day one. The domain was registered under their name at a registrar they controlled. All the code we wrote was handed over completely. Their Google Analytics property sat in their own Google account, not ours. When we launched, there was nothing tying them to us except a relationship they chose to maintain.

That’s how it should work. A good web vendor doesn’t create dependency — they hand over a working, fully-owned site and let you decide what comes next. The fact that so many agencies do the opposite isn’t an accident. Dependency is a business model.

At Web Lift Up, clients own all their code, all their content, and their domain from the start. No retainer required afterward. No monthly platform fee to keep the lights on. That’s the deal.

Before You Rebuild, Check What You Have

Once you’ve recovered your assets, take a breath before you jump to rebuilding. Audit what you actually have. If your old site has decent SEO equity — real traffic, indexed pages, backlinks pointing to it — you want to preserve that during any redesign. Switching platforms carelessly can wipe out years of search ranking progress.

If you’re moving to a new builder or a new host, make sure you set up 301 redirects from any old URLs that changed. Keep your page titles and meta descriptions for high-performing pages as close to the originals as possible until you’ve confirmed traffic has stabilized. This isn’t complicated, but it matters.

Also check your hosting setup before you cancel anything. Don’t delete the old hosting account until you’ve confirmed DNS is pointing correctly to the new one and everything is live. Overlapping by two weeks costs almost nothing and saves you from a painful gap in visibility.

If You’re Starting Over Anyway

Sometimes recovering your old site isn’t the goal. You’re done with it, the agency, and the platform they built on — and you just want a clean start. If that’s where you are, you still need the domain transferred. That piece never changes. Everything else can be rebuilt.

If a full rebuild is what you’re after, Web Lift Up builds a free working demo before you pay a cent. Flat rate of $499, delivered in 7 days, and you walk away owning the code and the domain outright. No retainer, no ongoing fees, no platform that holds your site hostage. If you’ve just gone through the process of prying your site back from an agency, that probably sounds like exactly the opposite of what you just experienced. Reach out at [email protected] if you want to talk through what a rebuild would look like for your business.