---
title: "Blackbaud to Salesforce Migration: Field Mapping & Rollback"
description: "Migrate Blackbaud to Salesforce with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/blackbaud/to/salesforce-sales-cloud"
---

# Blackbaud to Salesforce migration

Moving from Blackbaud Raiser’s Edge NXT to Salesforce Sales Cloud is the most-requested nonprofit-to-CRM transition in our catalog. FlitStack AI maps every constituent, gift, campaign, and custom field — preserving original create dates and appeal-to-donation history so your Salesforce reports show the full fundraising lifecycle from day one. We sequence the migration to respect Salesforce's AccountId-before-Contact foreign-key requirements and Blackbaud's SKY API rate limits.

Short answer

FlitStack AI migrates account + contacts, contacts, opportunities, campaigns and custom object: fund\_\_cs from Blackbaud to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 50,000 constituent records.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See the field mapping →](https://flitstack.ai/migrations/crm/blackbaud/to/salesforce-sales-cloud#field-mapping)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Blackbaud ![](https://flitstack.ai/platforms-trim/blackbaud.webp)

Destination Salesforce ![](https://flitstack.ai/platforms-trim/salesforce-sales-cloud.webp)

Account + Contact Contact Opportunity Campaign Custom Object: Fund\_\_c

Mapped field by field · sample run · one-click rollback

## What moves from Blackbaud to Salesforce?

Blackbaud Raiser’s Edge NXT models its universe around the Constituent — a single record type that holds individuals, households, and organizations with their gift history, appeals, and custom attributes attached.

Read the full summary

Salesforce Sales Cloud splits this model across Account (organizations), Contact (individuals), and Lead objects, with Opportunities carrying fundraising amounts and Campaigns tracking appeals. The migration therefore has to decompose Blackbaud's constituent-centric model into Salesforce's relational graph: Constituents with an organization type become Accounts + primary Contacts; individual constituents become Contacts attached to a default Account; gifts map to Opportunities with CampaignId pointing to migrated Appeals; and constituent custom fields become Salesforce custom fields on the appropriate object using Blackbaud's field-type metadata (text, number, boolean, date, or picklist). The harder problems are mapping Blackbaud's soft-credit model (which has no native Salesforce equivalent), preserving gift batch and acknowledgment status, and keeping Blackbaud's SKY API extraction within the 10 calls/second throttle while still hitting 25,000 daily quota. FlitStack AI sequences the migration so parent Accounts resolve before child Contacts, resolves constituent owners by email match to Salesforce users, and runs a delta-pickup window at cutover to capture any gifts entered during the final load. Workflow Designer automations and Smart Field rules do not migrate — we export their definitions for your Salesforce admin to rebuild in Flow.

split

### Constituent (organization type) → Account + Contact

Blackbaud organization constituents split into a Salesforce Account (the organization name, address, industry) and a primary Contact (the organization's primary point of contact with their email, phone, and title).

How it maps

The organization's constituent ID is stored as Source\_System\_ID\_\_c on both records for traceability.

direct

### Constituent (individual type) → Contact

Blackbaud individual constituents map directly to Salesforce Contact.

How it maps

The constituent's primary address becomes MailingAddress fields on Contact; additional addresses require AccountContactRelation or custom address fields on the Contact. Email, phone, title, and birthdate transfer directly. Individual constituents without a household association are linked to a default Account during migration.

transformed

### Constituent (household type) → Account + Contact (household model)

Blackbaud households require a choice between Salesforce's Household Account model (one Account per household) or Individual Account model.

How it maps

We map household members as Contacts under a shared Account, preserving the household name and primary address on the Account record. Each household member's name and contact details become separate Contact records linked to the household Account.

direct

### Gift → Opportunity

Each Blackbaud gift becomes a Salesforce Opportunity with Amount, CloseDate, StageName, Description, and CampaignId (pointing to the migrated Appeal/Campaign).

How it maps

Gift date becomes Opportunity CloseDate; gift acknowledgment status migrates to a custom picklist field on Opportunity. Multiple gifts from one constituent become separate Opportunity records.

custom\_field\_required

### Soft Credit → Custom Junction Object

Blackbaud's native soft-credit recipient field has no direct Salesforce equivalent, so we create a custom Gift\_Soft\_Credit\_\_c junction object linking the Opportunity (gift) to the Contact (soft-credit recipient).

How it maps

This junction object includes a role picklist field to capture the soft-credit relationship type, such as Spouse, Employer, or Matching Gift, enabling accurate soft-credit attribution reporting in Salesforce.

direct

### Appeal → Campaign

Blackbaud appeals map to Salesforce Campaign records.

How it maps

Campaign Name, Description, StartDate, EndDate, and TargetRevenue map directly from the Blackbaud appeal fields. Salesforce's campaign hierarchy (parent campaigns) mirrors Blackbaud's appeal hierarchy, preserving the relationship between parent and child appeals. We preserve the appeal's fund reference as a custom field on the Campaign record.

******What moves 12 objects

Blackbaud Salesforce

- Constituent Account split
- Constituent Contact 1:1
- Constituent Account transformed
- Gift Opportunity 1:1
- Soft Credit Custom Junction Object transformed
- Appeal Campaign 1:1

\+ 6 more in the mapping below

## How Blackbaud and Salesforce differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

| Dimension                  | Blackbaud                                                                                                                                     | Salesforce                                                                                                                                                          |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Primary record model       | Blackbaud uses Constituent as a single record type for individuals, households, and organizations — all attributes live on one object.        | Salesforce splits this across Account (organizations), Contact (individuals), and Lead objects, each with separate field sets and page layouts.                     |
| Gift / donation storage    | Blackbaud stores gifts as a top-level Gift record with appeal, fund, campaign, soft-credit, and batch-reference fields.                       | Salesforce has no native Gift object; gifts migrate as Opportunity records with Amount, CloseDate, CampaignId, and custom gift-type fields.                         |
| Campaign / appeal tracking | Blackbaud uses Appeals, Campaigns, and Funds as separate hierarchical objects with target amounts and fiscal-year alignment.                  | Salesforce Campaign object covers appeals and campaigns; Fund accounting requires custom fields or a separate Fund custom object with lookup relationships.         |
| Soft credits               | Blackbaud natively supports soft credits with a dedicated soft-credit recipient field on each gift.                                           | Salesforce has no native soft-credit mechanism; soft credits require a custom junction object or custom fields on Opportunity.                                      |
| Workflow automation        | Blackbaud Workflow Designer automations include action triggers, email alerts, and field-update rules running on constituent and gift events. | Salesforce Flow handles automation — Workflow Rules and Process Builder are deprecated. FlitStack exports Blackbaud workflow definitions for rebuild in Flow.       |
| Data export method         | Blackbaud requires a support ticket and FTP file drop for bulk exports; SKY API throttles at 10 calls/second with 25,000 daily quota.         | Salesforce Bulk API 2.0 handles up to 15,000 batches/day with 10,000 records per batch; REST API caps at 100,000 daily requests on Enterprise.                      |
| Custom field extensibility | Blackbaud custom fields (attributes) attach to any record type and support Boolean, CodeTableEntry, Currency, Date, Number, Text types.       | Salesforce custom fields use \_\_c suffix and support Checkbox, Currency, Date, Number, Percent, Phone, Picklist, Text, Text Area — no native CodeTable equivalent. |

## Blackbaud to Salesforce field mapping

The 30 most-used fields of 45 mapped for this pair. Custom fields are added from your own schema during scoping. [Download the full mapping (CSV) ↓](https://flitstack.ai/migrations/crm/blackbaud/to/salesforce-sales-cloud.csv) or open it in the [field mapping template](https://flitstack.ai/tools/field-mapping-template).

******Field mapping 5 shown

Blackbaud Salesforce

1. `constituent_id` Constituent `Source_System_ID__c` Account
2. `name` Constituent `Name` Account
3. `email_address` Constituent `Email` Contact
4. `phone_number` Constituent `Phone` Contact
5. `mobile_phone` Constituent `MobilePhone` Contact

| Blackbaud field                 | Salesforce field                             | Mapping                 | Note                                                                                                                                                               |
| ------------------------------- | -------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `Constituent.constituent_id`    | `Account.Source_System_ID__c`                | custom\_field\_required | Blackbaud internal ID stored on Salesforce for traceability and delta-run de-duplication.                                                                          |
| `Constituent.name`              | `Account.Name`                               | direct                  |                                                                                                                                                                    |
| `Constituent.email_address`     | `Contact.Email`                              | direct                  |                                                                                                                                                                    |
| `Constituent.phone_number`      | `Contact.Phone`                              | direct                  |                                                                                                                                                                    |
| `Constituent.mobile_phone`      | `Contact.MobilePhone`                        | direct                  |                                                                                                                                                                    |
| `Constituent.address_line_1`    | `Account.BillingStreet`                      | direct                  |                                                                                                                                                                    |
| `Constituent.city`              | `Account.BillingCity`                        | direct                  |                                                                                                                                                                    |
| `Constituent.state`             | `Account.BillingState`                       | direct                  |                                                                                                                                                                    |
| `Constituent.postal_code`       | `Account.BillingPostalCode`                  | direct                  |                                                                                                                                                                    |
| `Constituent.country`           | `Account.BillingCountry`                     | direct                  |                                                                                                                                                                    |
| `Constituent.constituent_type`  | `Account.Type`                               | value\_mapping          | Blackbaud constituent type values (Organization, Individual, Household) map to Salesforce Account Type pick-list values.                                           |
| `Constituent.employer_name`     | `Account.Industry`                           | transformed             | Blackbaud employer stored on individual constituent maps to Account.Industry as a best-fit text field since Salesforce has no direct employer link.                |
| `Constituent.birth_date`        | `Contact.Birthdate`                          | direct                  |                                                                                                                                                                    |
| `Constituent.first_name`        | `Contact.FirstName`                          | direct                  |                                                                                                                                                                    |
| `Constituent.last_name`         | `Contact.LastName`                           | direct                  |                                                                                                                                                                    |
| `Constituent.middle_name`       | `Contact.MiddleName`                         | direct                  |                                                                                                                                                                    |
| `Constituent.suffix`            | `Contact.Suffix`                             | direct                  |                                                                                                                                                                    |
| `Constituent.title`             | `Contact.Title`                              | direct                  |                                                                                                                                                                    |
| `Constituent.created_date`      | `Account.Original_Create_Date__c`            | custom\_field\_required | Salesforce CreatedDate is set at migration time. Original Blackbaud created date preserved as a custom datetime field for reporting continuity.                    |
| `Constituent.modified_date`     | `Account.LastModifiedDate`                   | direct                  |                                                                                                                                                                    |
| `Gift.gift_id`                  | `Opportunity.Source_System_ID__c`            | custom\_field\_required | Blackbaud gift ID stored on Salesforce Opportunity for traceability and delta-run de-duplication.                                                                  |
| `Gift.gift_amount`              | `Opportunity.Amount`                         | direct                  |                                                                                                                                                                    |
| `Gift.gift_date`                | `Opportunity.CloseDate`                      | direct                  |                                                                                                                                                                    |
| `Gift.gift_type`                | `Opportunity.Type`                           | value\_mapping          | Blackbaud gift type values (Cash, Check, Credit Card, Stock, In-Kind) map to Salesforce Opportunity Type pick-list values.                                         |
| `Gift.fund_id`                  | `Opportunity.Fund__c`                        | custom\_field\_required | Blackbaud Fund lookup requires a Fund\_\_c custom object created in Salesforce before migration; Opportunity gets a lookup field pointing to it.                   |
| `Gift.appeal_id`                | `Opportunity.CampaignId`                     | transformed             | Blackbaud Appeal maps to Salesforce Campaign; the appeal\_id becomes the Salesforce Campaign ID on the Opportunity record.                                         |
| `Gift.soft_credit_recipient_id` | `Gift_Soft_Credit__c.Soft_Credit_Contact__c` | custom\_field\_required | Soft-credit recipient migrates to a custom junction object linking Opportunity to the Contact. Custom object Gift\_Soft\_Credit\_\_c created before migration.     |
| `Gift.batch_reference`          | `Opportunity.Batch_Reference__c`             | custom\_field\_required | Blackbaud gift batch reference preserved as a text custom field on Opportunity for reconciliation during migration.                                                |
| `Gift.acknowledgment_status`    | `Opportunity.Acknowledgment_Status__c`       | custom\_field\_required | Acknowledgment status (Sent, Not Sent, Acknowledged) migrates to a custom pick-list field on Opportunity.                                                          |
| `Gift.constituent_id`           | `Opportunity.AccountId`                      | transformed             | Gift's constituent link resolves to the migrated Account record. Organization constituents link to Account; individual constituents link to their primary Account. |

## What to watch for in a Blackbaud to Salesforce migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### Soft credits have no native Salesforce equivalent — requires custom junction object

Blackbaud's Gift record includes a dedicated soft-credit recipient field that lets you attribute a gift to a secondary constituent (e.g., a spouse who directed a donation).

How we handle it

Salesforce Opportunity has no native soft-credit mechanism — if you try to map this directly, you'll lose the relationship. We handle this by creating a custom Gift\_Soft\_Credit\_\_c junction object that links the Opportunity (gift) to the Contact (soft-credit recipient) with a role pick-list field. This requires the custom object to be created in Salesforce before migration, and your admin should verify the junction object supports your reporting needs for soft-credit attribution.

high

### Blackbaud constituent N:N relationships require Salesforce AccountContactRelation setup

Blackbaud lets a constituent be linked to multiple organizations simultaneously (a board member who also works for a vendor, for example).

How we handle it

Salesforce Contact has a single primary AccountId, but the AccountContactRelation object supports additional relationships. We migrate the most recently modified or primary organization as AccountId on Contact, and surface all secondary organization links as AccountContactRelation records. If your Blackbaud instance uses complex N:N constituent-to-organization relationships with custom relationship types, you'll need to define the corresponding relationship types in AccountContactRelation before migration — we surface this in the pre-migration schema plan.

medium

### SKY API rate limit (10 calls/second) extends extraction time for large datasets

Blackbaud's SKY API enforces a hard throttle of 10 calls per second regardless of subscription tier, with a daily quota of 25,000 calls.

How we handle it

For a constituent database with 100,000 records, a naive extraction hitting each record individually would require 10,000 API calls minimum — consuming nearly half your daily quota in a single pass before gifts, appeals, and actions are even queried. FlitStack AI uses bulk export requests and batched processing to stay within the throttle while maximizing records per call, but large Blackbaud datasets will extend the extraction phase beyond what a comparable Salesforce-source migration would require. Plan your data freeze and delta-pickup window accordingly.

medium

### Workflow Designer automations do not migrate — export definitions for Flow rebuild

Blackbaud Workflow Designer rules fire on constituent events (gift received, appeal opened, field changed) and include action steps, email alerts, and task assignments.

How we handle it

These are platform-specific automation constructs with no Salesforce equivalent — they cannot be exported as working rules and loaded into Salesforce Flow. FlitStack AI extracts your workflow definitions from Blackbaud as a written reference document (workflow name, trigger event, step logic, and action assignments) so your Salesforce admin can rebuild them as FlowBuilder workflows post-migration. This is a manual step that should be scoped alongside your Salesforce admin during the pre-migration phase.

medium

### Blackbaud fund accounting requires a custom object for Salesforce fund tracking

Blackbaud's Fund object lets you route gifts to specific accounting buckets — a critical requirement for nonprofit fund accounting and 990 reporting.

How we handle it

Salesforce has no native Fund object; the standard Opportunities are not segmented by fund without configuration. We create a Fund\_\_c custom object with a fund code text field and a lookup to Campaign, then add a Fund\_\_c lookup field on Opportunity so gift records can be tagged to the correct fund at migration time. Your finance team should validate the fund code mapping against your Blackbaud fund list before the migration runs to ensure all gift-to-fund assignments are correct.

## How the migration runs

1. ### Request Blackbaud data export via FTP or support ticket

   Blackbaud bulk data extraction requires either a support ticket with a Customer Authorization Form (for managed backups) or access to the FTP site where Blackbaud places a zipped database file.

   What this step covers

   We initiate this request on your behalf — the admin who owns the Blackbaud account must sign the authorization form and attach it to a support case. While waiting for the export, we begin the Salesforce schema design so custom objects, custom fields, and record types are ready before data lands.

2. ### Design Salesforce schema: custom objects, custom fields, record types, page layouts

   We analyze your Blackbaud data export to inventory all custom fields (by type: Boolean, CodeTableEntry, Currency, Date, Number, Text), appeal/campaign/fund hierarchy, and gift batch structure.

   What this step covers

   We then deliver a Salesforce schema setup plan: Fund\_\_c custom object definition, soft-credit junction object, custom fields on Account/Contact/Opportunity/Campaign with pick-list value mappings, and record-type assignments if you're splitting constituent types across Salesforce profiles. Your Salesforce admin creates these before migration runs.

3. ### Extract constituents, gifts, appeals, actions, and attachments from Blackbaud

   We run API extraction against Blackbaud SKY API respecting the 10 calls/second throttle.

   What this step covers

   Constituents are extracted first (to build the ID mapping table), then gifts (with appeal and fund references resolved from the ID map), then appeals and campaigns, then actions, then file attachments. Each extraction pass logs record counts, API call consumption, and any throttling events. Duplicate detection runs against constituent email and constituent\_id to flag records that may need merging before Salesforce load.

4. ### Run a sample migration with field-level diff before full run

   A representative slice migrates first — typically 200–500 constituent records spanning individuals, organizations, and households, plus associated gifts, appeals, and actions.

   What this step covers

   We generate a field-level diff comparing source Blackbaud values against destination Salesforce field values so you can verify: constituent-to-Account/Contact split, gift amount and close date accuracy, appeal-to-campaign mapping, soft-credit junction object linkage, and owner resolution by email. You approve the sample before the full run commits.

5. ### Execute full migration with delta-pickup window at cutover

   Full migration runs against Salesforce using Bulk API 2.0 for high-volume record loads (Accounts, Contacts, Opportunities).

   What this step covers

   A delta-pickup window — typically 24–48 hours — runs after the initial bulk load to capture any gifts entered in Blackbaud during the cutover. Audit log captures every create and update operation. One-click rollback reverts all Salesforce records to pre-migration state if reconciliation against the Blackbaud source reveals data integrity issues. We deliver a reconciliation report comparing source record counts and gift totals against Salesforce Opportunity counts and sum amounts.

![](https://flitstack.ai/platforms/blackbaud.svg) Blackbaud ![](https://flitstack.ai/platforms/salesforce-sales-cloud.svg) Salesforce

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Salesforce Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**48–72 hours for under 50,000 constituent records** Typical, smaller accounts

**5–10 days for over 500,000 records or complex gift-batch / custom-object setups** Large or heavily customised accounts

Blackbaud to Salesforce migration pricing scales with three drivers: (1) record volume — constituent count, gift count, and campaign count determine extraction time and Salesforce API batch consumption; (2) custom field count — Blackbaud's attribute model means each custom field on Constituent, Gift, or Appeal requires a Salesforce custom field (or custom object) to be created before data loads, and Blackbaud setups commonly carry 30–100+ custom fields per record type; (3) data-model divergence — the constituent-to-Account/Contact split, the Gift-to-Opportunity remapping, and soft-credit handling all add mapping complexity that higher record counts amplify. Teams with complex gift batches, appeal hierarchies, or N:N constituent relationships fall in the upper range. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Blackbaud to Salesforce →](https://flitstack.ai/contact)

## Why teams move from Blackbaud to Salesforce

- Blackbaud's NXT interface has drawn repeated criticism for slow data input and counter-intuitive navigation — users on the Blackbaud Community report that cleaning up bulk imports in NXT requires going to a separate table view rather than editing inline, ballooning what took 3 hours in database view to 6–9 hours in NXT.
- Organizations report that Blackbaud's pricing model has become unpredictable — custom quotes with no public floor, add-on fees for premium features like Strategy Assistant and Cultivation Assistant, and contract structures that make budgeting difficult as teams scale. Multiple organizations report surprise line items on invoices and difficulty forecasting annual software costs without a consistent pricing framework.
- Salesforce's Nonprofit Success Pack (NPSP) combined with the Power of Us (P10) program offers eligible nonprofits 10 free subscriptions plus discounts on Salesforce services — a concrete cost advantage cited by organizations like The Mustard Seed and CNIB that migrated from Raiser’s Edge.
- Organizations with multiple constituent bases — volunteers, donors, program participants — find Blackbaud's unified constituent model constrains reporting depth. Salesforce's Account-Contact relationship model with junction objects and custom lookup fields lets them segment and analyze each constituent group independently while maintaining a holistic view in one org.
- Blackbaud's SKY API enforces a 10 calls/second throttle and 25,000 daily quota that makes high-volume data extraction slow and complex. Salesforce Bulk API 2.0 handles 15,000 batches per day with 10,000 records per batch — far faster for large constituent databases.

Questions, answered

## Blackbaud to Salesforce migration questions

How long does a Blackbaud to Salesforce Sales Cloud migration take?

Most Blackbaud-to-Salesforce migrations complete in 48–72 hours of clock time for under 50,000 constituent records. Larger setups with 500,000+ records, complex gift-batch structures, or multiple custom objects extend to 5–10 days. The longest planning step is designing the Salesforce custom-object schema (Fund\_\_c, Gift\_Soft\_Credit\_\_c) and getting your admin to create custom fields before data loads. SKY API extraction speed is constrained by Blackbaud's 10 calls/second throttle, which can add hours for large datasets compared to a comparable Salesforce-source migration.

Will my Blackbaud Workflow Designer automations migrate to Salesforce Flow?

No. FlitStack AI migrates data and schema only — Workflow Designer rules, action triggers, and Smart Field updates do not transfer. They run on Blackbaud-specific event models that have no Salesforce equivalent. We extract your workflow definitions as a written reference document (workflow name, trigger event, step logic, and action assignments) so your Salesforce admin can rebuild them as FlowBuilder workflows. This is a manual step that should be scoped alongside your Salesforce admin during the pre-migration phase — most nonprofit organizations have 5–20 workflows that take 1–3 days to rebuild depending on complexity.

What does a Blackbaud gift become in Salesforce?

Each Blackbaud gift becomes a Salesforce Opportunity record. The gift amount maps to Opportunity.Amount, the gift date maps to Opportunity.CloseDate, and the Blackbaud appeal maps to Opportunity.CampaignId (pointing to the migrated Appeal/Campaign). Gift acknowledgment status and batch reference migrate as custom fields on Opportunity. Soft credits require a custom Gift\_Soft\_Credit\_\_c junction object that your admin creates before migration, linking the Opportunity to the secondary contact recipient.

Can I migrate Blackbaud custom fields to Salesforce custom fields?

Yes. Blackbaud custom fields (called 'attributes' in Raiser’s Edge NXT) attach to constituent, gift, and appeal records. We analyze each custom field by Blackbaud type — Boolean, CodeTableEntry, Currency, Date, Number, Text — and create corresponding Salesforce custom fields on Account, Contact, Opportunity, or Campaign using the closest Salesforce field type. CodeTableEntry pick-list values require value-by-value mapping since Salesforce pick-lists are scoped to the field rather than a shared code table. Blackbaud setups commonly carry 30–100+ custom fields per record type, which is the primary driver of upper-range pricing.

What happens to Blackbaud soft credits in Salesforce?

Blackbaud's native soft-credit recipient field has no direct Salesforce equivalent — Salesforce Opportunity does not have a soft-credit lookup. We handle this by creating a custom Gift\_Soft\_Credit\_\_c junction object before migration. This object links the Opportunity (gift) to the Contact (soft-credit recipient) and includes a role pick-list field to capture the relationship type. Your Salesforce admin should validate that this junction object supports your soft-credit reporting needs; organizations with complex soft-credit attribution chains (e.g., matching gifts, employer matches) may need additional custom fields or a different junction model.

Does the migration affect my Blackbaud account during the cutover?

No. FlitStack AI uses scoped read access on Blackbaud — your team continues working in Blackbaud throughout the extraction and migration process. We recommend a content freeze only during the final delta-pickup window (24–48 hours after the bulk load completes), when your team pauses new gift entry to ensure Salesforce reflects Blackbaud's final state at go-live. During this window we run the delta extract to capture any records created or modified since the initial bulk extraction.

How does Blackbaud's fund accounting map to Salesforce?

Blackbaud's Fund object (the accounting bucket for gift routing) has no native Salesforce equivalent. We create a Fund\_\_c custom object with Name, Fund\_Code\_\_c (text), and a lookup to Campaign, then add a Fund\_\_c lookup field on Opportunity so gift records can be tagged to the correct fund at migration time. Your finance team should validate the fund code mapping against your Blackbaud fund list before migration runs. If your organization uses Blackbaud Financial Edge NXT for fund accounting, the Fund\_\_c custom object should be reconciled against your Financial Edge fund codes as a post-migration step.

What happens to Blackbaud constituent attachments and file links during migration?

Blackbaud file attachments on constituent and gift records are downloaded from Blackbaud's storage and re-uploaded to Salesforce Files (ContentDocument/ContentVersion) linked to the parent record — Account, Contact, or Opportunity. File size limits apply: Salesforce default is 25MB per file; larger files require Salesforce Large File Storage or a file management app. We preserve the original file name, upload date, and uploader as metadata on the Salesforce File record. Inline images embedded in Blackbaud notes are extracted and re-hosted as Salesforce Files linked to the note's parent record.

## Related migrations

[![](https://flitstack.ai/platforms-trim/salesforce-sales-cloud.webp) Migrate to **Salesforce** Every source we move into Salesforce, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/crm/salesforce-sales-cloud)

### [Salesforce implementation](https://flitstack.ai/services/salesforce-implementation)

[Set up Salesforce and migrate into it as one engagement.](https://flitstack.ai/services/salesforce-implementation)

[See the service →](https://flitstack.ai/services/salesforce-implementation) [**ActiveCampaign to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/activecampaign/to/salesforce-sales-cloud) [**Freshsales to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/freshsales/to/salesforce-sales-cloud) [**monday CRM to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/monday-crm/to/salesforce-sales-cloud) [**Twenty CRM to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/twenty-crm/to/salesforce-sales-cloud) [**Highrise to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/highrise/to/salesforce-sales-cloud) [**Jobber to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/jobber/to/salesforce-sales-cloud)

## Sources: official documentation

1. [Custom Field Attributes — Salesforce Help (External ID)](https://help.salesforce.com/s/articleView?id=platform.custom_field_attributes.htm)
2. [Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help](https://help.salesforce.com/s/articleView?id=000380434\&type=1)
3. [Uploading Activity data to Salesforce — Salesforce Stack Exchange](https://salesforce.stackexchange.com/questions/15694/uploading-activity-data-to-salesforce)
4. [Sandboxes — Staging Environments for Customizing and Testing](https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/deploy_sandboxes.pdf)
5. [Case Comment STRING\_TOO\_LONG — Salesforce Stack Exchange](https://salesforce.stackexchange.com/questions/44763/case-comment-error-string-too-long-body-data-value-too-large)
6. [Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV](https://dev.to/prince_6a5fbc059971cef8c8/salesforce-data-migration-7-challenges-and-how-to-solve-them-3bb7)
7. [Salesforce Duplicate Management — Salesforce Stack Exchange](https://salesforce.stackexchange.com/questions/151012/salesforce-duplicate-management-importing-duplicates)

Get a quote

## Moving from Blackbaud to Salesforce?

Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
