DirectAdmin backup and restore can move WordPress safely when it matches the source, destination, and risk level. This method is best for DirectAdmin-to-DirectAdmin account moves and migrations where account data, files, databases, and mail must stay together.
Audience: DirectAdmin users, resellers, and admins moving WordPress sites or accounts. 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
- Decide whether the move is user-level, reseller-level, or admin-level.
- Check destination PHP, database, DNS, SSL, and disk capacity.
- Back up the source and document email routing.
- Lower DNS TTL before cutover.
Migration steps
- Create the DirectAdmin backup at the correct scope.
- Transfer the backup to the destination safely.
- Restore the user or selected data on the destination DirectAdmin server.
- Check database users, file ownership, domains, SSL, cron, and email.
- Preview the WordPress site.
- Change DNS only after validation.
Post-migration verification
Test WordPress pages, wp-admin, media uploads, plugins, forms, mail, cron jobs, SSL, and error logs. Confirm old server traffic drains after DNS cutover.
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
- Wrong restore scope can overwrite unrelated data.
- Database users or file permissions may need correction.
- Mailboxes and DNS zones can surprise you if not reviewed before launch.
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 DirectAdmin backup and restore 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 JetBackup Restore Point
- 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
