What to Do Before You Fire Your Web Developer

Before you fire your web developer, get control of the things that become hard or impossible to retrieve once the relationship is over. That means confirming the domain, hosting, and every account are in your name, and getting a full backup of the site, all while things are still civil. The order matters: secure access first, part ways second. Owners who do it the other way round can find themselves locked out of their own website by someone they have just annoyed. Here is the checklist to work through first.

Why order matters

A developer you have just fired has little reason to help you, and if they hold your domain or accounts, that becomes a real problem. Everything on this list is a routine, reasonable request while you are still working together, and a fight once you are not. So you do this quietly and completely before you have the difficult conversation.

This is not about being sneaky. It is about making sure that ending the relationship does not mean losing your website.

The checklist, in order

Work through these before you say anything about leaving:

1. Confirm you control the domain. Check it is registered to you and that you have the registrar login. This is the one that hurts most to lose. Who owns your website covers how to check.
2. Confirm you control the hosting. An account in your name, with your login, or a clear way to move.
3. Get an administrator account on the site that is yours, not a shared one that can be removed.
4. Take a full backup. Files and database, downloaded and kept somewhere safe, so you have a copy no matter what.
5. List every third-party account the site depends on, payment gateways, email services, plugins with their own logins, and confirm you can access each.
6. Reset shared passwords once you have your own access, so the departing developer no longer holds keys.

If you cannot complete some of these because the developer holds them, that is important to know before you act, and getting access when they will not cooperate covers the harder cases.

Then part ways cleanly

With access secured, you can end the relationship professionally. Keep it civil regardless of why you are leaving, both because it is decent and because you may still need one last cooperative handover. Ask for anything outstanding, design files, documentation, and confirm what you now hold matches the full picture.

Line up what comes next

Do not fire your developer with no plan for who maintains the site. A site with nobody responsible drifts into neglect quickly. Whether you are moving to a new developer, taking it in-house, or handing it to a maintenance provider, have that arranged so there is no gap. Taking over a website from another developer covers the handover from the receiving side.

What to do next

Before you have any conversation about leaving, work down the six-point checklist and confirm you hold everything: domain, hosting, admin, backup, third-party accounts, and reset passwords. Once you control your own site, ending the relationship is straightforward and safe. Line up who maintains it next so the site does not fall into a gap. If you want a clean handover to a new arrangement, that is a normal thing to plan for in advance.