Migrate from Blackbaud to HubSpot

Blackbaud constituents map directly to HubSpot contacts. We preserve the original constituent ID as Source_System_ID__c on the HubSpot contact for traceability. Constituent address records collapse to HubSpot’s single address property, with primary address retained and others surfaced as custom properties.

Blackbaud household relationships require mapping to HubSpot’s Households feature (requires HubSpot Enterprise) or to a custom contact grouping strategy. We build a HubSpot list per household and link members via the household contact as the primary group owner for queryable reporting.

Blackbaud gifts do not have a direct HubSpot equivalent. We create a custom Gift object in HubSpot with fields for amount, date, payment method, fund, campaign, appeal, soft credits, and tribute type. Each gift links to the constituent contact via a custom association.

Soft credits on a Blackbaud gift are stored as separate records referencing the original gift. We map these as a multi-select or repeatable field group on the HubSpot Gift custom object, preserving the credited constituent ID and amount for each soft credit.

Designation lines on a gift (which fund receives which portion of a split gift) map to a repeatable fund_designation field on the HubSpot Gift custom object. Each designation includes the fund ID, amount, and appeal reference from Blackbaud, preserving the full accounting detail for reconciliation.

Blackbaud funds are financial entities used for gift attribution and GL distribution. HubSpot has no native fund object. We map fund IDs to a custom pick-list field (Fund__c) on the Gift custom object so fund attribution is queryable in HubSpot reporting.

Blackbaud appeals map to a custom appeal field on the Gift object. The appeal name and appeal code from Blackbaud are stored as separate text and pick-list fields so campaigns can be filtered in HubSpot reports by appeal source.

Blackbaud campaigns map to HubSpot campaigns 1:1. We preserve campaign start and end dates, campaign type, and goal amounts as HubSpot campaign properties. Campaign membership (constituents targeted) translates to HubSpot campaign contacts for accurate reach tracking.

Blackbaud constituent actions (tasks, appointments, notes) and opportunities map to HubSpot engagements and deals. We preserve the original action type, date, owner, and completion status. Major gift prospects modeled as opportunities in Blackbaud become HubSpot deals with pipeline and stage.

Blackbaud event participants map to HubSpot meetings linked to constituent contacts. Registration status, ticket type, and fee paid translate to custom properties on the meeting record. Event-level revenue aggregates roll up via HubSpot reporting for accurate event ROI.

Blackbaud custom fields across all objects (constituent attributes, gift-specific fields, action custom fields) map to HubSpot custom properties. We create each custom property in HubSpot with the appropriate field type (text, number, date, pick-list, boolean) matching Blackbaud’s type metadata from the API.

Blackbaud constituent and gift attachments are downloaded and re-uploaded to HubSpot Files. Files attach to the corresponding contact or gift custom object record via HubSpot’s file association model. We preserve original file names and upload timestamps for compliance documentation.

Blackbaud constituent relationships (spouse, employer, board member) and constituent attributes map to HubSpot contact properties. N:N relationships surface as a custom association object linking two contacts, preserving the relationship type and metadata from Blackbaud for accurate relationship reporting.

Blackbaud batch records (used for gift entry grouping) have no HubSpot equivalent. We preserve batch ID and batch description as a custom property on the affected gift records for audit reference but do not create a separate batch object.