Sell Coaching Memberships Without MemberPress: A Guide

You can sell coaching memberships without MemberPress by connecting a clearly defined recurring service to payment, member access and dependable delivery. If you already have paying members, the harder question is how to preserve what they bought while establishing a new billing arrangement without duplicate charges.

Coachful is our #1 recommendation when the membership centers on coaching resources, ongoing Programs and supported group sessions. This guide follows a small, complete transition: four prepaid members receive the access already owed, two choose new recurring payments and a separate lifetime Course entitlement survives membership ending. The example uses deliberate checks rather than assuming a member export moves subscriptions or permissions.

Decide which part of the WordPress operation to replace

MemberPress is a WordPress membership system. Its current documentation distinguishes membership products, recurring subscriptions and one-time subscriptions. A member can hold more than one subscription, and a one-time purchase can have lifetime access. Those business meanings matter more than copying a list of names into another platform.

You may keep the public WordPress website while moving the member experience to Coachful. Alternatively, you may replace more of the site. Identify the work actually required: member login, protected content, payments, live events, historical evidence and public links. Do not dismantle a functioning site simply because a different member portal is ready.

Make a requirements table with the current arrangement, intended destination and a pass condition. “Member can open the material they bought” is a useful pass condition. “Imported successfully” is incomplete if the person cannot sign in, a subscription still bills elsewhere or a separate purchase has disappeared.

A larger practice with complex gateways, tax arrangements, licensed content or many historical offers may need specialist migration work. The small case below is intentionally bounded. Its lack of old recurring subscriptions is a verified starting condition, not an assumption that recurring subscriptions transfer automatically.

Write a membership promise before building checkout

Separate the continuing service from the content already owned. A monthly discussion group with a few written resources is different from an unlimited private coaching relationship. Explain the actual frequency, formats, channels, response allowance and ending before asking someone to authorize recurring payment.

For applicable UK consumer arrangements, the CMA's current fair-contract guidance emphasizes transparent wording, prominent significant terms and avoiding hidden conditions that undercut what was advertised. Its guide was updated in July 2026. Your terms also need the requirements relevant to your own jurisdiction and transaction; this example is not a complete legal policy.

Existing purchases need their original terms respected. Changing a platform does not by itself permit a new price, reduced access or a switch from a one-time purchase to recurring billing. Resolve proposed changes openly rather than burying them in the new portal's welcome page.

Build a register that separates people, money and rights

Use one row per relevant entitlement or subscription, linked to the person. One person may need several rows. Useful fields are identity, product, original terms, payment reference, paid-through date, future billing state, promised content, destination access and unresolved exception.

MemberPress's current Members page documentation distinguishes exports of displayed records from the full table export. Check the actual export scope, filters and count. A CSV of member details is not a migration of card authorization, course progress, content rights or historical transaction evidence.

Export and secure only the information needed for the transition and applicable records obligations. Reconcile membership, transaction and subscription information rather than deciding from a single active/inactive label. Preserve original receipts and terms in their authoritative records; do not recreate old money as a new sale.

Before changing access, inspect exceptions individually: prepaid periods, canceled subscriptions with time remaining, failed payments, founding arrangements and separate lifetime purchases. If the records disagree, put that entitlement on hold for investigation while maintaining an appropriate continuity arrangement. Do not resolve uncertainty by charging again.

Complete fictional case: four prepaid members

Bea runs a small membership called Planning Practice. Asa, Brin, Chen and Dove each paid £30 for November access through MemberPress as a one-time purchase. None has automatic renewal. Bea also owes Dove access to a separately purchased lifetime reference Course. All names, amounts, records and events below are invented; these are not current Coachful prices or customer results.

Bea checks the four original transaction records, their end dates and the payment provider. All four membership periods run through 30 November 2026, with no future recurring charge scheduled. Dove's Course is a different purchase. Bea confirms these facts rather than treating a blank rebilling field as sufficient evidence.

Bea will keep the public WordPress site but use Coachful for the membership. All four agree to the described portal transition with the same November service and a private help route. Accepting that transition is not approval for a new subscription.

Configure the real service and bridge the paid period

Bea creates an ongoing independently timed Program for Planning Practice, with its normal recurring price set to the illustrative £30 per month. The service includes one 60-minute group question session each month and a small collection of written planning material inside the Program. Individual document review and private coaching appointments are not included.

In Sessions, Bea schedules the group call for eligible Program members. Independently timed individual Programs can share group calls without becoming a fixed cohort. A Program enrollment, a client group and a particular event registration are different records, so she checks the actual call audience rather than relying on matching names.

For November's obligation, Bea deliberately enrolls the four existing client accounts using free access. This is a nonbilling bridge because the service was paid elsewhere. She records the original paid-through date in the migration register and schedules a human end-of-period check. A free grant does not automatically expire on the date typed in an administrative note.

She places member-only material in the intended Program context and verifies its actual access. Dove's reference Course receives a separate direct grant with no expiry, preserving the existing purchase terms. It is not bundled into a new monthly obligation or dependent solely on the Program.

The Coachful features overview helps map these jobs to the platform. If you use an Offer to package other resources, configure actual What they get inclusions. Descriptive benefits alone do not grant a resource. Publishing a paid Offer also requires the necessary payout setup; a saved draft is not a working checkout.

Test the migration with an actual exception

Bea prepares a small register of checks: account accepted, Program opens, written material opens, group call is available to the intended audience and the member knows where to ask for help. She invites each person to confirm their own route instead of claiming a coach preview proves the member's access.

The first three members can reach the intended material. Dove cannot open the reference Course. Bea had copied its private link into the welcome message but had not completed the independent assignment. The link was not an access grant. She assigns the Course to Dove, saves and checks the actual grant. Dove then opens it directly and confirms access.

That failed first check remains in the migration record. Bea does not mark all four people migrated merely because four invitations were sent. Once the correction is verified, all four have the November membership route and Dove also has the separate Course route. No historical lesson completion or attendance is manufactured.

Completed member notice: Your November membership was paid through the previous site and is available here through 30 November. You do not need to pay again for that period. For account or access help, send Bea a one-to-one message in Coachful Messages. Bea checks that route Monday to Friday and replies within two working days, Europe/London. Any monthly continuation from 1 December requires a separate choice and payment approval. Dove's separate Course purchase keeps its existing access terms.

Bea sends the appropriate individualized notice in each person's one-to-one conversation. It is an administrative route, not unlimited private coaching. The group question session is the included coaching channel; nobody is required to post billing details publicly.

Create recurring payment requests only for members who choose them

Asa and Brin choose to continue. Because they already have the Program, Bea uses the released existing-enrollment workflow rather than creating duplicate enrollments or pretending the old one-time payments were subscriptions:

1. Open Clients, choose the joined client, then Billing. In Simple Mode, reveal Billing through More options. Open Recurring payments and choose Start recurring payments or the plus control.
2. Select the existing Program and Program price. Bea checks the saved £30 monthly amount and currency. A custom client price is a separate option; it must not silently rewrite the reusable Program price.
3. Choose First payment: On a date, 1 December 2026. This preserves free access until then. Choose payments continuing until stopped and If payments stop: Pause access. No setup fee is added.
4. Review Today, Then, Until and If payments stop. Create the request and send the secure link deliberately. Creating it does not charge or change access.
5. Have the client sign in, inspect the same terms and approve with their own card through the hosted payment page. Verify the resulting status; sending a link is not approval or payment.

The workflow requires an app account, a connected Stripe account under Payments and the appropriate Payments permission. The resulting subscription attaches to the existing Program enrollment. Do not describe a WordPress contact export as the source of that authorization.

For a new member without existing access, use the paid Program's normal published registration and checkout, with the actual recurring price and terms visible. Verify the resulting payment and enrollment. The free bridge in this case serves an already-paid obligation; it is not a required extra step for every future buyer. Do not also start a second recurring payment request for a purchase that already established billing.

Asa approves on 25 November and Brin on 26 November. Both requests show the dated start, and Bea verifies that no December membership money is collected at approval. On 1 December, each first £30 payment actually succeeds; the receipts appear in the member's Billing records and the Program remains accessible. These are observed fictional case events, not a claim that a payment always succeeds.

Chen and Dove receive no recurring request because they declined. Bea does not send a payment link repeatedly as though lack of approval were an error. All four still receive the full November service already owed.

Reconcile the period ending and the independent Course

The November group session is held on 18 November. The written materials remain available through the paid-through period. At the end of 30 November, Bea checks that no November live service or individual feedback promise remains outstanding; the membership never included a private reply allowance.

For Chen and Dove, Bea uses the Program's Remove from program action to stop their nonbilling enrollments. She understands that this also affects Program-related participation and future work; it is not a billing cancellation or an account deletion. She checks their access after the change rather than assuming it from the menu confirmation.

Dove receives a confirmation that distinguishes the ended membership from the continuing Course. “You no longer have membership access” would be incomplete if it made the person think their separate purchase had ended. Bea preserves the original Course terms and the grant evidence in the record.

The practice now has four client accounts, two paying recurring members and one additional person with a separate paid-course entitlement. Those are different counts. Reporting all four accounts as active paying members would misrepresent the transition.

Close the old membership operation only after the checks

Bea turns off the old membership purchase routes and replaces the public member-login directions with the new route. She preserves a secure archive of the relevant terms, original receipts and transition evidence. Member-facing protected material has been recreated from her own authored work; no third-party content permission is assumed to transfer.

Before disabling the MemberPress member area, she rechecks all four destination accounts and Dove's independent Course. She unpublishes the old member-only pages and removes the retired download routes, keeping the needed records in a restricted archive. Signed-out checks of the old addresses no longer serve protected material. Only then is the old area closed on 2 December. The public WordPress website stays in use. Members have the named help route, and Bea checks that old public buttons no longer send someone to buy an obsolete November membership.

This closure is possible because the old payment audit established no recurring subscriptions. MemberPress's own payment documentation warns that deleting the plugin, users or subscription records does not cancel processor subscriptions. If you have recurring billing, check and deliberately resolve it at the actual provider before retiring the system. A display label, deleted record or new portal invitation is not proof that future charges stopped.

For a contrasting fictional annual member whose access is prepaid through the following March, a November move needs continuity through March or another appropriate agreement. Starting a new monthly charge immediately would not become acceptable simply because others renewed on 1 December. Keep that exception in its own row rather than applying the small case's common end date to everyone.

Count migration work separately from the recurring service

Bea's monthly service plan allocates 60 minutes to the group call, 40 to preparation, 20 to follow-up and 30 to routine member administration: 150 minutes, or 2.5 hours. November's missing-Course repair takes another 15 minutes, making service and administration work 165 minutes.

The one-time move separately uses 90 minutes for records, 120 for recreating content, 60 for account and route checks and 30 for transition communications: 300 minutes, or five hours. The specific repair is additional to those planned checks. Total November work counted here is 465 minutes, or seven hours 45 minutes. It does not include every activity in the wider business.

The original November receipts total £120, four times £30, in the old financial record. The bridge creates no new revenue. December's two actual receipts total £60. Do not call the combined £180 December income or count the free grants as four new purchases. Processor fees, overhead, owner pay and tax remain separate from these gross receipts.

Before offering the continuation, Bea records what two members would mean for the service economics. At the planned 2.5 monthly hours, £60 is £24 gross per delivery-and-administration hour before costs. It is not a target wage or profit. The group call still takes an hour when only two people buy, so its workload does not halve with the revenue.

Bea explicitly chooses to run one December pilot at that small size, reserves up to three working hours and commits to the service before accepting the approvals. She will review future enrollment and pricing after delivering it. That review cannot silently raise Asa's or Brin's already accepted price or reduce their current service. No forecast of additional members is included in the £60 received.

At the 3 December operating review, Bea keeps the small service rather than expanding enrollment. The migration is complete for this defined four-person membership population, but the next renewal and December live session remain future events. A completed transition does not establish profitable recurring delivery or improved retention.

Handle the next billing event using its actual state

A request is still waiting: check whether the person wants it and whether the link is valid. Waiting requests can be copied, emailed again or canceled. Do not create parallel live requests for the same client and Program.

An approval payment fails: the existing-enrollment workflow can reopen the request and stop the failed processing subscription. Inspect that state before retrying; do not treat a redirect as captured money.

An established payment stops: apply the saved Pause access or Keep access policy and inspect the actual paid period and payment state. Under Pause access, progress is kept while access pauses at the relevant end or after an unresolved failure. Do not invent a universal grace period.

A member cancels: verify the saved end-of-period status and explain the paid-through access and separate purchases. Stop at end of period is not an automatic refund. For the fuller recurring-operation example, see the membership billing and access guide.

The old and new systems both show a charge: compare exact processor references and periods before acting. Stop the incorrect future billing through its real control and resolve any actual duplicate payment appropriately. Do not delete the evidence or mark a nonbilling grant as a refund.

The billing-record guide develops the distinction between the financial authority and client administration. Keep payment evidence, access grants, enrollment, attendance and support delivery connected without pretending they are the same record.

Frequently asked questions

Can I keep WordPress and stop using MemberPress?

Yes, if the remaining public site and member journey work without that plugin. Bea keeps the public website and moves member access. Check old purchase buttons, login directions, protected content and billing dependencies before closure.

Does exporting members move recurring billing?

No such transfer is assumed here. The example's old purchases are verified as one-time. New recurring payments require a separate supported arrangement and each member's approval; an export is not authorization.

Should I charge again to activate the new portal?

Preserve the paid service already owed. A deliberate nonbilling bridge can provide access while you reconcile existing terms. Do not create a new sale merely to make the destination look paid.

Can a membership ending remove a lifetime Course?

Do not remove an independent entitlement simply because membership ends. Map the actual rights and grants separately. Dove's Course is checked directly after the membership Program is stopped.

Is a waiting recurring request an active paid member?

No. Waiting, approval, captured payment and active access are distinct states. Use the actual saved records and receipt rather than counting sent links as paid subscriptions.

Will moving platforms improve retention?

The transition alone does not prove that. Measure the service people received and their later choices using clear definitions. Bea's next renewal and December session are still unobserved at the operating review.