Website Migration Checklist: Move to UKNode with Minimal Downtime
Migrating a website does not need to be risky or disruptive. This checklist walks you through a smooth move to UKNode, covering preparation, transfer, testing, and DNS cutover so you can minimize downtime and avoid surprises.
Before You Start
1. Audit Your Current Setup
- List your domains, subdomains, and email accounts
- Identify where DNS is managed (registrar or third party)
- Note your current PHP version, database size, and cron jobs
- Record your SSL certificate details (issuer, expiry date)
2. Reduce DNS TTL Values
Lower your DNS TTL to speed up the cutover.
- Set A/AAAA and MX records to 300 seconds (5 minutes)
- Make the change at least 24 hours before the migration
3. Prepare a Rollback Plan
- Keep a full backup of your current site and database
- Avoid canceling your existing hosting until the migration is complete
Migration Checklist
4. Create a Full Backup
- Download site files (public_html or equivalent)
- Export databases via phpMyAdmin or CLI
- Save any configuration files (wp-config.php, .env, etc.)
5. Provision Your UKNode Hosting
- Create the new hosting account or server
- Set up your primary domain
- Create a new database and user
6. Upload Files and Import Database
- Upload files via SFTP or file manager
- Import the database into the new host
- Update config files with new database credentials
7. Test on a Temporary URL or Hosts File
Validate functionality before pointing DNS:
- Check page loads, forms, and dynamic content
- Verify admin access (e.g., WordPress dashboard)
- Confirm images, CSS, and JS load correctly
DNS Cutover
8. Update DNS Records
- Point A/AAAA records to your UKNode IP
- Update CNAME records for subdomains if needed
- Update MX records if email is moving
9. Verify Propagation
- Use multiple networks or tools to confirm DNS changes
- Expect global propagation to take a few minutes up to 24 hours
Post-Migration Checks
10. Enable SSL and Force HTTPS
- Install an SSL certificate (Let’s Encrypt or custom)
- Force HTTPS in your app or via redirects
11. Validate Email and Forms
- Test outgoing email and contact forms
- Confirm SPF, DKIM, and DMARC settings if configured
12. Monitor Performance
- Check page speed and error logs
- Ensure scheduled tasks (cron jobs) are running
Common Issues and Fixes
Mixed Content Warnings
- Update hard-coded HTTP URLs to HTTPS
- Regenerate cached assets if your CMS supports it
500 Errors After Migration
- Confirm PHP version compatibility
- Check file permissions and ownership
- Review error logs for missing modules
DNS Not Updating
- Double-check record values and TTLs
- Clear local DNS cache or test on a different network
Conclusion
With the right preparation, a website migration can be predictable and low-risk. Follow the checklist, validate thoroughly before the DNS cutover, and keep your previous hosting active until everything is verified.
Need help migrating? Our team can assist with transfers and verification. Contact us and we’ll help plan a smooth move.