Migrate from Blackbaud to Twenty CRM

Blackbaud constituents map 1:1 to Twenty People. Name components (prefix, first, middle, last, suffix) concatenate into the Twenty displayName; FlitStack preserves the split components in custom fields for rebuild flexibility. Multiple addresses per Blackbaud constituent collapse to one primary address; remaining addresses surface as custom fields.

Blackbaud organizations map to Twenty Companies with primary field alignment on name, address, and contact fields. Parent-child organizational hierarchies in Blackbaud use a Parent Organization field that FlitStack maps to Twenty's parentCompany foreign key. Organization-constituent relationships are N:N in Blackbaud; since Twenty Company supports only a single companyId foreign key per People record, FlitStack creates a custom junction object in Twenty to preserve these many-to-many associations between organizations and constituent records.

Blackbaud households group multiple constituents under one shared household name with designated primary and secondary members. FlitStack handles this by creating one primary People record using the household name and adding other members as related People records linked via a custom HouseholdMember junction object. This approach preserves the household-level identity while maintaining each member's individual constituent data in the correct Twenty People structure.

Blackbaud constituent codes classify donors into meaningful categories such as Major Donor, Board Member, Volunteer, or Recurring Giver. FlitStack creates a custom Select field on the People object and populates it with the exact source code values as selectable options. When a constituent code has no matching value in the source data, FlitStack creates a 'Legacy' option to flag these records for post-migration cleanup and review by the administrative team.

Blackbaud gifts represent a comprehensive fundraising record with fund, appeal, campaign, payment method, soft credits, and tribute fields. Since Twenty has no native gift object, FlitStack creates a custom Gifts object with fields for GiftAmount, GiftDate, Fund, Appeal, Campaign, PaymentMethod, SoftCreditConstituentId, and TributeName. Each gift record links to the constituent People record via a relation field, enabling attribution of donations to individual donors within the Twenty data model.

Blackbaud campaigns are fundraising initiatives that track start and end dates, goal amounts, and associated appeal codes. FlitStack creates a custom Campaign object in Twenty linked to the Opportunities attributed to each campaign. Campaign name, start date, end date, and goal amount migrate as custom fields on the Campaign object, preserving the strategic context of fundraising efforts within Twenty's relational structure.

Blackbaud funds define the designation rules for gift money, distinguishing between restricted funds (designated for specific purposes) and unrestricted funds (available for general use). FlitStack creates a read-only custom Fund object in Twenty referenced by Gift records via a relation field. Fund code, description, and restriction type migrate as custom fields on the Fund object, ensuring gift allocation rules remain traceable and auditable in the Twenty environment.

Blackbaud appeals are specific fundraising ask vehicles within a campaign, such as Annual Fund letter, Gala auction item, or direct mail solicitation. FlitStack creates a custom Appeal pick-list field on the Gifts object so each gift can reference its originating appeal. The appeal code from the Blackbaud source preserves the specific fundraising vehicle attribution, allowing teams to analyze which appeals generate the most giving in Twenty's reporting layer.

Blackbaud opportunities map directly to Twenty Opportunities with stage, amount, close date, and owner fields aligned. Blackbaud's opportunity status values (Open, Completed, Aborted) map to Twenty's status field using a value mapping table. Owner resolution uses email matching against Twenty user records; any owners without matching email addresses flag for fallback assignment during the migration run.

Blackbaud engagement records including constituent notes, call logs, email threads, and meeting records migrate as Twenty Notes (for free-text content) or Tasks (for action items requiring follow-up). Original timestamps, author information, and the parent record link (ConstituentId or OrganizationId) are preserved as custom fields on the Twenty record, maintaining the complete engagement history and audit trail across the migration.

Blackbaud file attachments on constituents and organizations are downloaded and re-uploaded to Twenty's file storage. File size limits and inline image handling follow Blackbaud's export format; FlitStack maps the attachment's parent record (ConstituentId or OrganizationId) to the corresponding Twenty People or Company ID.

Blackbaud custom fields per category support multiple data types simultaneously (Boolean, CodeTableEntry, Currency, Date, FuzzyDate, Number, Text). FlitStack creates one Twenty custom field per Blackbaud field type encountered, naming them with the category prefix (e.g., ConstituentAttribute_Date, ConstituentAttribute_Currency) so no data is lost during migration.