Views:


GOsupport Logo

 

 

Revised 4/17/26

 

 

Prerequisites


Data Validation Checklist 
 

Purpose 

 

This checklist helps confirm that your data from your previous system (such as FIMS, Blackbaud, or Excel) was migrated accurately into akoyaGO. You do not need to review every record. Instead, validate counts, totals, and representative samples that you know well. 

 

Review of your data is required before data validation sign-off. Note - the list below is not inclusive of custom fields and tables unique to your organization. Please reference your Data Map to verify mapping of converted records and your Data Validation Worksheet to compare counts and totals from your previous system(s) to akoyaGO.

 

 

Organizations (Constituents) & Individuals (Contacts) 

 

 

Please verify:

  • Names display correctly (organizations and individuals)

  • Addresses, emails, and phones are populated appropriately

  • Individuals link to the correct organization (parent constituent), where applicable

  • Organizations link to the correct primary contact

  • Custom fields match the data map. 

 

How to check: 

  • Compare totals: # of organizations and # of individuals/contacts (optionally by type/status). 

  • Spot-check key + random records (names, salutations, key fields). 

  • Review missing contact info (blank address/email/phone) vs. legacy. 

  • Validate links: individual ↔ organization and organization ↔ primary contact. 

  • Scan for likely duplicates and confirm merge/dedupe approach. 

 

Connections (Affiliations/Relationships) 

 

Please verify:

  • Connections/affiliations link to the correct constituents. 

  • Role types are correct (e.g., Board/Trustee, Committee, Officer, Staff Liaison, Employee/Employer, Volunteer, Advisor, Family, Grant/Billing/Primary Contact). 

  • Direction/reciprocity is correct where expected. 

  • Dates/status are correct for time-bound relationships. 

  • Primary flags and notes/custom fields match the data map. 

 

How to check: 

    • Compare connection counts overall and by key role type. 

    • Spot-check known people/orgs to confirm roles, dates, and linked records. 

    • Verify org contacts (primary/billing/grant) against legacy. 

    • Check both sides display correctly for reciprocal relationships. 

    • Review edge cases (multi-role, multi-employer, inactive/history, duplicates

  •  

Distributions (Requests & Payments/Requirements)  

 

Please verify: 

  •  

  • Grant/scholarship amounts and dates are accurate 

  • Applicant vs. payee is correct 

  • Fund/designation (+ accounting) is correct 

  • Status and program coding are accurate 

  • Payments/requirements reflect multi-payment disbursements 

  • Interfund transfers: receiving fund is correct 

  •  

How to check: 

  • Compare transactions to the legacy system. 

  • Spot-check recent distribution amounts and dates. 

  •  

ShapeCommittees 

 

Please verify: 

  • Committee names/types/descriptions match legacy. 

  • Status and dates (active/inactive, start/end, term structure) are accurate. 

  • Memberships link to the correct constituents. 

  • Roles/leadership and term dates are accurate. 

  •  

How to check: 

  • Compare committee and roster counts to legacy (focus on key committees). 

  • Spot-check rosters for roles and term dates. 

  • Verify memberships from the constituent record view. 

  • Check edge cases (multi-committee, role changes, former members). 

  •  

Programs 

 

Please verify: 

  • Program names/codes/descriptions match the data map. 

  • Programs link correctly to related records (grants/requests/payments/requirements and/or gifts, as used). 

 

How to check: 

  • Compare service area/program counts to legacy (include inactive if migrated). 

  • Run a simple summary by program and compare to legacy totals (where possible). 

  • Check exceptions (missing picklist values, duplicates, miscoded records). 

 

 

 

akoyaGO + Accounting Only  

  

 

Gifts & Gift Payments

 

Please verify: 

  • Totals match legacy: gift count/amount and payments received (same date range). 

  • Gift crediting/coding is correct (donor, date, type, fund/designation, campaign/appeal, soft credit). 

  • Payments are complete and accurate (date, amount, method, batch/deposit). 

  • Pledges are correct (amount, schedule, paid-to-date, balance; payments applied correctly). 

  • No unintended duplicates; unapplied payments/credits are intentional. 

 

How to check: 

  • Compare totals: gift count/amount and payments received (same filters). 

  • Spot-check a mix of gifts (high-dollar, recent, recurring, complex types). 

  • Validate pledges end-to-end (schedule, applied payments, balances). 

  • Review exceptions (missing/unapplied payments, duplicates, mismatched pledge status). 

 

Donors & Prospects 

 

Please verify: 

  • Donor/prospect records link to the correct constituent/primary contact. 

  • Gifts/pledges/payments credit to the correct donor/prospect (and constituent). 

  • Soft/recognition credit and household rollups are correct (if used). 

  • Giving summary fields (if stored) match the underlying gift/payment history. 

  • Donor/prospect codes (solicitation, comm prefs, DNC, etc.) match the data map. 

 

How to check: 

  • Spot-check top donors: compare giving totals, then drill into gifts/payments for correct attribution. 

  • Test org vs. individual crediting on a small sample of gifts. 

  • Check pledges end-to-end (linked donor, applied payments, balances). 

  • Verify a few known soft-credit examples and confirm rollups. 

  • Run exceptions: zero-giving donors, gifts missing donors, miscoded gifts, duplicates splitting history. 

 

 

Funds 

 

Please verify: 

  • Fund designation is correct (Fund Type, Fund Class, Endowed checkbox)

  • Active funds have DT Accounts assigned

  • Fund list totals match expected number based on statuses/designations

  • Fund data reflects data map for fields like Established, Date Retired, etc.

  • Fund History reflects contributions and disbursements accurately

  • Fund Net Assets totals (balances from ledger) match expected value 

 

How to check: 

  • Review list of funds in akoyaGO 

  • Spot check handful of fund history and compare to legacy system