Pre-Migration & New Provider Launch Checklist: Step-by-Step Verification

The pre-switch checks have one purpose only: **confirm the new environment can run on its own**. Below are seven groups of checks—missing even one may surface i…

Insights:Pre-Migration & New Provider Launch Checklist: Step-by-Step Verification

I. Data Integrity

  • Number of tables matches the old database.
  • Row counts in key tables match the old database (minor differences must be explained).
  • Character set and collation rules are consistent.
  • No conflicts between auto-increment IDs and primary keys.
  • No truncation in large fields (text, JSON).

II. Environment Consistency

Item Check
Runtime Version Same as or verified compatible with the old environment
Extensions Complete (including image, encryption, and cache extensions)
Timezone Consistent
Upload Size Limit Consistent
Pretty Permalinks Rules migrated
Cron Jobs Recreated and tested

III. Functional Availability

  • Homepage, category pages, detail pages, and search results return HTTP 200.
  • Admin panel login, publish, edit, and delete functions work.
  • Form submissions succeed and notifications are delivered.
  • Payment and external APIs (if any) connect successfully.
  • File upload and download are operational.

IV. Resource Accessibility

  • All images, attachments, and videos are accessible.
  • No significant number of 404 errors.
  • Static assets have correct cache headers.
  • SSL certificate is valid; HTTPS has no mixed-content warnings.

V. DNS Resolution & Filing

  • TTL was lowered in advance.
  • DNS records match the old site (verify A/CNAME/MX separately).
  • Filing affiliation updated (for mainland China servers).
  • Email-related records (MX, SPF, DKIM) have not been accidentally changed.
  • 6. Monitoring & Backups

    • Monitoring has been redirected to the new environment.
    • Backup tasks are running in the new environment and have completed at least one successful run.
    • Log directory is writable and rotatable.
    • Alert channels are operational.

    7. Rollback Plan

    • Old server retained and accessible.
    • Original DNS values recorded.
    • Rollback trigger conditions clearly defined (e.g., error rate exceeding threshold).
    • Rollback owner identified.

    Day-of-Switch Sequence

    1. Run core page checks once more.
    2. Switch DNS resolution.
    3. Verify across multiple networks after 5 minutes.
    4. Monitor error logs for 1 hour.
    5. Notify relevant parties upon confirmation.

    24-Hour Post-Switch Observation

    • New entries in error logs.
    • Form submission volume within normal range.
    • No spike in 5xx responses from search crawlers.
    • No unusual reports via user feedback channels.

    Common Oversights

    • Only checking the homepage without verifying deep pages.
    • Forgetting to migrate the upload directory, resulting in broken images (404s).
    • Neglecting to set up backups on the new environment.
    • Overlooking monitoring updates, leaving incidents undetected.

    Scope

    This checklist ensures “no critical failures during cutover”; it does not guarantee “identical user experience.” If templates or site structure are also changing, a separate content comparison is required.

    Related Reading: