Payment Migration Guide for Coaches and Course Creators
Moving your coaching or course business to a new platform? This payment migration guide covers what transfers, what to rebuild, and how to switch without double charges.
By the Hopper team

A payment migration moves your paying clients, their saved cards and their active subscriptions from your old platform's checkout to a new one, without anyone being charged twice or locked out. Saved customers and cards can usually travel. Subscriptions, plans, coupons and payment schedules usually have to be rebuilt. The whole job comes down to doing that rebuild in the right order and keeping your old account alive until the last refund and dispute is settled.
If you are leaving Kajabi, Circle, Skool, Teachable or a stack of separate tools, this is the part that keeps you up at night. Your members trust you with their card. A botched cutover is not a tech glitch to them, it is a surprise charge or a locked door. This guide walks through the process the way we would explain it to a friend, and shows where our free, done-with-you migration at Hopper takes the heavy lifting off your plate.
TL;DR
- Customers and saved payment methods can often be copied between processors. Subscriptions, products, prices, coupons and invoices generally cannot, so you recreate them.
- Inventory every client, plan, renewal date and amount before you touch anything. Keep each person's price and billing date exactly the same.
- Test in a sandbox, run old and new side by side, and move people in small waves, not all at once.
- Keep your old account open for refunds, disputes and reserves for weeks or months after the switch.
- At Hopper, migration and onboarding are free and done with you, so you are not doing this alone.
Table of Contents
- What a payment migration actually involves
- What transfers and what you rebuild
- Step 1: Inventory every paying person
- Step 2: Check the destination's payment setup
- Step 3: Rebuild products, prices and subscriptions
- Step 4: Handle payment plans and half-finished programmes
- Step 5: Test before anyone is charged
- Step 6: Tell your people first
- Step 7: Run both systems in parallel, then ramp
- Step 8: Watch closely, and keep the old account open
- What to keep for your records
- How Hopper makes the move lighter
- Our point of view
- FAQ
- Sources
What a payment migration actually involves
Most coaches picture a payment migration as one big export and import. It is closer to moving house with a very specific packing list. Stripe's own data migration overview describes a multi-step process: build the new payments integration for one-time and recurring payments, plan how to migrate data (starting with new customers), decide which payment details and methods to move, count your customer records, agree a timeline with your previous processor, remap subscriptions, design a way for customers to update their card, and then begin charging existing customers on the new setup.
For a coaching business there is another layer on top of that: the human one. Your payment data is tangled up with what each person is entitled to. One client is halfway through a six-month cohort. Another pays monthly for a membership and has a founding-member rate you promised years ago. Another bought a 1:1 package with three sessions left. A processor knows none of that. It only knows cards and charges.
That is why there is no universal one-weekend timeline. A solo coach with 40 monthly members and one price can move in days. A coach with six programmes, payment plans and a mix of PayPal and card clients needs a longer runway.

What transfers and what you rebuild
This is the question that decides your workload. The details depend on the processors involved, but the pattern is consistent.
| Item | Usually moves | Usually rebuilt |
|---|---|---|
| Customer records (name, email, ID) | Yes | |
| Saved cards, US ACH records, SEPA mandates | Yes, between eligible Stripe accounts | |
| Subscriptions | Yes | |
| Products and prices | Yes | |
| Coupons and discounts | Yes | |
| Invoices and charge history | Yes, or keep in the old account | |
| Apple Pay and Google Pay methods | Not in some processors' exports | Customer re-adds |
| Course access and progress | Mapped to the new platform |
Stripe's documentation on copying customer and payment method data between accounts confirms the first rows: Customer objects and associated payment methods such as cards, US ACH and SEPA mandates can be copied, while Charges, PaymentIntents, Invoices, Plans, Subscriptions and Coupons cannot. Customer IDs stay unchanged, and payment-method IDs are mapped through a CSV file.
The same page lists constraints worth knowing before you start:
- The copy is one-way. Data ends up in both accounts, and nothing is merged or moved out of the old one.
- The receiving account must be activated first.
- After copying, you confirm the new account is set up to accept the copied payment methods, then recreate subscriptions using the same plan IDs.
If you are coming from Braintree, the picture is similar. Its data migration documentation says customer and credit card records can be imported and exported, but subscription and transaction information cannot, so plans are recreated and subscriptions created afterward. Apple Pay and Google Pay methods are excluded from exports, and ACH payment methods require agreeing to additional legal terms.
The takeaway: expect your clients' cards to survive the move, and expect to recreate everything that describes what they are paying for.
Step 1: Inventory every paying person
Before any export, build one honest spreadsheet. One row per paying client:
- Name and email
- Which product or programme they bought
- Amount, currency and billing interval
- Next renewal date
- For payment plans: how many installments are left
- Which processor holds the card (Stripe, PayPal, something else)
- What they currently have access to
This looks tedious, and it is. It is also the single step that prevents most migration disasters. The mistakes people make here are small: forgetting the clients on PayPal, forgetting the old founding-member price, forgetting someone on a paused subscription. Each one becomes a support email later.
Where Hopper helps: our migration is done with you, not handed to you as a manual. We start from this same inventory of clients and what they have access to, so you are not holding the whole map in your head.
Step 2: Check the destination's payment setup
Before you move a single card, make sure the place you are moving to can actually take payments from your customers. Ask:
- Which payment processor does the new platform use, and who owns the merchant account?
- Does it support your country and the countries your clients pay from?
- Which currency do customers see, and which currency do you get paid in?
- How are refunds, chargebacks and payouts handled?
- Which payment methods do your clients use (cards, bank debits, wallets)?
Currency is the quiet trap. The price a client sees, the currency they are charged in and the currency you settle in can all be different. Decide these on purpose before cutover, not after the first confused email.
Because our clients are coaches and teachers all over the world, it helps that Hopper accepts creators in every country Stripe supports. If you can run a Stripe account where you live, you can run Hopper.
Also keep one thing separate in your mind: being able to take a payment is not the same as being legally ready to sell in a market. Local consumer rules, tax registration and data requirements are their own workstream, and your accountant or a local adviser is the right person for that, not your platform's support team.
Step 3: Rebuild products, prices and subscriptions
The new account needs its own products, prices, coupons and tax settings. Source IDs generally cannot be reused, so treat this as a clean build with a careful map from old to new.
A few rules that save pain:
- Keep prices and dates identical. If a member pays $49 on the 12th, they should pay $49 on the 12th. A changed amount or date is a new term in the customer's eyes, and the most common reason for a dispute.
- Do not restart trials on memberships you are moving. Existing members are not new members.
- Recreate each subscription so its first charge on the new system lands on the date the old one would have renewed, then end the old one. Ending the old subscription too early loses a renewal. Ending it too late double-charges.
- Document the exceptions. Grandfathered pricing, installment plans, coupons and PayPal agreements often cannot move cleanly. For each, decide whether to preserve it, recreate it with the client's consent, keep billing on the old system until it ends, or end it and invite the client to re-enroll.
Stripe's guide to migrating subscriptions describes the typical three stages: set up the billing integration, migrate customer and payment-processor information, then import subscriptions. It also notes that subscriptions can be imported from another billing system or another Stripe account with either a no-code toolkit or API scripts.
On Hopper, you set up your hubs, library, products and landing page in one place, so the product rebuild lives alongside the community and content it unlocks rather than across three tools. And our free migration covers the client and payment side with you, so you are not recreating every plan alone at midnight.
Step 4: Handle payment plans and half-finished programmes
The hardest case is the client halfway through an installment plan. The card can move, but the plan, the count and the original agreement do not. Recreate only the remaining installments, with the same dates and amounts, and keep the agreement the client originally accepted.
Similar care applies to 1:1 packages with sessions left and cohort programmes mid-run. Write down what each person is owed, and honor it in the new system before you announce anything. The goal is that no client notices anything except a nicer place to log in.
Never collect or transfer card details manually, by spreadsheet or by email. Cards move between processors through secure, processor-controlled channels. If a client has to retype a card, you ask them to do it on the new checkout, not by sending you the number.
Step 5: Test before anyone is charged
Treat your first week as a rehearsal. Stripe's guide to switching payment processors recommends integrating in a sandbox first to validate authorizations, refunds, webhooks and edge cases, and scheduling the cutover in a low-volume period.
A simple coach-sized test list:
- A successful purchase of each product
- A declined card
- An expired card
- A full refund and a partial refund
- A recurring charge on a test subscription
- A purchase in each currency you sell in
- A failed payment, and what it does to the buyer's access
That last item matters more than most people expect. Payments and access should be linked: a paid invoice opens the door, a failed one pauses it, and a recovered one reopens it. Test that loop before real members rely on it.
Step 6: Tell your people first
Your clients should hear about the change from you before they see it. Keep the message short and warm:
- What is changing, and the date
- That their price and billing date stay the same
- Where to log in, and that there is an app
- What, if anything, they need to do (often nothing, sometimes re-adding a card)
- Who to write to with questions
Move people in waves instead of all at once. Start with your most engaged members, who will forgive a rough edge and tell you what confused them. Keep the old tool read-only for a short overlap so nobody feels stranded.
This is where a community platform earns its keep. When your members land in a space that feels like a digital living room, with discussions, a library and a native app on their phone, the move reads as an upgrade rather than a paperwork exercise.
Step 7: Run both systems in parallel, then ramp
Do not flip every client on day one. Stripe recommends running both processors in parallel and ramping from a small share of transactions. Razorpay's migration checklist suggests starting at 10 to 20 percent of live traffic and scaling to 100 percent only when each tier is stable.

For a coach, "traffic" is simpler: new buyers go to the new checkout first. Existing members follow in waves, each timed to their renewal date, so no one is charged by both systems in the same cycle.
Step 8: Watch closely, and keep the old account open
After cutover, watch failed payments, declines, refunds and support emails. Fincoro's migration playbook suggests monitoring authorization rates, dispute rates and payment-related customer contacts for 30 days.
Then resist the urge to close the old account. Razorpay's checklist advises keeping the old account active for 30 to 60 days after full cutover for refunds, chargebacks and retries. Fincoro adds that many processors hold reserves for 90 to 180 days after closure, and recommends not closing until in-progress disputes are resolved and reserves released. Disputes on old sales go to the old processor, so it has to stay reachable.
A realistic calendar for a small coaching business looks like this:
| Phase | Typical length |
|---|---|
| Inventory and planning | A few days to two weeks |
| New account setup and review | Days to weeks, depending on the processor |
| Product rebuild and sandbox testing | About a week |
| Waves of member moves | One to two weeks |
| Monitoring | 30 days |
| Old account kept open for refunds and disputes | 30 to 180 days, depending on processor |
These are planning ranges, not promises. Your processor's own timeline governs.
What to keep for your records
Keep your own copy of the things a processor will not hand back: the agreements clients accepted, the terms they agreed to for installment plans, your refund policy as it stood when they bought, and a log of who moved when. Export your old transaction history before you close anything. If a dispute lands months later, you will want it. For tax and legal retention rules in your country or state, ask your accountant or lawyer.
How Hopper makes the move lighter
Hopper is an all-in-one home for coaches, healers and educators who already have paying clients: community, course and content library, async coaching, storefront and landing pages, and a native iOS and Android app for members, on one flat plan. Migration and onboarding are free and done with you.
Here is what it costs, as published on our site in 2026:
| Plan | Monthly | Annual |
|---|---|---|
| Base | $58 per month | $580 per year |
| Pro | $108 per month | $1,080 per year |
Both plans include unlimited hubs, members, team and products and the native app, and Pro carries 0% fees. If you are paying for a course tool, a community tool and a checkout tool separately, a payment migration is the best moment to consolidate, because you are rebuilding your products anyway. See the plans and start with a free trial at hopper.so.
We also built Sprout, an AI twin that answers students from your own lessons and escalates the rest, so a calmer inbox can be part of the move too.
Our point of view
I started Hopper because I watched coaches build something beautiful and then spend their energy keeping a Frankenstein of tools alive. One for courses, one for community, one for selling, one for the app. Each with its own bill, its own login and its own way of breaking.
The sneakiest part is that leaving is hard on purpose. Prices climb with contacts and features, a cut comes off every sale, and the thought of moving paying clients to a new checkout is frightening enough that people stay. We think that fear should not be a business model.
So we do the scary part with you. Migration and onboarding are free, done with you, and led by people who care whether your members feel at home. Our pricing is flat, so growing your tribe does not raise your bill. The lecture hall is closed. The playground is open.
A payment migration is just a promise kept: same price, same date, no surprises. Do it carefully and your members will barely notice, except that everything feels more alive.
Cedrik, Founder at Hopper.so
FAQ
Will my members have to re-enter their cards?
Often not, if the cards move between eligible accounts through the processor's secure transfer. Stripe's documentation says cards, US ACH records and SEPA mandates can be copied between accounts. Some methods, such as Apple Pay and Google Pay in Braintree's case, are excluded from exports, so a few members may need to add a card again.
Can I move my subscriptions as they are?
No, not as the same objects. Stripe's documentation says subscriptions, plans and coupons cannot be copied, so you recreate them in the new account. The key is matching each member's price and next billing date so nothing changes for them.
How do I avoid double charges?
Time each new subscription's first charge for the date the old one would have renewed, then end the old one. End it too early and you lose a renewal. End it too late and the member pays twice. Moving people in waves by renewal date makes this much easier to manage.
When can I close my old payment account?
Not right away. Keep it open for refunds, chargebacks and retries for at least 30 to 60 days, and until open disputes are resolved and any reserves are released. Some processors hold reserves for 90 to 180 days after closure, so check your processor's terms.
Does Hopper handle the payment migration for me?
Our migration and onboarding are free and done with you, and they cover moving your clients and payments. Start at hopper.so and we will plan it around your programmes and members.
Sources
- Stripe: data migrations overview
- Stripe: copy customer and payment method data across accounts
- Braintree: data migration overview
- Stripe: migrate subscriptions to Stripe Billing
- Stripe: how to switch payment processors
- Razorpay: payment processing migration checklist
- Fincoro: how to switch PSP without losing revenue
Recommended
On our list and want off? .
