Migrate from Blackbaud to Odoo CRM

Blackbaud Constituent maps directly to Odoo res.partner. The Constituent Type field (Individual, Organization, Household) sets res.partner.type (contact / company / delivery). Multi-address constituents: Blackbaud's address table (Constituent Address) is flattened to the primary address on res.partner, with additional addresses stored as partner address records linked by parent_id.

Individual constituents migrate as Odoo contacts. Blackbaud name parts (First Name, Last Name, Prefix, Suffix) map to name, firstname, and lastname on res.partner. The constituent lookup_id becomes the external_id field for deduplication. Household constituents use a different mapping approach — see Household mapping row.

Organization constituents migrate as Odoo companies (type=company). Blackbaud Organization Name maps to res.partner.name. We set parent_id to null for organizations — related contacts link back to the company record via parent_id. If the Blackbaud constituent has a primary contact flag, that contact lands as the default child contact.

Blackbaud Household is a separate record type that groups family members under one giving unit. We map the Household name to a company-type res.partner and create individual child contacts for each named member, preserving the household designation in a custom field (Household_Member__c or x_household_id). Soft credit and aggregate giving amounts transfer as custom fields on the household-level partner.

Odoo has no native gift/donation object. We discuss two paths with each client: (1) map gifts to account.move lines with analytic account tags for fund tracking — preserves financial integrity for organizations doing GL reconciliation in Odoo Accounting; (2) map gifts to crm.lead with custom fields (gift_amount, gift_date, fund_id) for organizations using Odoo CRM only. The chosen path determines the full field mapping set.

Blackbaud Fund tracks restricted and unrestricted giving designations, goal amounts, and GL distribution codes. Odoo analytic accounts serve as the closest equivalent. We map Fund ID to analytic_account.code, Fund Name to analytic_account.name, and goal amounts to custom fields on the analytic account. If Odoo Accounting is not installed, we create analytic tags as a lighter-weight alternative.

Blackbaud Campaign groups Appeals and Gifts hierarchically. In Odoo, we use crm.tag records (or analytic.account.parent_id for nested campaigns) to recreate the campaign hierarchy. Campaign status (Active/Completed) maps to a tag category in Odoo. We preserve the campaign code as a tag name prefix so reporting can reference both Blackbaud and Odoo identifiers.

Blackbaud Event records map to Odoo event.event. Event Participants (attendees) migrate as event.registration linked to the event and to the constituent's res.partner record. Registration status (Attended, Cancelled, No-Show) maps to registration.state. Ticket types and fees become registration.seats_local or custom fields if they have custom pricing.

Blackbaud Action records (calls, meetings, tasks) migrate as Odoo mail.activity records linked to the parent res.partner or crm.lead. Activity type, due date, completion date, and outcome notes are preserved. Blackbaud Action categories map to Odoo activity type definitions — your admin defines the activity types in Odoo before migration runs.

Blackbaud document attachments on constituents, gifts, or events migrate as ir.attachment records in Odoo, linked to the corresponding res.partner, account.move, or event.event record. Files are downloaded from Blackbaud's blob storage and re-uploaded to Odoo's filestore (ir_attachment). Large file handling respects Odoo's attachment size limits.

Blackbaud custom field categories and their types (Text, Boolean, Code Table Entry, Currency, Date, Number) are read from the SKY API schema endpoint. Each Blackbaud custom field category becomes a custom field on the corresponding Odoo model — x_name for Community Edition, x_studio_name for Odoo Studio. Type mappings: Currency → monetary, Code Table Entry → selection (with value map), Date → date, Number → float or integer.

Blackbaud Users (gift officers, fundraisers) resolve to Odoo res.users by email address match. Constituent Owner fields on gifts and actions become Odoo activity and record creators. Unmatched owners are flagged before migration — your team either invites them to Odoo or reassigns their records to a fallback user. No record lands without an Odoo owner assignment.