Cyclone Hosting practical guide: A low-downtime migration is a sequence of inventory, copying, testing, DNS planning, and post-move monitoring.
Good Migrations Are Planned Before Files Move
A website migration involves more than copying public files. You may also need databases, email, DNS records, SSL, scheduled tasks, configuration files, and application-specific settings.
Inventory The Current Site
- Website files and document roots
- Databases and users
- Email accounts and forwarders
- DNS records
- PHP version and extensions
- Scheduled tasks
- SSL and redirects
Create Independent Backups
Download copies of files and database exports before the move. Do not rely only on a control-panel transfer.
Build And Test Before DNS Changes
Upload the site to the new server and test it using a temporary URL, hosts-file entry, or staging domain. Verify forms, logins, database writes, uploads, and email.
Prepare DNS
Lower TTL values ahead of time when possible. Record every existing DNS entry, especially mail, verification, and third-party service records.
Handle Dynamic Data Carefully
Stores, forums, and membership sites can change while the migration is happening. Plan a brief maintenance window or final database synchronization to avoid losing new orders or posts.
Switch Traffic
Update the required DNS records or nameservers. Keep the old hosting account active while caches expire and visitors begin reaching the new server.
Monitor After The Move
Check access logs, error logs, forms, email, SSL, and important application functions. Keep the old backup until the new environment has been stable for several days.
Cyclone Hosting Practical Checklist
- Inventory files, databases, email, DNS, cron jobs, and PHP requirements.
- Test the copied site before changing public DNS.
- Plan for orders or posts created during the final synchronization.
- Keep the old account active until traffic and email have fully moved.
When To Contact Support
Contact Cyclone Hosting support when the issue involves the hosting account, server access, DNS hosted with us, email-server settings, SSL issuance, or an error you cannot isolate. Include the domain, the exact error, the page or mailbox affected, when it began, and the troubleshooting already attempted. Never send a password in a normal support message.
What To Record For Future Reference
Keep a short change log containing the date, the setting changed, the reason for the change, and the backup or rollback point. This makes future troubleshooting faster and helps separate a hosting problem from an application change.