Token Transfer Prerequisites

Last updated: February 2026

Overview

Before WeGive can begin migrating your recurring donation tokens from your current payment processor, a few things need to be in place. Completing these prerequisites upfront ensures a smooth migration and that your donors have a fully functional experience from day one — including the ability to manage their own recurring plans through the Donor Portal.

Estimated prep time: 1–2 weeks, depending on your data readiness

Note: Each of these prerequisites is covered in your onboarding project plan. Reference your project plan for detailed steps on how to complete each item.

Data Prerequisites

1. Donors Must Exist in WeGive

All donors tied to active recurring plans need to be in WeGive before the recurring plans import. Each recurring plan row requires a WeGive Donor ID, so donors must be created first. If your organization uses a CRM integration, ensure the integration is complete and donors have synced to WeGive before proceeding.

2. Designation Funds Must Exist in WeGive

Every recurring plan is tied to a designation fund. These funds need to be set up in WeGive so each plan can reference a WeGive Fund ID. If your organization uses a CRM integration, ensure designation funds have synced to WeGive before proceeding.

3. Campaigns Must Exist in WeGive

If your recurring plans are associated with campaigns, those campaigns need to exist in WeGive ahead of time. Each plan row requires a WeGive Campaign ID. If your organization uses a CRM integration, ensure campaigns have synced to WeGive before proceeding.

Platform Configuration

4. Payment Processor Must Be Connected

Your WeGive payment processor (e.g., Tilled, Stripe) needs to be fully configured and active before tokens can be migrated and transactions can be processed.

5. Default Checkout Must Be Live

A default checkout needs to be published and live in WeGive. This is the checkout that will be associated with your migrated recurring plans and is what donors will see if they update their giving through the Donor Portal.

6. Default Designation List Must Be Selected

A default designation list should be configured so that donors who access the Donor Portal can see the correct fund options when modifying their recurring plans.

7. Custom Domain Must Be Set Up

Your custom domain (e.g., give.yourorg.com) should be configured and verified. This domain is used for your checkout pages and the Donor Portal, giving donors a branded, trustworthy experience.

8. Donor Portal Must Be Enabled

The Donor Portal allows donors to log in and manage their own recurring plans — updating payment methods, changing amounts, or pausing donations. This should be enabled and tested before migrated plans go live so donors have self-service access from the start.

9. Email Templates Must Be Configured

Make sure the following email templates are set up and customized with your branding:

• Payment success emails — sent after each donation is successfully processed

• Payment failure / dunning emails — sent when a charge fails, prompting donors to update their payment method

• Recurring donation created emails — sent when a new recurring plan is created

• Payment processing emails — sent when a payment is being processed

• Tribute emails (optional) — sent when a donation is made in honor or memory of someone

These emails are essential for donor communication once recurring plans are active.

Ready to Start?

Once all items above are complete, you're ready to move on to the token transfer process. Your WeGive Implementation Coordinator will provide you with two additional guides:

Token Transfer Guide — The full process, timeline, and steps for your token transfer.

Questions?

Reach out to your WeGive Implementation Coordinator if you need help completing any of these prerequisites.