Migration checklist
Use this list before you change DNS. It does not replace backups or testing — it keeps common surprises visible.
Procurement SLA alignment: targets in SLA §5 for acknowledgements (severity table) apply once ticketing captures scope; WhatsApp pings are conversational—open a correlated ticket when finance requires an SLA clock.
Go-live verification pack
DNS is flipped — validate SSL termination, SMTP auth, SPF/DKIM, cron, gateways, CDN purges before closing the migration. Follow the standalone verification checklist.
Appendix · KVM VPS migrations
Use alongside the numbered steps below when the source workload is bare-metal or KVM (not necessarily cPanel). These bullets exist so finance can attach the same artefacts we ask NOC peers for.
- Snapshot block storage or image exports before changing DNS—even if control panel reinstall is faster than disk lifts.
- Validate virtio / storage drivers ahead of downtime; mismatched kernels are the silent multi-hour regressions.
- Plan IP cutover consciously: BGP/SWIPs, SMTP reputation, webhook callbacks, VPN allow-lists—all need pairing with HostStack-delivered IPs.
- Keep the old VPS hot until TTLs expire; rollback steps belong in ticket updates, not frantic WhatsApp voice notes alone.
- Edge mitigation tiers mirror the KVM hub disclosure (aggregate volumetric tiers tied to upstream scrubbing contracts)—budget CDN/WAF for parallel application-layer raids.
-
1.Freeze a full backup
Export databases, download site files, and snapshot email forwarders or mailboxes you still need.
-
2.Lower DNS TTL early
A day before cutover, reduce TTL on the domain so DNS changes propagate faster (often 300–600s).
-
3.Provision HostStack first
Order the target plan, create cPanel, and verify you can log in before you touch production DNS.
-
4.Move files & databases
Restore backups or use migration tools; test wp-admin or your app on a hosts file or temporary URL if available.
-
5.Verify email & SSL
Recreate mail accounts, test send/receive, and confirm Let’s Encrypt or your certificate covers the right hostnames.
-
6.Cut DNS & monitor
Point A/AAAA and MX records to HostStack; watch logs and open a ticket if you see mail loops or mixed content.