Plan donor-record cleanup with a nonprofit virtual assistant

Donor databases collect years of small inconsistencies. One person appears under a personal email and a work email. A household record splits after an address change. An event spreadsheet uses a nickname that does not match the gift system. A virtual assistant can investigate and prepare corrections, but gift restrictions, receipting, tax treatment, and deletion decisions belong to authorized nonprofit staff. The cleanup should be reversible. Each proposed change needs the original record identifiers, evidence consulted, field-level choice, reason, reviewer, and rollback note. The goal is not a database that merely looks tidy. It is a record that staff can trust without losing the history behind a contribution.

Choose the authoritative source for each field

No single system wins every conflict. The gift ledger may control amount and receipt history. A constituent's direct request may control communication preference. A returned-mail record may show that an address is unusable without identifying a replacement. Write a field map that names the controlling source and the person allowed to approve exceptions. Ask the assistant to preserve source dates. A newer event registration does not automatically replace a donor's formal mailing preference. A payment processor name may reflect a cardholder rather than the person who should receive recognition. If the evidence does not establish the answer, keep the conflict open. Use stable donor and gift identifiers in the work queue. Names are search clues, not dependable keys. Two people can share a name, and one person can donate under several forms of a name. The assistant should never merge records solely because the text looks similar.

Preserve gift and acknowledgment history

Gift amount, date, fund, campaign, restriction, payment source, acknowledgment, and receipt records need an audit trail. The assistant may compare them and flag mismatches. Only authorized finance or development staff should change a designation, restriction, receipt, or tax-related field. The IRS explains that donors need records for charitable contributions and that written acknowledgments have requirements for certain contributions. A cleanup process should not detach an acknowledgment from the gift it documents or rewrite historical wording without review. Keep links between the transaction, receipt, correspondence, and any correction. Avoid copying financial data into the cleanup sheet. Record the minimum reference needed to locate the controlled transaction. Payment card details, bank information, identity documents, and sensitive notes do not belong in a general project board.

Investigate duplicates cautiously

Build a match packet rather than an automatic merge list. Include record IDs, names, verified contact points, household links, organization, gift history, creation dates, source systems, and conflicting fields. Explain why the pair was selected. Exact email matches may be strong evidence in one database and misleading in another where families share an address. Set clear no-merge conditions. Keep records separate when identity is uncertain, gift ownership conflicts, restrictions differ, confidential notes would cross access boundaries, or rollback is unavailable. A duplicate remaining open is safer than combining two donors and sending one person's history to another. For approved merges, identify the surviving record and the source for every retained field. Preserve the retired identifier as an alias when the system supports it. Test that gifts, acknowledgments, tasks, relationships, and preferences remain connected after the change.

Respect communication preferences

Treat unsubscribe, do-not-call, returned-mail, deceased, and channel-specific preference fields as controlled data. The assistant can locate evidence and prepare a proposed update. The designated owner approves ambiguous cases, especially when two systems disagree. Do not infer permission from a donation. A person may support the organization while declining marketing email. Likewise, a bounced address does not authorize substituting an address found on the public web. Record the failed channel and route the next step under the nonprofit's privacy and outreach rules. Household records need special care. One member's preference should not silently overwrite another member's choice. Define how salutations, recognition names, joint gifts, and separate contact permissions are handled before cleanup begins.

Work a realistic duplicate case

Suppose the database contains record 1842 for "Ana Reyes" with three gifts and mailed acknowledgments, and record 9170 for "Ana M. Reyes" created from a webinar registration. The records share a work email but have different home addresses. The newer record contains an email preference; the older record contains the gift history. The assistant creates a packet with both IDs, source dates, shared and conflicting fields, gift links, and the webinar registration. The assistant does not merge them. A development staff member confirms through an approved channel that they belong to the same person and approves the surviving record. After the merge, the assistant checks that all three gifts and acknowledgments remain linked, the confirmed preference is preserved, the retired ID resolves to the survivor, and no household relationship changed unexpectedly. The reviewer signs off on the result. If any link fails, the team uses the rollback plan before processing another pair.

Approve a migration sample

Begin with a representative sample: an exact duplicate, a household pair, a shared organizational email, a conflicting preference, a donor with restricted gifts, and a pair that should remain separate. Run proposed changes in a sandbox or export when possible. Review every field choice and test recovery. Count pairs reviewed, merges approved, no-merge decisions, unresolved conflicts, preferences corrected, reviewer changes, and rollback tests. State the sample size. Do not judge success by the number of records deleted; aggressive deletion can make the database smaller while making it less reliable. When errors appear, update the match rule or field map before expanding the batch. Add one source system or record type at a time. Keep high-risk records, restricted gifts, and sensitive relationships under full review even after routine duplicates become dependable. The IRS guidance on written acknowledgments for charitable contributions (https://www.irs.gov/charities-non-profits/charitable-organizations/charitable-contributions-written-acknowledgments) provides background for contribution records and acknowledgments. Apply the tax, privacy, fundraising, retention, and nonprofit rules relevant to your organization with qualified advisers. To scope a controlled cleanup project, review virtual assistant services (/services) or request a role plan (/contact). Bring a redacted pair of duplicate records, the field authority map, and the rollback procedure.