Quick answer
The hard part is not file transfer; it is keeping data consistent while DNS and users move between two live environments.
Build and test the destination first
Copy the site while the old host remains live. Test the new environment using a temporary hostname or local hosts-file mapping.
Reduce the write gap
For stores and memberships, schedule a short maintenance or final-sync window or use a migration method that can copy late database changes.
Keep rollback simple
Do not cancel the old host immediately. Preserve the prior DNS values and a recent source backup until the new environment is stable.
Where Cloudways enters the decision
Cloudways migration tooling can move WordPress data, while staging and backup features help create a safer destination. The cutover process remains your responsibility.