> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wegive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What Gets Migrated vs. What Needs a Separate Import in a Platform Migration

> When your organization migrates recurring donors into WeGive from another platform, the migration brings over active recurring plans and payment methods — but historical giving records from your previous platform need a separate data import to appear in WeGive.

## Overview

When your organization switches to WeGive from another giving platform,
recurring donors are typically migrated using a process called a
token-transfer migration. This migration moves the active pieces that
keep recurring giving running — the plans themselves and the payment
methods attached to them — so that donations continue on schedule
without donors needing to re-enter their information.

However, historical transaction records (past gifts, previous charges
on a recurring plan, one-time donations) from your old platform are
**not** part of this migration. If you need that history visible in
WeGive, it requires a separate data import step.

## What the migration brings over

* **Recurring plans** — amount, schedule, fund designation, and next
  billing date
* **Payment methods** — the card or bank account attached to each plan,
  securely transferred so charges continue without interruption
* **Donor and user accounts** — matched or created so the payment
  method and plan are properly linked

After the migration, recurring gifts will process on their next
scheduled date through WeGive. From that point forward, every charge
creates a new transaction record in WeGive automatically.

## What you will not see after the migration alone

* **Past transactions from your previous platform** — the individual
  giving records that existed before the migration do not transfer
  automatically. A donor's giving history in WeGive will start from
  the first charge processed through WeGive, not from when they
  originally started giving on your old platform.

## How to bring historical giving records into WeGive

If your organization wants a complete giving history in WeGive, you
can import past transactions using the **Import Wizard**:

1. Export your historical transaction data from your previous platform
   as a CSV file. At minimum you will need a donor identifier (such
   as email address), the gift amount, and the date of each
   transaction.
2. In WeGive, go to **Settings → Import** and choose the **Donation**
   import type with the **Insert** action.
3. Upload your CSV and use the mapping step to match your columns to
   WeGive's fields.
4. Review the preview and confirm the import.

Once complete, those historical transactions will appear in donor
records and reports in WeGive alongside any new gifts processed after
the migration.

<Tip>
  If you plan to import historical transactions, consider doing it
  **before** or shortly after the migration so your reports reflect the
  full picture from the start. Disabling triggered messages before a
  large historical import prevents donors from receiving unexpected
  notifications — see [Disable Triggered Messages Before a Data Import](/external/support/communications/disable-triggered-messages-before-a-data-import).
</Tip>

## Related

* [Why Your Activity Log Shows New Payment-Info Edits After a Platform Migration](/external/support/giving/why-your-activity-log-shows-new-payment-info-after-a-platform-migration)
* [Importing Existing Supporters](/external/support/settings/importing-existing-supporters)
* [Disable Triggered Messages Before a Data Import](/external/support/communications/disable-triggered-messages-before-a-data-import)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.