Development
How to Migrate a Membership Site Without Losing Access Rules

Migrate a membership site without losing access rules by treating entitlements as the primary contract. Map who can access each protected capability, why they have access, and how that access changes before moving users or content.
A successful user import does not prove that a paying customer can still download a file, enter a course, renew a subscription, or recover access after a failed payment.
Map membership access rules before choosing import fields
Create a sanitized sample covering active, cancelled-but-paid-through, expired, trial, paused, refunded, gifted, and manually granted access where those states exist. Separate billing state from entitlement state. A cancelled renewal can still leave access valid until the paid-through date.
For each product or plan, record:
| Item | Question to resolve |
|---|---|
| Entitlement | What capability does this purchase grant? |
| Start and end | Which timestamps and timezone govern access? |
| Billing identity | Which provider object owns recurring charges? |
| Exceptions | What manual grants or overrides exist? |
| Revocation | Which event removes access, and when? |
These are discovery questions, not guarantees that two membership products support equivalent features. Verify the exact source and destination versions and their supported migration paths.
Build an explicit mapping table
Give every source plan and access rule a destination decision. Document rules that cannot be translated directly, rather than quietly collapsing them into the nearest tier.
Include content-level restrictions, files, API access, course enrollment, community groups, and integration side effects. A page can be protected while its attached download remains publicly accessible. The WishList Member file-protection guide illustrates that separate boundary.
If a rule depends on purchase history or a custom integration, inventory the code implementing it. Labels in an administration screen may not expose the complete behavior.
Preserve billing identities deliberately
Inventory payment providers, merchant accounts, subscription identifiers, webhook destinations, renewal dates, and who is responsible for each recurring charge after cutover.
Do not create replacement subscriptions until you know whether the existing provider objects can continue and whether the destination can associate them with the migrated accounts. Otherwise a migration can produce duplicate charges or lost renewals.
Stripe's subscription webhook documentation is one provider-specific reference for lifecycle events. Other providers have different contracts. Verify the actual integration instead of translating event names by intuition.
Rehearse with representative customer journeys
Restore a sanitized copy into an isolated environment. Disable real emails, payment side effects, and third-party automations. The safe Lando cloning workflow provides a practical foundation.
For each sample account, compare access before and after migration. Attempt permitted and forbidden pages, direct download URLs, course entry, account management, and renewal-related transitions. Record expected outcomes and actual evidence.
Reconcile account totals, active entitlement totals, plan mappings, expiration values, and unresolved records. Totals help find omissions, but matching totals do not prove that the same customers have the right access.
Make the cutover reversible
Define a write freeze or a bounded delta synchronization process. Establish which system owns new purchases, refunds, and manual access changes during the transition. A migration with two uncontrolled writers is difficult to reconcile.
Record a cutover checkpoint, backups, routing changes, webhook changes, and rollback criteria. Explain what happens to writes accepted after the checkpoint. Restoring an old database can discard valid transactions unless the plan captures them.
After cutover, monitor access denials, renewal failures, duplicate events, support requests, and reconciliation differences. Keep the old system available only under the access controls required for the agreed transition.
Can I migrate membership users with a CSV alone?
A CSV can move supported fields, but it does not automatically move billing control, password compatibility, access logic, files, integrations, or renewal behavior. Verify each contract separately.
For a migration involving custom access rules or recurring payments, scope the entitlement and billing review first.