Almost nobody leaves over price — they leave over silence, and the specific trigger is usually a small request that took three weeks or never happened at all. The decision is easier than the exit, so plan the exit before you announce the decision.
The moment it happens
What finally makes you leave your old web developer is rarely a dramatic failure. It’s a Tuesday. You need a phone number changed. You message. Nothing. You message again on Friday. “Sure sir.” Two weeks later the old number is still there, and you realise you’ve been managing this relationship for a year.
Buyers describe the underlying pattern plainly: once payment is complete, nobody listens.
The six reasons, and whether they justify switching
| Reason | Justifies switching? |
|---|---|
| Silence after full payment | Yes. This is the most common and the most reasonable |
| Small changes take weeks | Yes, if repeated. A number change is a ten-minute job |
| Charged per change with no plan | Not on its own — first ask for a fixed monthly plan |
| They hold your domain or logins | Yes, and fix this whether or not you leave |
| They can’t do what you now need | Yes, and it’s nobody’s fault. Businesses outgrow vendors |
| They’re cheaper than anyone else | Weak reason to stay if the first two apply |
Two reasons worth pausing on. Being charged per change is often fixable by asking for a monthly plan — many one-person developers have simply never structured one. And outgrowing a vendor is a legitimate, blameless switch; a developer who builds excellent brochure sites may genuinely not be the right person for a store with payments and stock.
Before you announce anything
This is the part people get wrong. Telling a developer you’re leaving before securing access converts an unresponsive vendor into an uncooperative one.
Do these four things first:
- Check whose name the domain is in. Run a WHOIS lookup. If it’s theirs, request the transfer as routine housekeeping now — not as part of a departure.
- Get hosting access, or confirm the plan is in your name with the hosting company directly.
- Download a full backup — files and database. This is the site itself in portable form.
- Collect your content — text, photographs, logo files — into your own folder.
With those four in hand, switching is a logistics exercise. Without them, it’s a negotiation.
Useful context: searches around website transfer in Delhi NCR attract almost no advertiser competition — top-of-page bids under ₹8. Very few companies market themselves to people in your position, which means you’ll need to look for migration specialists deliberately rather than expecting them to find you.
How to leave properly
Settle any genuine balance. If you owe something, pay it. A few thousand rupees is cheap compared with a contested handover.
Send one civil message. No grievances, no explanation of why:
Hi [name]. I’m moving the website management elsewhere. Could you confirm the domain registrar access, hosting login and site admin login, and send a full backup? Happy to settle anything pending. Thanks for your work.
Ask about anything registered in their name. Google Business Profile, analytics, business email, payment gateway. This is the question most people forget, and it’s often where the real dependency is hiding.
Don’t burn it. A developer you part from politely will usually answer one question six months later. One you’ve argued with won’t.
Handing over to someone new
Give the new developer, in one message: the domain registrar login, the hosting login, the site admin login, the backup file, and a short list of what’s currently broken or missing.
Then ask them two things before work starts. Will the domain stay in your own account — the answer must be yes. And how will they handle redirects if page addresses change, so you don’t lose search visibility.
When not to switch
Being fair to the incumbent:
- If the site works and you rarely need changes, an unresponsive developer is a mild irritation rather than a problem. Switching has a cost too.
- If you haven’t asked for what you want. Many developers respond well to “can we set up a fixed monthly plan with a response time?” — they’ve just never been asked.
- If you’re mid-project. Finishing with someone imperfect is usually faster than restarting, provided real progress exists.
- If the actual problem is that nobody visits your site. Switching developers doesn’t fix a traffic problem.
What to do this week
- Run a WHOIS check and confirm whose name the domain is in.
- Get hosting access and download a full backup.
- Collect your content into your own folder.
- Ask the incumbent for a fixed monthly plan before deciding to leave.
- If leaving, send the one civil message — and ask what’s registered in their name.
If you want it done the certain way
Tell us what access you currently hold and we’ll tell you what a clean migration involves and what it costs — including when staying put and asking for a maintenance plan is the better answer. Where we take over, the domain and logins sit in your account and redirects are handled. WhatsApp us; we reply in about five minutes between 9am and 7pm.
Related reading
- The friction of moving to a new developer
- Why does your developer stop replying after payment?
- ₹500 to change a phone number?
- The website handover checklist
FAQ
When should I change my web developer?
When support stops after payment, when small changes repeatedly take weeks, when they hold your domain or logins, or when your needs have outgrown what they build. Price alone is rarely a good reason either to stay or to leave.
What should I do before telling my developer I’m leaving?
Secure the domain in your own name, get hosting access, download a full backup, and collect your content. Announcing first can turn an unresponsive vendor into an uncooperative one.
Will switching developers affect my Google ranking?
It can if page addresses change during a rebuild without redirects. Ask your new developer to confirm how redirects will be handled before work starts.
