> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/get-started/apply-for-an-account/migrate-donors-to-anedot.md). # Migrate Donors to Anedot How to migrate recurring donors to Anedot using a CSV of commitment data and a secure payment method file from your previous processor. How to migrate recurring donors to Anedot using a CSV of commitment data and a secure payment method file from your previous processor. Anedot can recreate commitments so recurring donations continue. {% hint style="info" %} Migration typically takes **one to three months**, depending on your previous processor's responsiveness and procedures. After migration completes, cancel recurring donations with your previous provider. {% endhint %} ## Migration Fee Policy There is a **one-time fee of $500** for migrating commitments totaling **less than $5,000 per month**. Examples: * 100 commitments of $50 each * 10 commitments of $500 each The fee is debited from your account once migration is complete. When monthly commitment volume is high enough, there is **no migration fee**. Anedot charges the **$500** fee only for volumes **under $5,000/month**; organizations with higher monthly commitment volume should confirm fee waiver details with [Support](https://www.anedot.com/getsupport) when starting a migration. ## Limitations Anedot cannot migrate: * Commitments under **$10** * Commitments with an **expired** payment method * Commitments using **PayPal, Apple Pay, or Google Pay** (see [Switching from PayPal / Google Pay / Apple Pay](#switching-from-paypalgoogle-payapple-pay-to-anedot)) ## Getting Started ### 1. Notify Anedot * Visit [anedot.com/getsupport](https://www.anedot.com/getsupport) and say you plan to migrate recurring donors * Include the number of commitments * If available, include the URL of the donation page on your other processor * Anedot follows up with detailed steps ### 2. Notify Your Previous Payment Processor * Tell your previous payment processor you are moving commitments to Anedot * Your payment processor may differ from your previous fundraising platform; the platform can confirm the processor and contact info * Your previous payment processor must contact Anedot at **** * If needed, Anedot provides a PGP encryption key and PCI Attestation Letter * The previous processor must create an **SFTP** account to upload the payment method file securely ### 3. Prepare Your Commitment Data Gather: * A list of all [**Funds**](/settings/finance/funds.md) from your previous processor (fund designations or programs tied to commitments) * Anedot's **CSV template** filled with current donor commitment information **Important** * The CSV template is required * Do **not** change column headers * Include all data you have * Add extra data as new columns at the end of the CSV ## What To Expect * Migrations can take a few months; following the steps helps keep the timeline short * A designated Anedot contact keeps you informed * When Anedot receives the payment method file and your CSV, engineers match payment methods to CSV records to create commitments (typically a few weeks) * When complete, Anedot notifies you to **stop billing** on the previous processor; Anedot processes on the next scheduled date * New commitment records appear under **Finance →** [**Commitments**](/finance/management-and-reporting/commitments.md) ## Switching From PayPal / Google Pay / Apple Pay to Anedot Anedot cannot migrate recurring donations processed through PayPal, Google Pay, or Apple Pay. Those commitments must be **canceled and recreated by the donor** in Anedot. PayPal, Venmo, Google Pay, and Apple Pay remain available as built-in payment methods on Anedot accounts for **new** recurring donations. ### How To Transition Donors Ask donors to: 1. Cancel their existing recurring donation 2. Create a new recurring donation on your Anedot Donation Page ### Steps For Donors to Cancel PayPal Commitments 1. Log in to PayPal 2. Click **Settings** 3. Select **Payments** 4. Click **Manage pre-approved payments** 5. Select the donation and click **Cancel** or **Cancel automatic billing** 6. Direct them to your Anedot Donation Page to set amount, frequency, and payment method Encourage donors to create a Donor Account / DonorID so they can manage recurring gifts: [What Is a Donor Account or DonorID?](/donor-support/getting-started/what-is-a-donor-account-or-donorid.md) ## Related * [Commitments](/finance/management-and-reporting/commitments.md) * [Funds](/settings/finance/funds.md) * [What Is a Donor Account or DonorID?](/donor-support/getting-started/what-is-a-donor-account-or-donorid.md) * [Manage Recurring Gifts](/donor-support/manage-giving/manage-recurring-gifts.md) * [Payment Methods](/get-started/anedot-101/payment-methods.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.anedot.com/get-started/apply-for-an-account/migrate-donors-to-anedot.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.