Migrate from Blackbaud to Pipedrive

Blackbaud individual constituents map 1:1 to Pipedrive People. Name fields split into first_name and last_name. Email addresses migrate to the email field; multiple email addresses on a single constituent collapse to the primary with additional addresses stored in custom fields.

Blackbaud organization constituents map to Pipedrive Organizations. Organization name maps to the name field. Domain/website migrates to the website field. Parent-child constituent relationships map to Pipedrive's parent organization reference where supported.

Gifts do not have a native Pipedrive equivalent. Gift amount, date, fund, campaign, and giftaid status migrate as custom fields on Pipedrive Deals or People, depending on your reporting preference. We surface the mapping choice during planning before migration runs.

Blackbaud fundraising Opportunities map to Pipedrive Deals. Deal name, amount, and expected close date translate directly. Opportunity stage maps to a custom pick-list field or Pipedrive pipeline stage, depending on whether the opportunity tracks fundraising milestones or pipeline progress.

Blackbaud Campaigns have no native Pipedrive equivalent. We preserve the campaign name and code as a custom field on Deals for attribution reporting. Your admin can choose to create a custom Pipedrive field (Campaign_Name__c) or use a label convention in the deal name.

Blackbaud Funds (the accounting dimension for restricted or unrestricted gift allocation) migrate as a custom pick-list or text field on Deals. Fund-restriction status can be preserved as a separate custom field if your reporting depends on it post-migration.

Blackbaud Appeals (the specific ask vehicle within a campaign) migrate as a custom field on Deals alongside the campaign field. Appeal-level appeal code and appeal description can be stored in separate custom fields or combined into a single delimited field based on your reconciliation needs.

Blackbaud constituent Actions (task-type records) migrate to Pipedrive Activities. Activity type (call, email, meeting, task) maps to Pipedrive's activity_type. Original completed date and owner migrate with the record. Uncompleted actions surface as open Pipedrive activities with due dates.

Blackbaud Notes attached to constituents or opportunities migrate as Pipedrive Notes. Rich-text formatting is preserved where supported. Notes are linked to the corresponding Person, Organization, or Deal record in Pipedrive based on the source attachment.

Blackbaud custom field categories with types Boolean, Text, Number, Date, Currency, and CodeTableEntry create as Pipedrive custom fields. Pipedrive generates a 40-character hash key for each custom field — we map the source category name and values during migration. ConstituentId reference fields require manual relationship rebuilding in Pipedrive.

Blackbaud household constituents (family grouping) can be handled two ways: (1) primary household member becomes the Person record with others as related contacts, or (2) household name creates an Organization record and members link to it. We surface the preferred approach before migration based on your reporting structure.

Blackbaud file attachments on constituent records re-upload to Pipedrive's file attachment model. File size limits apply (varies by Pipedrive plan). Inline images in notes download and rehost in Pipedrive's file storage. Files without a clear record attachment land on the related Person or Organization.