Your WordPress site is running slow, plugins break with every update, and your developer vanishes for weeks. If this sounds familiar, it might be time to find someone new. Switching developers is uncomfortable but sometimes necessary—and doing it right protects your site and budget.
Signs Your Current Developer Isn't Working
Poor communication is the most common red flag. If you're waiting days for responses, getting vague explanations about what was changed, or can't reach them when something breaks, that's a problem. A solid developer responds within 24 hours and explains technical work in terms you understand.
Quality issues pile up fast. You notice security vulnerabilities aren't being patched, the site crashes regularly, or custom code is poorly documented. When you ask for fixes, they either ignore the problem or charge you thousands for what should be routine maintenance.
Unexpected costs are another signal. Your developer quoted $3,000 for a feature but billed $8,500. They add "urgent fees" or surprise charges for work that seemed included. Reputable WordPress developers (typically charging $50–200/hour or $5,000–25,000 for project-based work) are transparent about scope and costs upfront.
Planning Your Exit Strategy
Before breaking things off, document everything. Export your database, take screenshots of your site structure, note which plugins and themes are installed, and collect any custom code or configuration files. Request a full backup from your current developer—in writing, via email—so you have proof they delivered it.
Create a handover document listing:
- Login credentials (update all passwords first)
- Hosting provider and admin access
- Current plugin list with versions
- Any custom development work completed
- Outstanding issues or bugs
- SSL certificate details
This prevents your new developer from wasting 10+ billable hours reverse-engineering what should have been documented.
Choosing Your Next Developer
Look for someone with proven WordPress experience, not just general web development. Ask for:
- Portfolio of live sites they've built or maintained (not just screenshots)
- References from past clients who'll confirm reliability and communication
- Maintenance and support availability (24/7 emergency response, regular backups, security monitoring)
- Transparent pricing with a written contract listing what's included
- Migration experience so they can safely move your site without downtime
WordPress specialists typically cost more upfront ($8,000–20,000 for a complex migration) but save money long-term through better security, performance, and fewer emergencies. Budget $2,000–5,000 for a basic site transfer and $500–1,500/month for ongoing maintenance with reputable providers.
Mercoly makes it easy to compare trusted WordPress development providers side-by-side, so you can review rates, specializations, and client feedback before committing.
Executing the Handover
Give your current developer written notice (email counts). State clearly: "We've decided to work with another development team, effective [date]." Two weeks' notice is standard for ongoing work, but you can request immediate access to your files and credentials.
During the transition:
- Have both developers in communication so nothing falls through cracks
- Test everything on a staging environment before going live
- Schedule the actual switchover during low-traffic hours
- Verify all backups, databases, and assets are accessible to your new team
- Check that your site functions identically after migration (test forms, payments, logins)
Most migrations take 3–7 days for a standard site, longer for complex setups. Expect minor downtime (under 1 hour) unless your new developer does a no-downtime migration (more expensive but worth it for high-traffic sites).
Moving Forward
Set clear expectations with your new developer from day one. Establish communication norms, response times, and escalation procedures. Schedule monthly check-ins to discuss performance, security, and upcoming updates rather than only talking when something breaks.
A good WordPress developer is an investment in your site's future, not just a cost center.
Frequently Asked Questions
Q: Can my current developer hold my site hostage by keeping access? No—your site lives on hosting you can access directly. If they won't provide credentials, your hosting provider (GoDaddy, Kinsta, WP Engine, etc.) can reset admin access within hours. Request account ownership transfer in writing.
Q: How long does a WordPress site migration actually take? A straightforward migration takes 2–5 days for testing and verification, though the actual data transfer is often just hours. Complex sites with custom integrations, WooCommerce stores, or membership plugins may need 1–2 weeks.
Q: Should I stay with my current developer's hosting, or switch providers too? You can stay or switch independently—they're separate decisions. If you're unhappy with both, changing both makes sense; if hosting is reliable, keep it. Just ensure your new developer has full admin access.
Find a WordPress developer who communicates clearly and charges fairly—use Mercoly to compare your options today.