Website and application
Move code, files, configuration, database and certificates in a controlled order.
Tool
Cloud migration checklist for business
A practical checklist for migrating applications, websites, mail and DNS to the cloud: backup, TTL, SSL, tests, monitoring and rollback.
Cloud migration should not start with copying files. First identify applications, websites, mail, databases, DNS, certificates, backups, scheduled tasks and administrative access.
Choose a cloud server
VPS, cloud server, dedicated server or hybrid model.
Containers after migration
Docker, Kubernetes and application environments.
DNS audit
Delegation, DNSSEC, HTTPS and mixed content after the change.
SSL after switch
Certificate, trust chain and domain names.
Business mail
MX, SPF, DMARC and old records after migration.
PageSpeed
Status, response time, cache and compression.
Application migration to the cloud: work order
A good migration starts by keeping a return path. Before switching DNS, prepare data copies, application configuration, dependency lists, access to the previous server and a clear post-switch verification plan.
What should be migrated together?
Database
Plan synchronization, write freeze or replication so the application does not write to two places.
Business mail
Handle MX, SPF, DKIM, DMARC, webmail, IMAP and application senders separately.
DNS and certificates
Check DNS, SSL/TLS, redirects and mixed content immediately after the switch.
Migration checklist
- Inventory services. List domains, subdomains, applications, databases, mailboxes, cron jobs, integrations and user files.
- Prepare backup. Copy files, databases, configuration, certificates and secrets, then test restore.
- Lower DNS TTL. Prepare A, AAAA, CNAME, MX, SPF, DKIM and DMARC changes and a rollback plan.
- Prepare target infrastructure. Configure server, firewall, users, monitoring and backup.
- Test before production traffic. Use a technical address or hosts entry before public DNS points to the cloud.
Post-migration tests
- The site or application returns the expected HTTP status and no backend errors.
- SSL/TLS matches all host names and has a correct trust chain.
- No mixed content or old HTTP resources remain.
- DNS points only to the new environment.
- Mail still has correct MX, SPF, DKIM and DMARC.
- Backup, monitoring and application logs are available.
FAQ: cloud migration
How should I use this DataHouse page?
Use it as a technical checklist and connect it with the relevant diagnostic tools before or after a production change.