Migrate from Blackbaud to Microsoft Dynamics 365 Sales

Blackbaud individual constituents map 1:1 to Dynamics 365 Contact records. The primary email address maps to Email, phone numbers to Telephone1/2/3, and mailing address to the composite address fields. Original constituent ID stored as Blackbaud_ID__c for traceability and delta-run de-duplication. Constituents without a primary address default to a placeholder address flagged in the migration report.

Blackbaud organization constituents map to Dynamics 365 Account records. Organization name maps to Account.Name, website to Website, industry to Industry (value-mapping from Blackbaud's industry codes to Dynamics 365 pick-list). Parent-child organizational hierarchies in Blackbaud map to Account.ParentAccountId. Multi-contact organizations generate one Account record plus a primary Contact record for the primary gift officer or organizational contact.

Blackbaud households (family giving units) have no direct Dynamics 365 equivalent. The primary member becomes the primary Contact record; secondary household members are created as related Contacts with an Account Contact Relationship record linking them to a shared household Account. Giving totals from the Blackbaud household record are preserved as a custom currency field on the primary Contact. Your team decides whether to collapse household structure or maintain it via the relationship model.

Blackbaud Gift records become Dynamics 365 Opportunity records — gift amount maps to Amount, gift date maps to CloseDate (set to actual gift date), and gift description maps to Name. Fund code and appeal designation from the gift are stored as custom Opportunity fields (Fund_Code__c, Appeal__c). Soft-credit gifts require secondary Opportunity records or a custom junction object depending on whether the soft-credit constituent should appear as a separate Opportunity or a participant on the primary gift record.

Blackbaud Campaigns map directly to Dynamics 365 Campaign records — campaign name to Name, start/end dates to StartDate/EndDate, budget to BudgetedCost. Campaign type codes (Annual Fund, Capital Campaign, Event) map to the Dynamics 365 Campaign Type pick-list via value-mapping. Campaign goals from Blackbaud are stored as custom numeric fields on the Dynamics Campaign record since Dynamics 365 Campaign does not have a native goal amount field.

Blackbaud Appeals are sub-objects of Campaigns with their own budget, goal, and designation. In Dynamics 365, each Appeal maps to a child Campaign record under the parent Blackbaud Campaign, preserving the hierarchy. If the Dynamics 365 environment uses only one Campaign model, Appeal designation is stored as Appeal__c on the related Opportunity/Gift record instead. We surface the chosen approach in the migration plan before execution.

Blackbaud Action records (reminders, to-dos, call logs) map to Dynamics 365 Task records. Subject maps to Subject, action date to ScheduledEnd, description to Description. Action status maps to StatusCode (Open/Completed). Owner resolution happens by email match against Dynamics 365 users — unmatched Action owners are flagged and assigned to a migration owner for resolution before the full run.

Blackbaud constituent notes and document attachments map to Dynamics 365 Annotation records. Note text maps to Notetext, attachment files are downloaded from Blackbaud's file storage and re-uploaded to Dataverse file storage (max 128MB per file). Inline images in notes are extracted and re-hosted as separate file annotations. Rich-text formatting is preserved where Dynamics 365 Notetext supports it — complex formatting is flattened to plain text fallback.

Blackbaud custom field categories (Boolean, CodeTableEntry, Currency, Date, Number, Text) require corresponding custom columns in Dynamics 365. We deliver a custom-column creation plan with exact schema definitions (column name, data type, pick-list values) so your Dynamics 365 admin creates all custom fields before the migration run. Custom fields on constituents with CodeTableEntry type require value-by-value pick-list mapping against Dynamics 365 option set definitions. Fields must exist in Dynamics 365 before data can land in them.

Blackbaud recurring gifts and pledges are split into individual installment Opportunity records in Dynamics 365 — one Opportunity per installment payment with pledge installment dates as CloseDate values. Pledge总额 is stored as a custom field (Pledge_Total__c) on the first installment Opportunity for reporting continuity. Alternatively, your team can choose a custom Pledge entity if Dynamics 365 Sales Enterprise is licensed, which allows unlimited custom tables — we present both options in the migration plan.

Blackbaud membership records (included in some Blackbaud CRM tiers) have no direct Dynamics 365 equivalent. Membership level, expiration date, and member ID are stored as custom fields on the Contact record (Member_Level__c, Membership_Expiration__c, Member_ID__c). If your organization runs membership events and benefits tracking, a custom Membership table in Dataverse may be warranted — we assess this during the migration planning call.

Blackbaud user and gift officer records are resolved against Dynamics 365 SystemUser records by email address match. The Blackbaud user ID is stored as Blackbaud_Owner_ID__c on migrated records for audit traceability. Users present in Blackbaud but not in Dynamics 365 are flagged before migration — your team either provisions them in Dynamics 365 first or reassigns their records to an existing user.