Make sure your fundraising export keeps the records connected

A nonprofit CRM data export passes only when your team can use the files without reopening the source platform. Download a representative slice, then prove that you can identify donors, gifts, recurring plans, and the relationships among them. Treat every missing link or unexplained total as an open portability defect.

That test is worth running before a renewal, integration project, or migration creates a deadline. A nonprofit technology guide calls data extraction critical for backup or migration, but the useful question is not whether an Export button exists. It is whether the result preserves the fundraising work your team depends on.

Start with a record inventory

Write down the records you expect before you click Export. Your list will depend on how your organization fundraises, but it may include:

• people, households, and organizations;
• gifts, payment states, funds, campaigns, and appeals;
• recurring plans and the gifts produced by them;
• communication preferences, activities, notes, and custom fields; and
• relationships such as household membership, organizational affiliation, or gift attribution.

Current platforms package those records differently. Fundraise Up documents separate donation, recurring-plan, and supporter exports, with selectable fields and one-time or scheduled delivery. Give Lively documents multiple donor-data export paths, including a report with a default three-month date range. DonorDock says its exports can include donors, gifts, tags, and activity timelines.

Those examples are not a universal checklist. They show why your export log should record the selected object, fields, filters, date range, time zone, file format, and export time. Otherwise, an apparently complete file can simply be a narrow view whose limits were forgotten.

Preserve the keys that connect files

Readable names are useful to a person. Stable identifiers are what let two files agree.

Before changing headers or opening the files in a cleanup tool, make an untouched copy of the export. Then find the identifiers for each donor, gift, recurring plan, organization, and source transaction. Check which identifier appears in both sides of every relationship.

For example, a gift row might contain a donor ID and a recurring-plan ID. The donor file should contain that donor ID, and the recurring file should contain that plan ID. If the export replaces those links with names alone, two people named Maria Garcia or two similarly named campaigns can no longer be joined safely.

This is also the boundary between an export drill and an import. The drill asks whether the source records retain their identity outside the platform. A later donation import control decides how a destination should accept those records without creating duplicate gifts.

Test exceptions instead of random rows

A random sample is likely to find the simplest records. Choose a small set that exercises the relationships your team would regret losing:

1. A donor with several gifts across more than one campaign.
2. An active recurring plan with at least one related gift.
3. A refunded, failed, or otherwise nonstandard payment state.
4. A person linked to a household or organization.
5. An imported gift that carries an external source or transaction identifier.

For each case, start with the source-platform record and trace it through the exported files. Confirm that you can answer: Who owns the gift? What happened to the payment? Which plan, campaign, fund, or source is connected? What information is missing, and was that omission intentional?

One nonprofit operator described spending a day or more each month reshaping third-party files because record types were mixed or needed fields were absent. Another nonprofit buyer asked about lock-in before adopting a CRM. These discussions are qualitative, not proof that every nonprofit has the same problem. They do show why a real exception is more informative than a clean five-row preview.

Give the drill an explicit result

Do not mark the export “done” because the files opened. Use one of three outcomes:

• Pass: Every sampled record can be identified, joined, and explained. Relevant totals match the source for the same recorded scope.
• Limited: The necessary facts exist, but a field map, join note, or additional export is required. Record the workaround and retest it.
• Fail: A material record or relationship is absent, identifiers are ambiguous, or the same filters cannot reproduce the source scope. Keep the defect open.

Store the export log, untouched files, field map, sample IDs, result, and test date together in an access-controlled location chosen by your organization. Name one owner and a retest date. The drill is most useful when the next operator can reproduce it without relying on the person who configured the CRM.

Know what this test does not prove

An export drill is not a complete backup, security review, records-retention policy, or migration rehearsal. It does not prove that attachments, credentials, automations, or stored payment methods can move. Ask the vendor and any destination provider about those items rather than inferring them from a CSV.

Once the drill passes, use the minimum viable fundraising software migration to decide what must work on day one. If the export will feed reporting instead, define the source and time window with the same care described in the fundraising dashboard metric contract.