JetBackup restore point can move WordPress safely when it matches the source, destination, and risk level. This method is best for moving from a provider backup when direct panel transfer is unavailable or when a granular database and file restore is safer.
Audience: hosts and customers whose current provider exposes JetBackup backups. Before using this path, decide whether the move changes hosts, domains, DNS, email, PHP versions, database versions, cache layers, or business data. Those details matter more than the migration button itself.
Before migration
- Confirm which JetBackup restore types are available on the current host.
- Download or request exportable backup data before cancelling service.
- Match the destination PHP, database, and filesystem layout.
- Avoid database rollback without preserving fresh transactional data.
Migration steps
- Open JetBackup and select the relevant restore point.
- Export or restore the files and database needed for WordPress.
- Move the backup data to the destination server.
- Restore files and import the database on the destination.
- Update wp-config.php and URLs where needed.
- Preview the site before DNS cutover.
Post-migration verification
Check login, front-end pages, media, forms, checkout, cron, SSL, email routing, and logs. Confirm JetBackup is configured on the new provider if it will be part of the ongoing backup plan.
Also check server logs, PHP errors, WordPress Site Health, cache behavior, CDN routing, redirects, robots/indexing state, cron jobs, and whether a new backup job exists on the destination.
Migration risks
- Not every host allows direct backup downloads.
- Granular restore can miss hidden files or database users.
- Leaving the old host too soon can strand needed restore points.
Rollback and cutover planning
Keep the old site online until the new site is proven. For stores, memberships, bookings, LMS sites, directories, and lead-generation sites, plan a final data freeze or sync so records do not split between servers. Keep DNS rollback notes, old-host access, and a verified backup until traffic and logs are stable.
Fix I.T. Phill recommendation
Use JetBackup restore point when it gives you the cleanest preview and rollback path. If the site makes money or stores customer records, treat the final cutover as a maintenance window, not a casual copy job.
Related Fix I.T. Phill Guides
- How to Migrate WordPress: Complete Hosting Move Guide
- How to Migrate WordPress by cPanel Full Account Backup
- How to Migrate WordPress by WHM Transfer Tool
- How to Migrate WordPress by Plesk Migrator
- How to Migrate WordPress by Plesk WP Toolkit Clone
- How to Migrate WordPress by Softaculous Clone or Import
- How to Migrate WordPress by Installatron Clone or Import
- How to Migrate WordPress by DirectAdmin Backup and Restore
- How to Back Up WordPress: Complete Methods Guide
- How to Restore WordPress: Complete Recovery Methods Guide
- How to Back Up WooCommerce Without Losing Orders
- How to Restore WooCommerce Without Losing Orders
- How to Test a WordPress Backup Restore Before an Emergency
