- 1) Freeze Changes (Or Plan a Final Sync)
- 2) Take Backups (And Verify They Actually Work)
- 3) Collect Access Details (This Saves Hours)
- 4) Audit Your DNS Records (Don’t Break Email or Verification)
- 5) Reduce DNS TTL (So Cutover Happens Faster)
- 6) Plan Email Migration Separately (Website Move ≠ Email Move)
- 7) Check PHP Version + Extensions (Avoid 500 Errors)
- 8) Prepare a Testing Plan (Staging/Preview Before DNS)
- 9) SSL and HTTPS Plan (Avoid Mixed Content)
- 10) Schedule the Cutover Window (And Communicate)
- Final Pre-Migration Checklist
- Need Help?
- Related Hosticko Pages
- Helpful External References
Doc Summary
A successful migration is mostly preparation. If you do the right things before you move, you avoid downtime, missing emails, broken pages, and “why is my SSL not working?” headaches. This pre-migration checklist is your step-by-step plan for a smooth transition to Hosticko—whether you’re moving a WordPress site, a custom PHP website, or multiple domains.
1) Freeze Changes (Or Plan a Final Sync) #
Websites and emails change constantly. If you migrate while content is being edited, orders are coming in, or email is flowing, you can end up with mismatched data.
- For websites: Avoid publishing new posts/pages, updating plugins/themes, or making major design changes during the migration window.
- For eCommerce: Plan a short “maintenance mode” period for final sync, or migrate during the lowest-traffic hours.
- For databases: The fewer writes during migration, the less risk of missing records.
2) Take Backups (And Verify They Actually Work) #
Backups are your safety net. Make sure you have at least one complete backup before you touch anything.
- Files backup: Full website directory (including hidden files like
.htaccess). - Database backup: Export via phpMyAdmin (or equivalent) as
.sql/.sql.gz. - Email backup (if possible): If you use an email client like Outlook/Thunderbird, ensure mail is synced locally or export if needed.
Pro tip: Don’t assume backups are good. Spot-check: open the SQL file, confirm it’s not empty, and confirm your ZIP contains the expected folders.
3) Collect Access Details (This Saves Hours) #
Most “migration problems” are just missing credentials. Before migration day, collect:
- Old hosting login (cPanel/DirectAdmin or custom panel)
- FTP/SFTP credentials (and server/port)
- Database name, user, password, and host
- Domain registrar access (where nameservers are set)
- DNS zone access (Cloudflare/registrar DNS/hosting DNS)
- Email accounts list (addresses, passwords, mailbox sizes)
4) Audit Your DNS Records (Don’t Break Email or Verification) #
DNS is not just your website. It’s usually email, verification, and third-party services too. Before migrating, export or screenshot your current DNS zone.
DNS Records to Watch Closely #
- A/AAAA records: website IP routing
- CNAME records: subdomains like
www, tracking, app portals - MX records: email routing (very important)
- TXT records: SPF, DKIM, DMARC, and domain verification
Important: If you use Google Workspace or Microsoft 365, you must preserve their MX/SPF/DKIM/verification records during your site move, or email may stop working.
5) Reduce DNS TTL (So Cutover Happens Faster) #
TTL controls how long networks cache your DNS records. If you lower TTL 24–48 hours before migration, your DNS changes propagate faster.
- Typical TTL: 3600 (1 hour) or higher
- Recommended for migration: 300 (5 minutes) or 600 (10 minutes)
Best practice: Lower TTL in advance, do the cutover, then increase TTL again later.
6) Plan Email Migration Separately (Website Move ≠ Email Move) #
One of the most common mistakes: people migrate the website and forget email. Email typically depends on MX records, not where your website files live.
Before You Move Email #
- List all mailboxes and aliases
- Check mailbox sizes (big mailboxes take longer)
- Confirm if IMAP is enabled on the source provider
- If 2FA is enabled (Gmail/Outlook), generate an app password if required
Zero-loss approach: migrate website first, keep MX pointing to old provider, then migrate email, then switch MX.
7) Check PHP Version + Extensions (Avoid 500 Errors) #
Many sites fail after migration because the new server runs a different PHP version or missing extensions.
- Note your current PHP version on the old host
- List critical extensions:
mysqli,mbstring,curl,gd,zip,intl - For WordPress: confirm your theme/plugins support your target PHP version
8) Prepare a Testing Plan (Staging/Preview Before DNS) #
Testing before the DNS switch prevents “surprises” in production.
- Use a temporary URL, subdomain, or hosts file approach to preview the migrated site.
- Test homepage, top pages, contact forms, logins, and checkout (if any).
- For WordPress: re-save permalinks (Settings → Permalinks → Save Changes).
9) SSL and HTTPS Plan (Avoid Mixed Content) #
If your site uses HTTPS, plan for SSL issuance after DNS points to Hosticko.
- Issue SSL (AutoSSL/Let’s Encrypt depending on plan)
- Force HTTPS and verify there are no mixed-content warnings
- Update site URL to
https://(WordPress: Settings → General)
10) Schedule the Cutover Window (And Communicate) #
Pick a low-traffic time. For business sites, night hours or weekends often work best. If multiple people manage the site, tell them:
- When the migration starts
- When to pause content changes
- When DNS will be updated
- What to do if they see old/new versions during DNS propagation
Final Pre-Migration Checklist #
- ✅ Full file + database backups taken and verified
- ✅ DNS records exported / documented
- ✅ TTL lowered 24–48 hours in advance
- ✅ Email accounts list prepared (and migration plan decided)
- ✅ PHP version and required extensions checked
- ✅ Staging/preview testing plan ready
- ✅ Cutover window scheduled
Need Help? #
If you want Hosticko to review your checklist, assist with DNS planning, or troubleshoot migration issues, submit a support ticket here:
https://client.hosticko.com/submitticket.php
