A WordPress migration gone wrong can tank your SEO, break your site functionality, and cost you weeks of revenue. Finding the right developer to handle this technical lift is the difference between a seamless transition and a nightmare. Here's how to vet and hire someone who'll actually deliver.
Why Migration Quality Matters
WordPress migrations involve more than copying files from one server to another. You're moving databases, updating URLs, preserving redirects, handling SSL certificates, testing plugins for compatibility, and ensuring zero downtime. A sloppy migration can break internal links, lose ranking signals, orphan media files, or corrupt your WordPress configuration. The stakes are high—especially if you're running an active business site.
What to Look for in a Developer's Track Record
Before hiring anyone, ask for concrete evidence of past migration work. A legitimate WordPress developer should provide:
- Client references or case studies specific to migrations (not just generic WordPress work)
- Before-and-after performance metrics—page speed, Core Web Vitals, crawlability
- Portfolio of similar-sized sites they've moved (a developer who migrated 50 small blogs may struggle with a complex e-commerce setup)
- Proof of SEO preservation—screenshots showing 301 redirects implemented, metadata intact, traffic retained post-migration
Ask for at least two recent client references you can actually contact. A developer confident in their work won't hesitate to provide them.
Key Technical Questions to Ask
Don't just ask if they've done migrations before. Dig into their process:
- How do you handle the database migration and URL updates? Listen for mentions of search-and-replace plugins, WP-CLI, or manual SQL—experienced developers know these tools.
- What's your downtime strategy? The best approach involves staging environments, DNS switching, or maintenance mode windows. They should have a specific answer, not a vague "we minimize it."
- How do you preserve SEO during the move? They should mention 301 redirects, XML sitemap updates, Google Search Console resubmission, and canonical tag management.
- Do you handle SSL certificate migration? This is non-negotiable for modern sites. If they don't mention it, walk away.
- What happens if something breaks mid-migration? Ask about their rollback plan and backup strategy. There should be multiple checkpoints where they can reverse changes.
Budget Realistic Pricing
WordPress migrations typically cost between $500 for a small, simple site to $5,000+ for complex enterprise migrations. Here's what affects price:
- Site size: A 50-page brochure site costs less than a 1,000+ page directory or WooCommerce store
- Complexity: Custom post types, advanced custom fields, membership plugins, and API integrations add time and cost
- Data integrity requirements: Sites handling sensitive data or high transaction volume cost more
- Timeline urgency: Rush jobs cost 20–40% extra
Get quotes from at least three developers. If someone quotes significantly lower than others, ask why—they may be cutting corners on testing or backup procedures.
Red Flags to Avoid
Skip developers who:
- Can't explain their technical process in at least moderate detail
- Refuse to provide client references
- Quote a price without asking detailed questions about your site
- Don't mention testing, staging environments, or backups
- Have no portfolio or public evidence of migration work
- Promise "guaranteed zero downtime" (technically unrealistic for all scenarios)
- Pressure you to decide quickly without a clear scope document
The Hiring Process
Once you've narrowed your list, request a formal proposal that includes:
- Detailed scope of work and timeline
- Testing checklist (forms, checkouts, redirects, plugin functionality)
- Communication cadence during the migration
- Post-migration support window (30 days is standard)
- Contingency plan if issues arise
A clear proposal protects both you and the developer.
Using a Marketplace
If you're comparing multiple providers, platforms like Mercoly let you browse vetted WordPress developers, read reviews from other clients, and compare services side-by-side—saving you the legwork of cold outreach.
Frequently Asked Questions
Q: How long should a WordPress migration take? A: Most migrations take 2–7 days depending on site size and complexity. Simple sites may finish in a day; large e-commerce or membership sites might take two weeks including testing phases.
Q: Will my site lose Google rankings during migration? A: Not if properly executed. Correct 301 redirects, updated sitemaps, and Search Console notification preserve rankings. Poor migrations can cause temporary traffic dips of 2–4 weeks.
Q: Should I migrate to a new host at the same time? A: You can, but it complicates troubleshooting. Migrate to new WordPress first, then change hosts—or do both with a developer experienced in combined migrations.
Find a WordPress developer who understands your migration needs and has proof of successful past work—your site's performance depends on it.