Moving a website involves files, databases, DNS, and connected services. Transferring a domain registration does not move the website or its mailboxes. Plan those tasks separately, and keep the old hosting available until you have verified the replacement.
Prepare hosting before moving traffic #
The hosting account begins setup after payment and, for a new domain purchased with it, registration confirmation. Account creation does not wait for website DNS. Keep your live site's existing DNS while you copy and test its replacement. Open My Account → Hosting services to check activation and use Manage website for the destination domain.
Keeping your current DNS provider is the default connection method. You can also choose Lucid nameservers. Before any delegation change, record the existing zone and preserve mail routing, SPF, DKIM, DMARC, verification records, and subdomains. These records and DNSSEC DS changes do not migrate automatically; coordinate them with support.
Prepare and copy the site #
- Inventory website files, databases, PHP requirements, scheduled tasks, mailboxes, and external integrations.
- Take complete backups and store a copy off the hosting account. Confirm available access at both hosts.
- Once the account is active, use the Control Center's Databases tab to create a database if needed, then upload files and import data through Virtualmin. Update private application connection settings. The dashboard's WordPress list does not perform migrations, and its Backups tab does not provide a configured backup service.
- Use a host-approved preview method when available. Virtualmin may offer Web Configuration → Preview Website, but a preview is not a substitute for testing the final hostname and HTTPS certificate. Virtualmin preview guidance
- For WordPress URL changes, use a migration method that preserves serialized settings. WordPress migration guide
Launch and verify #
Arrange a final data synchronization and pause new writes when needed, especially for stores. For external DNS, apply the website records shown in setup and run its check; keep web records DNS-only during initial verification. For Lucid DNS, follow the nameserver/delegation checks. Once the selected method is confirmed, request SSL through the setup controls. Issuance still depends on successful validation.
Test HTTPS, internal links, login, forms, media, redirects, and safe test transactions. Verify email separately; connecting website DNS does not establish that mail delivery works.
Monitor both hosts during DNS cache transition so you can reconcile any activity that reached the old site. Enable production jobs only where they should run; duplicate schedulers can send duplicate messages or process work twice.
Rollback and cleanup #
Keep backups and the old service until your checks pass. If launch fails, coordinate the rollback with support and preserve new production data. A DNS reversal is not instantaneous and does not merge databases.
Remove temporary exports and preview access after verification, arrange ongoing backups, then cancel the old service through its billing process.
Related: database migration, adding a website to existing hosting.
Leave a Reply