Website Migration Checklist: Move to UKNode with Minimal Downtime

Before you start

• Audit your current setup: domains, subdomains, email accounts, DNS management location, PHP version, database size, cron jobs and SSL details.
• Reduce DNS TTL values: set A/AAAA and MX records to 300 seconds at least 24 hours before migration.
• Prepare a rollback plan: keep a full backup of site and database, and do not cancel existing hosting until migration completes.

Migration checklist

• Create a full backup: download site files (public_html), export databases via phpMyAdmin or CLI, save config files (wp-config.php, .env).
• Provision UKNode hosting: create the account or server, set up the primary domain, create a new database and user.
• Upload files and import the database: transfer via SFTP or file manager, import the database, update config files with new credentials.
• Test on a temporary URL or hosts file: check page loads, forms and dynamic content, verify admin access, confirm images/CSS/JS load.

DNS cutover

• Update DNS records: point A/AAAA records to the UKNode IP, update CNAMEs for subdomains, update MX records if email is migrating.
• Verify propagation using multiple networks/tools — expect minutes to 24 hours.

Post-migration checks

• Enable SSL and force HTTPS (Let's Encrypt or custom certificate).
• Validate email and forms; confirm SPF, DKIM and DMARC if configured.
• Monitor performance: check page speed and error logs, and ensure cron jobs are running.

Common issues and fixes

• Mixed-content warnings: update protocol references in code and cached assets.
• 500 errors after migration: check PHP compatibility, file permissions/ownership and error logs for missing modules.
• DNS not updating: verify record values and TTLs, and test from different networks.