Adopt existing Stripe customers from a prior system

If your organization used another membership system with Stripe as the payment processor, your members’ saved cards are already stored in Stripe. This guide shows you how to link those existing Stripe records to your MapleGather members so they don’t need to re-enter their card details.

Who can do this: Admins with the billing:configure-processor permission (to list Stripe customers and run auto-match), billing:write (to apply matches), and billing:read-processor (to view the customer list). Typically all three are held by the primary admin.

Before you start

You must have Stripe connected to MapleGather first. See Connect Stripe and configure your payment processor.
Your members must already be imported into MapleGather before you run the match step.
This is a one-time migration step, typically done right after connecting Stripe.

Steps

Review your existing Stripe customers

In the admin sidebar, select Billing & payments, then select Migration, then select Adopt Stripe Customers.
MapleGather lists all Stripe Customer records found in your connected Stripe account. You can see each customer’s email address, their default payment method (card brand and last four digits), and their Stripe subscription status.
To find a specific customer, enter an email address in the Search by email field. To focus only on unmatched records, select Unmatched only.

Match customers to members

Select Match customers to members.
On the match screen, select Run auto-match. MapleGather compares Stripe Customer email addresses to your member email addresses and builds a draft match list. High-confidence matches (exact email) are pre-accepted. Lower-confidence matches are flagged for your review.
If any conflicts appear — a member email that matches more than one Stripe Customer — a conflict panel shows both records side by side. Review the created date, card, and subscription history for each, then select the one to keep. You must resolve all conflicts before you can apply the matches.
Review the draft match list and make any corrections. When you’re satisfied, select Apply matches.
MapleGather links each Stripe Customer to the matching member record. You’ll see a confirmation showing how many members were matched.

If your emails changed during migration: if most of your customers are unmatched because email addresses changed, use the CSV upload path. Select Upload a CSV instead and upload a file with the columns member_email,stripe_customer_id.

Create subscriptions against existing customers

After applying matches, create subscriptions for matched members as needed. If a member’s matched card is expired, MapleGather shows an inline notice — select Request card update to send that member a link to enter a new card before their subscription starts.

Verify

You’ll know it worked when the post-apply summary shows the number of members matched and PaymentMethod records created. You can reverse the matching within 48 hours from the Unified Undo panel.

If something goes wrong

Conflict — one member matches multiple Stripe Customers — see Duplicate Stripe customer match conflict.
“0 of N customers matched” — your Stripe Customer emails don’t match your member emails. Use the CSV upload path (select Upload a CSV instead) to provide a manual mapping.
“Another admin is running a match” — wait a moment and try again; only one match operation can run at a time.
A matched card is expired — select Request card update in the member’s record to send them a link to update their card before renewal.