How to Fire Your Web Developer (Without Losing Your Site)

VenbitThe Venbit TeamJuly 24, 20265 min read

The short answer

The safe way to fire your web developer is to secure your own copies of four things first, before you say a word: your domain login, your hosting login, the site files, and the database. Once those are in your hands, you can end the relationship cleanly and hand everything to a new team without risking your website.

Key takeaways

  • Secure four things before you fire anyone: domain login, hosting login, site files, and the database.
  • Never announce the split before you've confirmed you can access your own accounts.
  • A free built-with scan confirms your host and registrar so you know exactly what to secure.
  • Keep the tone professional and put the handoff request in writing.
  • A clean backup in your possession means the break can't cost you the site.

Firing a web developer is straightforward once you do the steps in the right order. The order is everything. Before you tell anyone you're leaving, you get your own copies of four things: the domain login, the hosting login, the site files, and the database. With those secured, the developer no longer holds anything over you, and the actual conversation becomes easy. Do it in reverse, and you can hand someone a reason to make your life hard on the way out.

To be clear, most developers are decent people who'll hand things over cleanly. But you don't want your website's safety to depend on someone else's goodwill during an awkward split. So we prepare first, then part ways. Here's how.

The four things to secure first

  • Domain login. Access to the registrar where your domain is registered. This is the most important one. Without your domain, you don't have a website.
  • Hosting login. Access to the account where your site's files are stored and served.
  • Site files. A downloaded copy of everything that makes up your website.
  • The database. For WordPress and similar platforms, your content lives in a database separate from the files. You need both.

Step by step: making a clean break

  1. 1Confirm where everything lives. Run a free Built With scan on your address to see your hosting company, registrar, nameservers, and DNS provider. Now you know exactly which accounts you need access to, by name.
  2. 2Get into the domain account. Log into your registrar. If you don't have the password, use the reset link on any account tied to an email you control, or call the registrar to prove you're the business owner. Confirm the domain is under your name, or start the transfer to move it there.
  3. 3Get into the hosting account. Same process. Log in, or recover access, and confirm you can reach the site's files and control panel.
  4. 4Download a full backup. Pull down the site files and the database together. On WordPress, a backup plugin or your host's backup tool exports both in one go. Store this copy somewhere safe. This is the single most important protective step: with a backup in hand, nothing the developer does can erase your site.
  5. 5Save your logins and any custom assets. Note your registrar, host, and CMS logins in a password manager. Grab any brand files, license keys, or custom code the developer created for you while you still have access.
  6. 6Now have the conversation. With everything secured, tell the developer you're moving on. Keep it professional and brief. Thank them, and ask in writing for anything you couldn't grab yourself, plus confirmation they've removed their own access.
  7. 7Change the passwords and revoke old access. Once the handoff is done, reset every password, set the recovery email to yours, and remove the developer as a user or collaborator on each account.

How to keep the conversation professional

You don't owe anyone a dramatic exit, and a calm one serves you better. A short, factual message does the job:

Thanks for your work on the site. We've decided to move our web work in-house / to another team. Could you please confirm we have full access to the domain, hosting, files, and database, and remove your own access once we've confirmed everything transferred? We appreciate your help wrapping this up cleanly.

Keep it in writing, keep it polite, and give a reasonable deadline. If money is owed either direction, settle it. A clean paper trail protects you if anything gets complicated later.

What a good new agency will ask you for

When you bring on someone new, they'll want the same four things you just secured: domain access, hosting access, the files, and the database. If you've done the steps above, you can hand all four over on day one, which makes the transition painless. A good agency will also check that the site is genuinely in your name, not theirs, so you're never in this spot again.

If your developer has already gone silent rather than being someone you're actively parting with, the what to do when your web developer disappears guide covers recovering access when there's no one on the other end.

How the handoff works when you come to us

We take on sites from other developers regularly, and we make the switch calm on purpose. We confirm your domain and hosting are truly yours, take a fresh backup, and get everything documented so it never lives in one person's head again. Our maintenance plans start at $99 a month and include keeping that access in order, so a future switch, if you ever want one, is simple.

We've been a Seattle-area studio since 2011, working with businesses across the Puget Sound and remotely nationwide. If you're weighing a switch and want a second opinion on your current setup first, call us at (425) 314-1415. No hard sell.

More website answers

Every question in this series, from Website Problems, Solved.

Symptoms & emergencies19
What happens if...9
Cost & pricing7
Plans & hiring10
Ownership & switching9
Platform-specific7
Seattle & local2
Venbit

The Venbit Team

Web design & SEO, Seattle

Venbit is a Seattle-area web design, SEO, and digital marketing studio. Since 2011 we've designed, built, and ranked small-business websites for clients across the Puget Sound and around the country, so the numbers and advice here come from real projects, not a content mill.

Common questions

Questions, answered straight.

Straight answers about website fixes for your business. If yours isn't here, ask us directly and we'll give it to you straight.

Ask the team

Secure four things first: your domain login, your hosting login, a copy of the site files, and the database. Confirm you can actually log into your own accounts before you say anything about leaving. Once those are in your hands, the developer holds nothing over you and the break can proceed cleanly and safely.

Only if they still hold the accounts and you don't have a backup. That's exactly why you secure the domain, hosting, files, and database before you announce the split. With a full backup in your possession and access to your own accounts, nothing they do can erase your website. Preparation removes the risk entirely.

You should, but it depends on how the accounts were set up. If your domain and hosting are registered under your name, you own the infrastructure. If they're under the developer's account, you need to transfer them into your name. A built-with scan plus a WHOIS lookup shows you who currently holds each piece.

No. A brief, professional note is enough: you're moving your web work elsewhere, and you'd like confirmation of full access and removal of theirs. You don't owe a detailed explanation. Keeping it short and courteous, in writing, is the cleanest approach and protects you if any disputes come up later.

Hand the new agency the four essentials: domain access, hosting access, the site files, and the database. If you secured those before leaving your old developer, the new team can take over immediately. A good agency will also verify the site is registered in your name and document everything so you're never locked in again.

Yes, once the handoff is complete. Reset the passwords on your domain, hosting, and CMS accounts, set the recovery email to one you control, and remove the old developer as a user or collaborator. Do this after you've confirmed everything transferred and you have a backup, not before, so you don't lock yourself out mid-move.

Free 30-minute strategy call

Let's talk about your project.

Tell us what you need and we'll give you an honest read on the project, the timeline, and what it takes, before you spend a dollar. Based in Seattle, working across the Puget Sound.

4.8 on Google 5.0 on Yelp