The email bounced. The phone number goes to voicemail. Your developer has vanished, and you’re running a business that depends on your website.
I’ve helped recover dozens of websites in this situation. Sometimes the developer got overwhelmed. Sometimes they moved on to other work. Sometimes they just stopped responding. The reason doesn’t matter when your website needs updating and you can’t reach the person who built it.
Here’s exactly how to recover.
Week 1: Regain Access
Your first priority is getting control of the critical accounts. You need three things:
Domain registration account - This is where your domain name (yourcompany.co.uk) is registered. Common UK registrars include 123-Reg, Namecheap, and GoDaddy.
Hosting account - Where your website files live. Could be shared hosting, VPS, or a platform like Netlify or Vercel.
Any other services - Email hosting, SSL certificates, CDN services, analytics.
If the accounts are in your name
Contact the provider’s support directly. You’ll need to prove you own the business:
- Business registration documents
- Invoice history showing you paid the bills
- Domain ownership documentation
- Email from your business domain
Most UK registrars have account recovery processes. They’re designed for this exact situation. I’ve never seen a legitimate business owner locked out permanently when they could prove ownership.
If the accounts are in the developer’s name
This is trickier but still recoverable. You have options:
1. Domain transfer - If you can prove you own the business name as a trademark or company registration, most registrars will help transfer ownership. This process takes 5-7 days but it’s reliable.
2. Hosting export - Even without account access, you can often get your website files and database. The hosting company wants to keep you as a customer. Explain you’ve lost contact with your developer and need to maintain your business website.
3. Legal route - Send a formal letter to the developer’s last known address requesting account transfers. In the UK, if you paid for the work, you own the website content. Most developers will cooperate when they receive formal notice.
The nuclear option: Rebuild from the live site
If you truly can’t get backend access, you can still save your website. Tools like HTTrack can download your entire live website. You won’t get the backend code, but you’ll have all the pages, images, and content.
This isn’t ideal - you lose the ability to edit easily - but it keeps you online while you plan a proper rebuild.
Week 1-2: Assess the Damage
Once you have access, you need to understand what you’re working with. I use a simple assessment framework:
What’s actually there?
Open your hosting file manager or FTP. Look for:
- A known platform - WordPress folder structure, clear framework files
- Custom code - Random PHP files, unclear organization
- Documentation - README files, comments, setup instructions
- Recent backups - Automated backup files in hosting
What’s the quality level?
Check for warning signs:
Red flags:
- No backups configured
- Outdated software (WordPress 4.x when 6.x is current)
- Hardcoded content in PHP files
- No SSL certificate or expired
- Plugins not updated in 12+ months
Good signs:
- Automated backups running
- Recent updates visible in logs
- Staging environment exists
- Clear folder structure
- Documentation present
What are you paying for?
List every service and its cost:
- Domain registration: £10-15/year
- Hosting: £5-50/month
- Email: £0-10/month per user
- SSL: Often free, sometimes £50/year
- Other services: Varies widely
I once found a client paying £180/month for basic shared hosting that should cost £10/month. The developer had marked up services significantly.
Week 2: Maintain Stability
Before you change anything, ensure the site stays online.
Create fresh backups
Use your hosting control panel (cPanel, Plesk) to create complete backups:
- Full file backup (all website files)
- Database backup (usually MySQL)
- Email backup if hosted with the site
Download these to your computer. Cloud storage as well. Multiple copies.
Document everything
Create a spreadsheet with:
- Every account (host, domain, email, SSL, CDN)
- Login credentials (use a password manager)
- Renewal dates
- Costs
- Contact information for support
This becomes your handover document for the next developer - or for yourself if you’re managing it going forward.
Test critical functions
Don’t assume everything works just because the site loads:
- Contact forms - Send test submissions
- E-commerce - Place test orders
- Booking systems - Make test bookings
- Email - Send and receive
I’ve seen sites where the contact form hadn’t worked for months and the business owner didn’t know because they couldn’t test it.
Week 2-4: Plan Your Migration
Now you’re stable. You have access. You understand what you’re working with. Time to decide your path forward.
Option 1: Find a new developer to take over
If the site is well-built and on a standard platform, another developer can take over maintenance.
Good candidates for takeover:
- WordPress with popular plugins
- Shopify or similar platforms
- Well-documented custom builds
- Recent technology stack
Poor candidates:
- Custom frameworks nobody uses
- Outdated technology (PHP 5.6, etc.)
- No documentation
- Heavily customized platform
When interviewing new developers, ask: “Can you maintain this, or should we rebuild?” An honest developer will tell you if it’s a mess.
Option 2: Migrate to a fresh build
Sometimes starting fresh is cheaper than fixing what’s there.
Rebuild makes sense when:
- Site is badly outdated (5+ years old)
- Security vulnerabilities present
- Technology is obsolete
- Faster to rebuild than untangle
Migration makes sense when:
- Site is relatively modern
- It’s working well for your business
- You mainly need access and documentation
- Custom features that would be expensive to recreate
I rebuilt a site for a solicitor’s office where the previous developer had created a custom content management system. Migrating to WordPress took 3 days and cost £2,500. Trying to document and maintain the custom system would have cost £5,000+ and left them dependent on specialized knowledge.
Option 3: Platform migration
Move your existing content to a more maintainable platform.
Common migrations I handle:
- Custom PHP to WordPress - Content stays, better editing
- Old WordPress to modern WordPress - Fresh install, migrate content
- HTML site to Astro - Fast, modern, easy updates
- Complex CMS to simple platform - Reduce overhead
The goal is making your website maintainable by regular developers, not just the one person who built it.
The Migration Process
Whether you’re moving to a new host, new platform, or new developer, the process follows similar steps:
1. Set up the new environment
Create your new hosting or development environment. Don’t touch the old site yet - you’re building parallel.
For most small business sites, I recommend:
- Vercel or Netlify for modern static sites
- Managed WordPress hosting for content-heavy sites
- Established hosting like Krystal for traditional hosting
If you’re recovering from a developer disappearance, our business website service includes migration from existing sites with proper documentation and ownership.
2. Migrate content first
Get your pages, blog posts, images, and products into the new system. This is the bulk of the work.
Use migration tools where available:
- WordPress to WordPress: Built-in export/import
- HTML to new platform: Manual but straightforward
- Custom to anything: Usually requires development
3. Migrate functionality
Contact forms, booking systems, e-commerce - these need testing.
Don’t assume a plugin or feature works identically. Test everything:
- Forms submit correctly
- Emails deliver
- Payments process
- Booking confirmations send
4. Test on a staging domain
Most hosting lets you preview the new site before switching. Use a temporary domain like newsite.temp.domain.
Show it to colleagues. Click everything. Use mobile. Send test forms.
5. Switch the domain
This is usually just updating DNS settings to point your domain to the new hosting. The actual switch takes 5 minutes, but DNS changes can take 24-48 hours to fully propagate.
6. Monitor for 48 hours
Watch for:
- Broken links
- Missing images
- Forms not working
- Email issues
- Search ranking changes
Keep the old site running for at least a week as backup. Once you’re confident, you can shut it down.
Preventing This Next Time
You’ve recovered. Now make sure this never happens again.
Demand access from day one
Before paying a deposit, ensure you’ll have:
- Domain registrar account in your name
- Hosting account credentials
- Admin access to the website
- Documentation for any custom work
These should be deliverables, not favors.
Use platforms, not custom code
Unless you have specific needs, standard platforms are safer:
- WordPress for content sites
- Shopify for e-commerce
- Squarespace for simple brochure sites
- Astro or similar for modern static sites
The easier it is for another developer to understand your site, the less dependent you are on one person.
Require documentation
Your developer should provide:
- Setup instructions
- List of all plugins/dependencies
- Credentials document
- Backup procedures
- Update procedures
I provide this as standard. It takes an extra hour but prevents exactly this situation.
Schedule regular backups
Automated backups should run:
- Daily for e-commerce or frequently updated sites
- Weekly for most business sites
- Stored off-site, not just on the hosting server
Most hosting includes this. Make sure it’s actually configured.
Test the disaster recovery plan
Once a year, verify you can:
- Access all accounts
- Download a backup
- Restore from backup
- Contact support if needed
If you can’t do these things, you don’t actually have control of your website.
What I Do Differently
When I take on a new client, they get:
Full access immediately - Domain, hosting, and admin credentials in their password manager before I start building.
Built on standard platforms - Astro for static sites, WordPress for content sites. Any developer can take over.
Complete documentation - Every decision explained, every dependency listed, contact information for all services.
Handover built into the process - Even if they stay with me for years, they could leave tomorrow with zero friction.
The website is your asset. You should have complete control of it.
When to Call for Help
Some situations are straightforward. Some need professional help.
Get professional help when:
- Complex custom functionality you don’t understand
- E-commerce site with active orders
- Domain is in someone else’s name and they won’t respond
- Security vulnerabilities present
- Time-sensitive business impact
A professional recovery typically costs £500-2,000 depending on complexity. Much less than rebuilding, and you keep your existing content and search rankings.
Most developer disappearances aren’t malicious. Life happens. People get overwhelmed. Projects fall through the cracks.
But your business can’t wait for someone to respond to emails. With the right approach, you can recover access, assess what you have, and migrate to a stable setup - whether the original developer helps or not.
The goal isn’t revenge or finding out why they disappeared. The goal is getting your business website under your control and keeping it there.
