Explore Gratona by fundraising goal
Move from Bloomerang without losing the history behind the relationship.
Bloomerang exports many connected files, not one finished donor record. This checklist turns those files, the documented gaps, and recurring-donor continuity into an acceptance plan your organization can verify.
Reviewed and updated 2026-08-16
Separate exportability from continuity
A CSV can preserve historical facts. It does not prove that a relationship stayed connected, a recurring donor will be charged correctly, or a report will reconcile. Treat history, active billing, operational artifacts, and staff acceptance as four related but distinct workstreams.
Reconnect the files into one accountable record
Bloomerang's current CRM export documentation lists separate CSV files by data type. Preserve the original keys and reconcile each group before and after transformation.
| Data area | Source files | Migration decision |
|---|---|---|
| People and relationships | Constituents, addresses, emails, phones, households, relationships, relationship roles, users | Preserve source IDs and decide how households, organizations, contact points, ownership, and relationship direction map. |
| Giving and commitments | Transactions, donations, pledges, pledge payments, recurring donations, recurring payments, refunds, soft credits, tributes | Reconcile counts and totals separately from active billing credentials, schedules, settlements, and future charges. |
| Fundraising structure | Funds, campaigns, appeals, custom fields | Choose which source structures remain distinct, which become tags or fields, and which should be archived. |
| Relationship history | Interactions, notes, tasks, file attachments | Retain dates, authors, ownership, linked records, completion state, and the context staff need on the new timeline. |
| Payment context | Processing info, transaction processor accounts, wallet items | Treat these as processor and reconciliation evidence. Do not assume an ordinary export can reactivate stored payment methods. |
Require proof at every handoff
Step 1
Create the complete Bloomerang exit package
Generate the organization-level CRM export, record its date and owner, and separately export any Bloomerang Fundraising or Volunteer reports your organization relies on. Keep the original files read-only.
Acceptance evidence
A source register with every file, product area, export date, row count, date range, and responsible owner.
Step 2
Inventory what the standard export does not contain
Bloomerang currently says the CRM export excludes email and letter templates, engagement scores, groups, membership programs and levels, split-gift information, and some built-in volunteer interaction fields. Decide whether each item is rebuilt, documented, exported another way, or retired.
Acceptance evidence
An exception ledger with a disposition and owner for every missing or separately sourced artifact.
Step 3
Map IDs and relationships before transforming fields
Use constituent, household, transaction, recurring, campaign, fund, appeal, and relationship identifiers to keep the files connected. Write down merge rules and source-to-destination keys before changing labels or combining structures.
Acceptance evidence
A relationship map that can reconnect people, gifts, commitments, soft credits, notes, tasks, and program context after import.
Step 4
Plan recurring-donor continuity as a separate project
Historical recurring records can be reconciled from exports, but active billing credentials require vendor and processor coordination. Confirm the destination, compliance path, technical contacts, transfer date, next charge, donor communication, and exception handling before changing a live series.
Acceptance evidence
A recurring continuity register covering every active series, processor, next bill date, transfer state, exception, and reconciliation owner.
Step 5
Run representative mappings and dry runs in Gratona
Start with a sample that includes clean and messy donors, historical gifts, refunds, soft credits, recurring cases, households, relationships, notes, tasks, and custom fields. Gratona supports mapping and validation paths that vary by import type; the written scope determines what is included.
Acceptance evidence
A reviewed dry-run report with row outcomes, mapping changes, unresolved records, record counts, and financial totals.
Step 6
Reconcile, accept, and then cut over
Validate records, totals, permissions, reports, forms, receipts, integrations, and staff workflows. Keep one named system authoritative during the transition and do not close the source system until the acceptance record and recovery plan are approved.
Acceptance evidence
A signed acceptance matrix, dated cutover runbook, exception queue, and source-retention decision.
Build a plan for excluded artifacts
Bloomerang's current documentation says the standard CRM export does not include email and letter templates, engagement scores, groups, membership programs and levels, split-gift information, or some built-in volunteer interaction fields. Your organization must decide how each is preserved, rebuilt, separately exported, or retired.
Coordinate recurring donors vendor to vendor
Bloomerang documents a separate request and compliance process for recurring donor information. As reviewed on August 16, 2026, that article lists a one-time $500 extraction fee. Verify current terms, destination processor acceptance, the secure transfer path, and the next charge before scheduling cutover.
Verify the source system before promising the destination
Resolve the exit risks before cutover
Can a nonprofit export all of its Bloomerang data?+
Bloomerang says its organization-level export includes most CRM data in separate CSV files, not every product artifact. Its current documentation excludes email and letter templates, engagement scores, groups, membership programs and levels, split-gift information, and some built-in volunteer interaction fields. Inventory Bloomerang CRM, Fundraising, Volunteer, integrations, and local spreadsheets separately before setting scope.
Can recurring donations move from Bloomerang to another provider?+
Bloomerang documents a separate recurring-donor transfer process. It requires a support request, the new vendor and technical contact, a compliance check, and a coordinated transfer date. As reviewed on August 16, 2026, the documentation lists a one-time $500 extraction fee. Confirm the current terms directly with Bloomerang and the receiving processor before making a cutover promise.
Should we cancel recurring gifts before the transfer?+
Not as a blanket first step. Establish the destination processor, transfer or reauthorization path, next bill date, donor communication, failure handling, and reconciliation owner first. Make changes series by series through the approved continuity plan so a donor is not charged twice or silently skipped.
What should we test before leaving Bloomerang?+
Test representative donor and household records, relationship links, gifts, refunds, soft credits, pledges, active recurring support, funds and campaigns, interactions, notes, tasks, attachments, permissions, reports, forms, receipts, and integrations. Reconcile both record counts and financial totals, then have the responsible owners sign the acceptance result.
What can Gratona import from a Bloomerang migration?+
Gratona has current supported workflows for donor and recipient records, relationships, historical transactions, interactions, and document mappings, with mapping, validation, batch, and error-review paths that vary by import type. Exact Bloomerang files, custom transformations, recurring-payment continuity, managed support, and recovery controls are confirmed after representative exports are reviewed.
Start with the source files and the next recurring charge
Gratona can review representative exports, map the supported destination, identify exceptions, and define the acceptance evidence with your team before a live import is approved.