What does this service cover?
What does a professional WordPress migration include?
A reliable migration covers more than wp-content and a database export. The destination must have a compatible PHP version, extensions, database engine, memory limits, cron behavior, SSL support and caching configuration. I inventory the current environment first so incompatibilities are found before DNS is changed. The transfer includes WordPress core files, themes, plugins, uploads, database tables, hidden configuration files and any site-specific rules that affect redirects or security.
How do you reduce downtime?
For sites that can be staged, I build and test the destination while the old site remains live. DNS TTL is reviewed before cutover, the destination is tested through a hosts-file or temporary URL where practical, and the final database sync is scheduled around site activity. This approach cannot make every migration literally zero downtime, but it minimizes the window and avoids switching traffic to an untested server.
Post-migration verification
After the switch I verify front-end pages, wp-admin, forms, transactional email, HTTPS, redirects, permalinks, scheduled tasks, caching and key plugin workflows. I also look for mixed-content errors, hard-coded old URLs and server-level redirects that can create loops or indexing problems.
Good fit for
Hosting changes, cPanel-to-cPanel moves, shared hosting to VPS, VPS to managed WordPress hosting, domain changes, staging-to-live deployments, large media libraries and migrations where a plugin transfer has already failed.
Typical scope
The exact work depends on your site, but these are the checks and tasks this service typically covers.
- Files, database and media completeness
- Domain, DNS and SSL cutover planning
- Serialized URL replacement where required
- Forms, login and ecommerce testing
- Redirect and Search Console post-launch checks
The exact scope is confirmed from the real site and problem before changes are made.
How the work proceeds
- Inventory the environment: document PHP, database, extensions, cron, SSL and caching on both ends before anything moves.
- Build and test privately: copy the complete installation to the destination and test via a hosts entry or temporary URL while the old site stays live.
- Handle URLs and cutover: perform serialized URL replacement where needed, lower DNS TTLs, then switch traffic only when the destination is ready.
- Verify everything: check pages, wp-admin, forms, email, HTTPS, redirects, permalinks and scheduled tasks after the switch.
What you need to provide
Most of the technical work is on my side. To start, I usually need:
- Admin access to the source and destination hosting
- Domain registrar or DNS management access
- A list of critical site functions to test — forms, checkout, memberships
- Preferred timing for the DNS cutover
Typical timelines
Standard migrations take 3–7 days including staging and verification. Large media libraries or complex setups take longer; the DNS switch itself is a short, scheduled event.
Frequently asked questions
Will my site be down during migration?
The aim is no visible downtime. The destination is built and tested while the original stays live; traffic switches only after verification.
Why not just use a migration plugin?
Plugins work for simple cases and fail on large sites, odd server configurations or serialized data. Manual migration handles URL replacement, permissions and environment differences that plugins gloss over.
What is “serialized URL replacement” and why does it matter?
WordPress stores some URLs in serialized PHP data where string lengths matter. A naive find-and-replace corrupts that data; proper tools update the lengths so widgets and settings survive.
Will my SEO be affected?
Not if done right — same URLs, proper redirects for any changed paths, and Search Console checks after launch. I verify indexation signals post-migration.
Can you migrate a very large site?
Yes — large media libraries and databases are handled with incremental transfer methods so the final cutover window stays small.
What if my current host is slow to provide access?
Common and manageable. I work with whatever access exists — control panel, FTP, database tools — and choose the transfer method accordingly.
What we confirm together
A standard brochure site can often be staged while the original remains live. Sites that accept changing data need a final synchronization plan. The exact method follows the application, not a fixed plugin workflow.
Before starting, we agree on access, affected systems, testing, timing and the handover. Hosting subscriptions, premium software and work outside that scope are identified separately.
Start with a clear scope
Describe your website and what needs to happen. You will receive a fixed scope, price and timeline before any work starts — no passwords needed at the enquiry stage.