Create an inventory that survives a handover
For every website, record the customer owner, application revision, PHP requirements, engine dependencies, database, uploads, scheduled work, domain, and renewal authority. Identify unsupported software before planning capacity.
Migrate one representative application first
Choose a staging candidate with a known backup and rollback path. Validate its build, routes, data access, uploads, jobs, DNS plan, and recovery. Use the findings to adjust the checklist for the remaining applications.
Move the portfolio in reviewable groups
Schedule application groups with explicit approval and acceptance criteria. Keep old environments available until each owner confirms the result. Record unresolved issues and the exact release and data recovery point for every move.
