Environment inventory
The first step is documenting PHP versions and modules, database versions, disk usage, inode pressure, web-server type, caching layers, cron jobs, SSL certificates, DNS records and mail dependencies. This becomes the migration checklist for the destination.
Server-to-server transfer
Files are transferred with methods appropriate to the access available, databases are exported consistently, and ownership and permissions are corrected on the destination. Large sites may use rsync-style incremental copies so the final transfer window stays small.
Control panels and custom stacks
I handle common moves involving cPanel, Plesk, CyberPanel and unmanaged Linux servers. When the destination is a custom stack, the web server, PHP-FPM, database service, Redis or object cache and TLS configuration are validated as part of the move.
Cutover and rollback
DNS is changed only after the destination is tested. The old server is kept intact during the validation period whenever possible, providing a practical rollback path if an unexpected application-specific issue appears.
Related services
What we confirm together
A server can host workloads beyond WordPress. Those dependencies need an inventory before the destination is prepared. Ongoing server administration and incident response should be agreed explicitly if required after migration.
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.