Website Migration & Provider Switch Troubleshooting: A 5-Step Guide

Post-migration incidents are highly predictable—with 80% concentrated in just five common areas. Following the checklist systematically beats guesswork every ti…

Insights:Website Migration & Provider Switch Troubleshooting: A 5-Step Guide

Step 1: Verify DNS Resolution

  • Access the domain from different networks (mobile hotspot, different carriers).
  • Check whether the current DNS records point to the new server.
  • Check if any CDN or old records are still active.

Typical symptoms: Some users see the new site while others see the old one or cannot access it.

Step 2: Check Environment Consistency

Item Common Differences
Runtime Version Version may be higher or lower on the new machine; function behavior changes
Extensions Missing image, encryption, or caching extensions
Timezone 8-hour time display discrepancy
Upload Size Large file upload fails
Pseudo-static URL rule missing, page 404

Typical symptoms: White screen, "undefined function" error, incorrect time.

Step 3: Are all files present?

  • Verify the number of directory files and total size.
  • Check the upload, cache, and log directories.
  • Ensure templates and static assets are complete.

Typical symptoms: All images return 404, styles missing, broken page layout.

Step 4: Are permissions correct?

  • Are the upload and cache directories writable?
  • Is the log directory writable and rotatable?
  • Is the config file readable?
  • Are execution permissions set correctly?

Typical symptoms: Cannot upload, cache cannot be written, empty log files.

Step 5: Is the database consistent?

  • Comparison of table counts and row numbers.
  • Character set and collation rules.
  • Whether critical configuration tables are fully imported.
  • Whether auto-increment IDs conflict.

Typical symptoms: Partial content not displaying, empty admin panel lists, duplicate new content IDs.

Five-step troubleshooting logic

Troubleshoot from "can you reach it externally" to "is the data inside":

  1. DNS resolution → Can it be accessed.
  2. Environment → Can the program run.
  3. Files → Are resources in place.
  4. Permissions → Can it write.
  5. Data → Is content complete.

Troubleshooting in reverse often leads to getting lost in the code.

Common symptom-to-cause reference

Symptom Likely cause
Some users cannot open the site DNS or CDN switch is incomplete
Entire site white screen Missing runtime environment or extensions
All images returning 404 Upload directory not migrated
Unable to upload / cache失效 Directory permissions
Missing content Incomplete database import

Boundaries

The five-step troubleshooting covers migration-related incidents. If the issue existed on the original site (before migration), treat it as a standard incident and do not attribute it to the migration.

Related reading: