Choose an Installatron or full-site migration workflow, test the copy, and keep your domain and email working.
Use this guide when you already have a self-hosted WordPress site and want to move hosting while keeping the site. If your site is on WordPress.com, check the WordPress.com guide first. Keep the source account active and download an independent recovery copy before making changes.
Choose a transfer method
Installatron remote migration: In DirectAdmin, open Installatron, select WordPress in Applications Browser, and look for Import existing install → From a remote account. Where available, its migration wizard takes the source URL, a supported source-access method, and a destination. Enter credentials only in the secure wizard, not in chat or a support ticket. The old host must permit the chosen access method. Review the exact destination before starting; do not replace a working site unintentionally. This transfers the supported application, not your entire hosting account or email.
Full-site export/import: If that workflow is unavailable, use a reputable WordPress migration plugin compatible with both environments, or manually transfer files and the database. Check the plugin's current size, license, and restore limits first; an extension may cost extra. WordPress Tools → Export is a content export, not a complete copy of your theme, plugins, settings, and database.
- Check requirements. Record PHP requirements, plugin/theme licenses, source database size, media size, and integrations. Leave room for the live copy plus temporary migration data within your account storage. WordPress Multisite and unusual applications need a specific plan; this guide is for a conventional single-site installation.
- Prepare a safe destination. Add your domain on the assigned DirectAdmin server. For a plugin restore into a fresh WordPress installation, Installatron can create that installation first. For a manual copy, upload the source files and create/import its database, updating wp-config.php with the new database settings. Do not install a fresh application over an existing restored copy.
- Keep URLs deliberate. If the domain and path stay the same, keep those WordPress URLs. Use a local hosts-file override to test the new server. If using another domain or staging address, use a WordPress-aware migration/search-and-replace tool for serialized data; blind database text replacement can corrupt plugin settings.
- Check the real website. Test the dashboard, navigation, media, forms, search, permalinks, mobile layout, and any shop or membership functions. Recheck SMTP, API keys, licensed plugins, scheduled tasks, redirects, and CDN settings. Protect staging from public indexing; disable real payments, email campaigns, and duplicate scheduled jobs while testing.
- Plan the last update. For a store, bookings, or member site, arrange a maintenance window or final application-consistent sync. Do not allow both copies to accept independent orders or send duplicate payment notifications. Preserve existing external-mail DNS, or migrate mailbox history separately using the general migration checklist.
- Cut over and verify. Point the necessary website DNS records to the assigned server, obtain the free SSL certificate, and check HTTPS and mixed content. Remove the local hosts override to confirm public routing. Keep the source available for recovery until you have validated the move and DNS caches have expired.
- Set up ongoing care. Confirm the transferred site is listed in Installatron, or use its local existing-install import option where supported. Review automatic updates and backups rather than assuming the old host's settings followed the site. Remove only the specific migration installer and public backup artifacts you created once they are no longer needed.
Independent backups · WordPress setup and maintenance basics
Official references
Installatron remote migration · WordPress migration and URL guidance
