Migrate from Blackbaud to Freshsales

Individual constituents with gift history map directly to Freshsales Contacts. First name, last name, email, phone, address, and title transfer as standard Contact fields. Constituents with no gift activity route to Lead instead based on lifecycle indicator. This routing preserves donor pipeline continuity.

Organization-type constituents map to Freshsales Accounts. Organization name, website, industry, employee count, and address fields map to their Account equivalents. Parent-child organizational hierarchies in Blackbaud translate to Account hierarchies in Freshsales via the Parent Account lookup. Ensuring consistent reporting across organizational levels.

Constituents flagged as prospects with no recorded gift become Freshsales Leads. Name, email, phone, address, and source campaign transfer. Leads are created when no gift record exists, preserving the pipeline for future cultivation. They retain any prospect rating or source tag from Blackbaud for segmentation.

Each gift becomes a Freshsales Opportunity with Name derived from donor name and gift type, Amount set to gift value, CloseDate set to gift date, StageName set to 'Closed Won', and RecordTypeId assigned based on gift fund type. Pledge gifts create Opportunities with 'Pledge' record type.

Blackbaud campaigns map to Freshsales Campaigns. Campaign name, start and end dates, status, and budget transfer. Campaign members (constituents associated with the campaign) link to Freshsales Contacts and Leads via Campaign Member records. The mapping preserves member status and any response tracking from Blackbaud.

Blackbaud appeals and fund codes store as custom pick-list fields on Freshsales Opportunities. Each appeal or fund code becomes an option in the custom field so fundraisers can report on giving source without rebuilding the accounting hierarchy. This preserves financial reporting continuity.

Blackbaud events map to Freshsales Events for scheduled occasions with start/end times. Event registrants become Tasks linked to the corresponding Contact or Lead so staff can track attendance and follow-up actions. The task description includes event name, date, and registration status for clear reference.

Constituent notes and action records transfer as Freshsales Notes attached to the corresponding Contact or Lead. Original timestamps and owner assignments are preserved. Rich-text formatting in Blackbaud notes is retained as plain text if the formatting is not compatible. This ensures audit continuity.

Recurring gift schedules create Opportunities with a custom 'Recurring Gift' indicator and a note containing the schedule details (frequency, start date, expected end date). Each actual payment in the series creates a child Opportunity linked to the parent. The parent Opportunity tracks total scheduled value.

Blackbaud constituent custom fields of type text, date, currency, yes/no, and number create Freshsales custom fields on Contact or Lead with matching data types. Table-type fields serialize to JSON text in Freshsales custom fields and are flagged for admin review.

Gift-level custom fields transfer as Opportunity custom fields with equivalent data types. Fields like 'Gift Aid eligible' (yes/no) become checkbox custom fields; 'Acknowledgment sent' (date) becomes a date custom field. This mapping ensures that gift-specific metadata remains visible on the Opportunity record for reporting.

Blackbaud relationships between constituents (e.g., board member, spouse) map to Freshsales Account Contact Relationships on the corresponding Account. Relationship type label is stored in the relationship record. The relationship includes a start date and notes field to capture additional context from Blackbaud.

File attachments on constituent and gift records download from Blackbaud and re-upload to Freshsales Files, linked to the corresponding Contact, Account, or Opportunity. File size limits per Freshsales plan apply. If a file exceeds the plan limit, FlitStack splits it into multiple chunks and preserves file metadata for reassembly.