Migrations and upgrades
Hosts, domains, PHP versions and multisite splits, with every row and every redirect accounted for.
A migration is not a file copy. It is a rehearsal, a cutover and a rollback plan, and the difference shows up three weeks later in your search traffic.
What is involved
- A full inventory: what is actually running, what it depends on, what has been customised in place.
- A rehearsal migration to the new environment, tested against real data.
- Serialised data handled with tooling that understands it, so no widget, option or page builder layout arrives corrupted.
- A redirect map covering every URL that changes.
- DNS and mail cut over with the TTL lowered in advance so the window is minutes, not days.
- Post-migration verification: forms, checkout, scheduled tasks, mail, search indexing.
PHP and WordPress upgrades
Same discipline for a major version jump. Compatibility checked against your actual plugin set on a staging copy first, with a written list of what will break and what it costs to fix, before anything touches the live site.
