Inventory the records that keep changing
This is an editorial planning checklist, not evidence of a completed migration. List the course and membership plugins, payment integrations, scheduled jobs, email delivery, media storage, and any mobile app. For each, record its owner and the destination verification task.
Separate public content from changing records such as learner progress, quiz results, memberships, and orders. Ask the migration provider how the final synchronization handles these records. Do not assume that a homepage copy includes every external integration or that a second database import can safely merge all changes.
Rehearse without creating live side effects
Use synthetic students and payment sandbox facilities in an isolated destination rehearsal. Confirm with the implementer how outbound mail, scheduled billing, and live webhooks are disabled or redirected for the test. A copied site must not accidentally send class announcements or process real charges.
Verify login, access to an entitled course, rejection of an unentitled account, progress saving, quiz results, and the relevant sandbox purchase flow. Reapply and check the cache configuration for the destination environment. MemberPress publishes environment-specific instructions; copying files does not prove those rules are active on a new host.
Choose the cutover method explicitly
| Decision | Record before the move |
|---|---|
| New student activity | A maintenance window or an implementer-approved final synchronization method. |
| Payment events | Which endpoint receives events and who reconciles them during the transition. |
| Final copy | The last synchronized timestamp and verification evidence. |
| Go or no-go | Named owner and agreed access, data, and operational checks. |
| Rollback | How new destination records are preserved and reconciled before returning traffic. |
Verify the course before retiring the old host
Repeat the agreed student tasks on the live destination after cutover, using an appropriate controlled verification plan. Check that the latest pre-cutover records exist and that new work saves where expected. Have the responsible person confirm payment and email operation without relying only on a successful page load.
Keep the old environment and backups available for the agreed recovery period, but ensure old jobs do not continue operating unexpectedly. Retire it only after the data reconciliation and operational checks pass. The worksheet provides blank fields for evidence and owners; it does not automate copying, billing, or rollback.
Questions before you decide
Can students keep using the course during migration?
Only with a deliberately supported synchronization and cutover plan. Otherwise agree a maintenance window with the implementer; do not assume a one-time copy captures later student work.
Is changing DNS back enough to roll back?
Not if new progress, memberships, or orders were written at the destination. Preserve and reconcile those changes as part of the rollback decision.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- MemberPress: caching configuration for the destination Accessed 2026-09-13
- MemberPress: hosting considerations Accessed 2026-09-13
- Original local WordPress restore: incomplete restore failure and recovery checks Accessed 2026-09-14
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.