A backup is useful only when it is complete, current, and restorable. A migration is successful only when the new site works for visitors, administrators, search engines, forms, and integrations. Treat both tasks as repeatable workflows instead of one-click events.

Know what must be protected

A complete WordPress backup usually includes the database, uploads, themes, plugins, configuration files, and any custom code outside standard directories. Stores and membership sites may also depend on rapidly changing orders or user data, which affects the timing of the final backup.

Use more than one location

Keep an off-site copy that remains available if the hosting account fails. Retention matters too: one recent backup cannot help if an unnoticed problem began weeks ago. Use a schedule that reflects how often the website changes and how much data the business can afford to recreate.

Test before the move

• Restore a copy to staging and confirm that it opens correctly.
• Check PHP, database, and server requirements at the destination.
• Search for environment-specific URLs and paths.
• Plan DNS, SSL, email, cron jobs, and caching changes.
• Choose a maintenance window for dynamic websites.

Verify after launch

Test navigation, forms, account login, search, checkout, downloads, and transactional email. Regenerate permalinks if necessary and inspect browser and server errors. Keep the old environment unchanged until the new one has been verified and a fresh post-launch backup exists.

The best migration workflow is documented, reversible, and calm. Tools can automate file transfer, but thoughtful preparation is what protects the website.