Launched:self-serve migrations intoSuperhuman Docs (Coda)
Try it now
01Agent-first
Runs where you already work
Plug it into Claude, ChatGPT or Cursor. Describe the move in plain English; the agent runs it.
02Engineer-led
Our production engine, unlocked
The pipeline our engineers use on managed enterprise migrations — the same code, now something you can drive yourself.
03Pricing
Try 10 pages free, then $1 a page
Credit-based, pay-as-you-go. No scoping call, no quote — sample it on your own docs before you spend anything.
04Sources
NotionSlabConfluenceSoonGoogle DocsSoon
Skip to content

Microsoft Fundraising & Engagement End of Support: 2026 Migration Guide

Microsoft Fundraising and Engagement loses all support on December 31, 2026. Here's what data must move, three migration paths compared, and how to avoid year-end disruption.

Roopendra Talekar Roopendra Talekar · · 21 min read
Microsoft Fundraising & Engagement End of Support: 2026 Migration Guide
TALK TO AN ENGINEER

Planning a migration?

Get a free 30-min call with our engineers. We'll review your setup and map out a custom migration plan — no obligation.

Schedule a free call
  • 1,500+ migrations completed
  • Zero downtime guaranteed
  • Transparent, fixed pricing
  • Project success responsibility
  • Post-migration support included

Microsoft Fundraising & Engagement End of Support: 2026 Migration Guide

Microsoft Fundraising and Engagement (F&E) reaches end of support at 11:59 PM Pacific Time on December 31, 2026 (learn.microsoft.com). After that date, there are no security patches, no bug fixes, and no technical support from Microsoft. Separately, from February 1, 2027, Microsoft will stop engineering support for select nonprofit solutions and move them to an open-source and partner-led model (learn.microsoft.com). Microsoft has not said which solutions that notice covers.

For nonprofit CTOs and IT directors, this timeline forces a hard transition. F&E is not a standalone application — it is a purpose-built fundraising layer that requires Dynamics 365 Sales Enterprise (learn.microsoft.com) and uses the Common Data Model for Nonprofits within Dataverse. Microsoft's notices say support ends, not that the application shuts off. The security fixes and compatibility work needed to run it safely in production are what stop.

If you are running F&E today, about six weeks remain before support ends. That is enough time for the data migration itself, which takes days. It is not much time to select a new platform and rebuild your donor management workflows if you have not started. This guide covers what is actually ending, what data has to move, the realistic target platforms, and how to sequence the work so your fundraising operations stay intact.

What exactly is being retired?

Microsoft Fundraising and Engagement is the purpose-built nonprofit fundraising layer that runs on top of Dynamics 365 Sales Enterprise and Microsoft Dataverse. It is not the same thing as Dynamics 365 itself. Only the F&E application layer is going away — Dataverse, Dynamics 365, and your Microsoft 365 licenses all continue to function.

That distinction matters because it shapes your migration path. If you stay within the Microsoft ecosystem, your data already lives in Dataverse and you are remapping schema, not exporting and re-importing across platforms.

Microsoft announced the retirement in July 2024. Support continues through December 31, 2026, critical security issues are addressed until then, and no product enhancements will be made. Licensing for new customers ended on December 31, 2024.

The February 1, 2027 notice is a separate announcement about select Microsoft nonprofit solutions, and Microsoft does not list which ones it covers. For F&E, the date that matters is December 31, 2026. Dataverse itself remains supported, but the msnfp_ tables, plugins, and Azure services behind F&E have no Microsoft-backed maintenance path after that date.

Warning

After December 31, 2026: No security patches, no bug fixes, no Microsoft-assisted support. You will be running unsupported software that processes donor payment data — a compliance exposure that auditors and payment processors may flag.

What breaks if you do nothing after December 31, 2026?

After December 31, 2026, Microsoft will no longer implement security updates for Fundraising and Engagement, and there will be no further technical support for the solution. In practice, that means:

  • Payment processing risk. F&E integrates with the Stripe, Moneris, and iATS payment gateways, and Microsoft already states that it gives no guidance on PCI DSS validation of the solution (learn.microsoft.com). PCI DSS expects known vulnerabilities to be patched, so a payment integration that no longer receives security fixes becomes a question for your PCI assessor and your processor.
  • Compliance exposure. Nonprofits handling donor PII and payment card data under PCI DSS, GDPR, or state privacy laws (CCPA, state charitable solicitation statutes) will find it harder to demonstrate "appropriate technical and organisational measures" when the underlying software receives no security updates. GDPR Article 32 specifically requires "a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures" — which is hard to show for software that no longer receives security fixes.
  • Integration decay. F&E relies on Azure services for features such as recurring gift processing and automated financial summaries (learn.microsoft.com). Microsoft retires Azure service versions on independent schedules, and after support ends nobody at Microsoft updates F&E to keep up with those changes.
  • No bug fixes. After 11:59 PM Pacific Time on December 31, 2026, all technical support ceases. While the software may continue to function initially, there will be no further enhancements or fixes for any defects that emerge.

The end-of-support deadline also functions as a forcing function to clean your data — something most organizations postpone indefinitely. Duplicate donors, missing emails, inconsistent giving categories, old household structures, and campaign names that changed over time are endemic to nonprofit datasets. If this data moves without cleanup, the new CRM inherits the same problems, and AI tools like Dynamics 365 Copilot will hallucinate rather than generate useful insights.

What data has to move? The 8 core workloads

Migrating off F&E is significantly more complex than a standard B2B CRM migration. Nonprofit data models are highly relational. A single $50 donation is rarely just a line item — it is tied to a specific donor ("constituent" in nonprofit CRM terminology, meaning any individual, household, or organization that has a relationship with your organization), restricted to a specific fund designation, attributed to a specific marketing appeal, and linked to a legal tax receipt.

F&E and the Common Data Model for Nonprofits it builds on store nonprofit-specific records in Dataverse tables prefixed with msnfp_, such as msnfp_transaction, msnfp_donorcommitment, and msnfp_paymentschedule. They also add custom columns with the same prefix to standard Dynamics 365 tables such as Contact and Account.

To safely deprecate F&E, you must extract and map the following eight data workloads.

1. Constituents (Contacts and Accounts)

In F&E, constituents are standard Dynamics 365 Contact records for individuals and Account records for organizations and households (learn.microsoft.com). You must extract individual donors, household groupings, and organizational funders, preserving the exact relationship structures. Standard CSV exports often flatten these hierarchies, severing the link between a spouse and a household account.

2. Donations and transactions

The msnfp_transaction table holds the financial history of your organization — one-time gifts, pledge payments, and in-kind donations. Extracting this data requires handling two donor lookups: in the Common Data Model for Nonprofits, a transaction points at a Contact record (an individual) or an Account record (a foundation or organization) through separate lookup columns (github.com). If your extraction method does not carry the right lookup and its GUID forward, the transaction will be orphaned in the target system with no valid donor link.

3. Recurring gifts and payment schedules

Migrating recurring gifts (msnfp_donorcommitment and the associated msnfp_paymentschedule records) means moving future revenue expectations. You must map the frequency, amount, next payment date, and status of every active recurring gift.

CRM data migration moves the schedule metadata; it does not move actual credit card tokens. Token migration is a separate PCI-compliant process that must be coordinated directly between your old and new payment processors. Stripe, for example, transfers card data only to another PCI DSS Level 1 processor, as an encrypted export that the new processor imports (docs.stripe.com). Without this process, every active recurring gift will fail on its next charge attempt. Contact your payment processor before you begin migration scoping, because the receiving processor has to qualify and the transfer needs coordination on both sides.

4. Designations

Designations dictate how funds are restricted. When a donor gives to the "2025 Clean Water Initiative," that restriction must survive the migration for accounting and compliance purposes. You must migrate the master list of designations and ensure every historical transaction remains hard-linked to its correct restricted fund. Failure here creates reconciliation problems between the CRM and your accounting system (for example, Intacct or Sage) that can take months to resolve.

5. Campaigns and appeals

F&E organizes fundraising efforts hierarchically: a master Campaign contains multiple Appeals (e.g., a direct mail drop and an email blast), each with Packages (learn.microsoft.com). Marketing efforts are tracked at each level of this hierarchy. Migrating this data requires preserving the parent-child relationships so that historical ROI reporting remains accurate in the new system. Flattening the Campaign → Appeal → Package hierarchy into a single-level structure during migration destroys your ability to run historical performance comparisons by channel.

6. Events

Event data includes the event master record, ticketing levels, registrations, sponsorships, and attendance history. If your organization hosts annual galas, preserving the historical attendance record of major donors is a strict requirement for major gift officers — knowing that a donor has attended every gala for eight years is information that informs ask strategy.

7. Memberships

For organizations with membership models (museums, associations, botanical gardens), membership tiers, start dates, expiration dates, and renewal histories must be mapped accurately. A lapsed membership must retain its historical status rather than defaulting to active during import — otherwise your membership retention reporting becomes unreliable from day one.

8. Gift-aid and tax-receipt history

Tax compliance requires an immutable audit trail. You must migrate receipt records, and the receipt stacks F&E uses to number them, and maintain their exact relationship to the original transactions. The IRS expects a written acknowledgment for gifts of $250 or more (irs.gov), and the CRA requires each official donation receipt to carry a unique serial number (canada.ca). You must be able to show which receipt was issued for which transaction on which date. Receipt numbers must not reset or duplicate during migration.

Info

Don't forget the custom columns on standard tables. F&E adds msnfp_-prefixed fields to Contact, Account, and other core Dynamics 365 entities. You can search for msnfp in the Columns section of any standard table in the Power Apps maker portal to identify which columns were added by Fundraising and Engagement or the Common Data Model for Nonprofits. If your target system is off-platform, these columns need explicit mapping or you lose donor-level metadata like lifetime giving summaries, engagement scores, and communication preferences.

Cross-platform schema mapping reference

The table below maps the most critical F&E tables to their nearest equivalents in Salesforce's Nonprofit Success Pack (NPSP) and Blackbaud Raiser's Edge NXT. Names in code format are confirmed in Microsoft's Common Data Model for Nonprofits. Check the schema names of the others in your own environment. Migration complexity is rated Low (direct field mapping), Medium (structural transformation required), or High (data model redesign required).

F&E table Description Salesforce NPSP Equivalent Blackbaud RE NXT Equivalent Migration Complexity
msnfp_transaction Gift/donation records npe01__OppPayment__c / Opportunity Gift record Medium
msnfp_donorcommitment / msnfp_paymentschedule Pledges and recurring gift schedules npe03__Recurring_Donation__c Pledge/Recurring Gift High
msnfp_designation Restricted fund definitions npsp__General_Accounting_Unit__c Fund Low
msnfp_designatedcredit Payment-to-fund allocation (designation credit) npsp__Allocation__c Gift fund distribution Medium
Receipt Tax receipt records Custom object (no native equivalent) Receipt record High
Event Event master records Campaign (with workarounds) Event Medium
Event registration Event attendance CampaignMember Event registration Medium
msnfp_membershipcategory Membership tier definitions No native equivalent Membership program High
msnfp_membership Individual membership records No native equivalent Membership record High
Appeal Appeal within a campaign Campaign (child) Appeal Low
Package Package within an appeal No direct equivalent Package Medium
Gift batch Batch of gifts entered together No native equivalent Batch Medium

Note on Salesforce naming: The object API names in the table above come from the NPSP managed package. Salesforce's newer nonprofit product, Agentforce Nonprofit (formerly Nonprofit Cloud, renamed in December 2025), is a separate product with its own data model (salesforce.com). Verify current API names against your Salesforce org's schema before mapping.

Note on Blackbaud: Raiser's Edge NXT uses a proprietary API (SKY API) with its own object model. The equivalents above are conceptual; actual field mapping requires the RE NXT Data Dictionary.

Three migration paths compared

Your choice depends on whether you want to stay in the Microsoft ecosystem, move to Salesforce, or leave both platforms entirely.

Decision matrix

Factor Dynamics 365 Native Replacement Salesforce Nonprofit Cloud Standalone Nonprofit CRM
Data migration complexity Low — Dataverse-to-Dataverse schema remapping High — full cross-platform ETL High — full cross-platform ETL
Automation rebuild effort Low–Medium — Power Automate flows often portable High — rebuild in Salesforce Flow Medium–High — platform-dependent
Existing Microsoft 365 integration Native Requires connectors Requires connectors
Nonprofit-specific data model Varies by ISV Strong (NPSP object model) Varies by platform
Best fit org size SMB to enterprise Mid-market to enterprise SMB to mid-market
Relative licensing cost Low if Microsoft licenses retained Medium–High Low–Medium

Path 1: Stay on Dynamics 365 with a partner-built nonprofit layer

Several partner products built on Dynamics 365 and Dataverse target F&E customers:

  • StratusLIVE 365 — Built on Microsoft Dynamics 365 and the same Dataverse platform as F&E, covering donor management, gift processing, events, grants, and corporate giving (stratuslive.com). Because it shares the Dataverse platform with F&E, the data migration is a schema-mapping exercise within the same infrastructure rather than a cross-platform export.
  • SylogistMission CRM — Sylogist describes itself as the co-builder of F&E. Its product runs on Dynamics 365 Sales Enterprise and offers an in-app migration for F&E customers (sylogist.com).
  • Configured Dynamics 365 Sales — Work with a Microsoft partner to define a Dynamics 365 Sales configuration that meets your fundraising needs. This approach requires the most implementation effort but carries no dependency on a third-party ISV's product roadmap.

Why this path is simplest for data migration: Your records already live in Dataverse. A Dynamics-native replacement reads from the same underlying platform. The work is mapping msnfp_ tables to the new application's schema, mainly through the Dataverse Web API — not extracting, transforming, and loading across a network boundary.

Path 2: Move to Salesforce Nonprofit Cloud (Agentforce Nonprofit)

This is a full cross-platform migration: export from Dataverse, transform to Salesforce's object model, import via the Salesforce Bulk API or Data Loader.

Key technical friction points:

  • Data model differences — Dynamics 365 uses Account/Contact as primary records; Salesforce Nonprofit Cloud uses a Person Account model (or the Household Account model in NPSP). This is not a cosmetic difference — it affects how every downstream report, workflow, and integration is structured. Get this mapping wrong and constituent deduplication and household rollup reporting break.
  • Option set translation — Dynamics 365 option sets (picklists with integer values) must be translated to Salesforce picklist values (string-based). Numeric option set codes do not transfer literally, so every option set needs an explicit value mapping table.
  • Power Automate flows — Flows that touch other Microsoft systems (Teams notifications, SharePoint document creation, Outlook task generation) must be rebuilt in Salesforce Flow or replaced with middleware like MuleSoft or Zapier.
  • Document references — SharePoint-linked documents stored in F&E are references (URLs to SharePoint), not embedded files. Document migration is a separate project from data migration and typically requires a SharePoint-to-Salesforce Files migration tool.
  • Card token migration — See the recurring gifts section above. Token migration between payment processors must be arranged independently of the CRM migration.

Confirm current product naming and licensing with Salesforce before scoping. NPSP and Agentforce Nonprofit (formerly Nonprofit Cloud) are different products with different data models.

Path 3: Move to a standalone nonprofit CRM

If you are leaving the Microsoft ecosystem entirely, platforms targeting different organization sizes include:

  • Enterprise (100,000+ constituents): Blackbaud CRM, Blackbaud Raiser's Edge NXT
  • Mid-market (10,000–100,000 constituents): Virtuous, Bloomerang, Neon CRM
  • SMB (under 10,000 constituents): Bloomerang, Bonterra (formerly EveryAction), Little Green Light

This path requires a full data export from Dataverse (via API or structured export), transformation to match the target schema, and import via the target platform's API or bulk loader. It is the highest-effort option for data migration but may be the right call if your team has outgrown the Microsoft stack or needs fundraising-specific features (major gift pipeline management, grant tracking, volunteer management) that a configured general CRM cannot match without significant customization.

The F&E data extraction playbook

Regardless of which target platform you choose, the extraction side starts the same way.

Step 1: Audit your F&E footprint

Before you export anything, inventory what is actually in your environment:

  1. Count records per entity. Query Dataverse for row counts on every msnfp_ table. Pay special attention to msnfp_transaction (donations), msnfp_donorcommitment (pledges), and msnfp_paymentschedule (recurring gifts) — these are often the largest tables and the highest-risk for data loss.
  2. Identify custom columns on standard tables. Check Contact, Account, Opportunity, and Campaign for any msnfp_-prefixed columns in the Power Apps maker portal under Table → Columns. These hold donor-level metadata that standard Dynamics export tools will not flag as F&E-specific.
  3. Map integrations. Document every Azure service connection, payment gateway connection (Stripe, Moneris, or iATS), and Power Automate flow that touches F&E data. These do not migrate automatically.
  4. Flag data quality issues. Run deduplication analysis on Contact records. Identify orphaned transactions (gifts linked to deleted contacts via inactive GUIDs). Audit designation codes for consistency. These issues compound during migration if not resolved in the source first.

Step 2: Choose your export method

Preference order: Dataverse Web API > Azure Synapse/Fabric Link > Configuration Migration Tool > CSV. CSV is the last resort.

  • Dataverse Web API (preferred) — The Dataverse Web API provides programmatic access to every table and column, supports server-side pagination ($skiptoken), and handles relationships via stable GUIDs. This is the highest-fidelity extraction method. Record GUIDs stay intact, preserving referential integrity across all tables.

    Service Protection API Limits: Microsoft throttles Dataverse API requests to protect the environment. The default limits apply per user and per web server: 6,000 requests in a 5-minute sliding window, 20 minutes (1,200 seconds) of combined execution time in that window, and 52 or more concurrent requests. High-volume extractions must honor the Retry-After header and retry 429 Too Many Requests responses. Because the limits apply per user, run the extraction under a dedicated application user so it does not compete with staff.

  • Azure Synapse Link / Microsoft Fabric Link for Dataverse — For large datasets (millions of transaction rows), continuous export to Azure Synapse Analytics or Azure Data Lake Storage gives you a staging layer to transform data before loading into the target. Because Dataverse pushes the changes, the initial bulk extraction does not run through the Web API's service protection limits.

  • Configuration Migration Tool — Microsoft built the Configuration Migration Tool to move configuration data between environments, and says configuration data is different from end-user data such as accounts and contacts. Use it for reference tables such as designations or membership categories in a Dataverse-to-Dataverse move, not for your gift history.

  • CSV export — last resort. CSV exports strip the metadata required to rebuild complex relationships. When you export a transaction via CSV, the donor lookup column exports as a display name string (e.g., "John Doe"). If you have fourteen donors named John Doe, the target system cannot determine which one made the donation. Additional problems: the lookup's target table is lost, special characters in donor names break encoding in many import tools, and manual re-linking is error-prone at scale.

Step 3: Transform and validate

Map every source field to a target field. For cross-platform moves, this means:

  • Translating Dynamics 365 option set integer values to target platform string values using an explicit mapping table
  • Converting Dataverse GUID lookups to external ID references the target platform can resolve
  • Restructuring hierarchies like Campaign → Appeal → Package into the target's equivalent structure
  • Resolving donor lookups (determining whether a gift points to a Contact or an Account) before export

Validation must include:

  • Record-count parity — Same number of records in source and target, per entity
  • Field-level checksums — Spot-check monetary totals (total gifts should sum identically), date ranges, and key text fields
  • Referential integrity — Every transaction links to a valid constituent and designation in the target
  • Giving history reconciliation — Lifetime giving per constituent in the target matches the source; run this check on your top 100 donors by giving volume

Step 4: Delta sync and cutover

During the gap between your bulk migration and go-live, new donations will land in F&E. Run a delta sync to capture any records created or modified after the initial extract timestamp. Keep F&E operational during this period so your source system stays live until the new platform is confirmed accurate.

Nonprofit-specific data traps

These edge cases appear repeatedly in nonprofit CRM migrations and are frequently underestimated during scoping:

  • Soft credits and matching gifts. F&E records a soft credit as a transaction for a donation a constituent influenced but did not make, such as a matching gift (learn.microsoft.com). The relationship model does not map 1:1 to every target platform. NPSP uses its own soft credit objects, and Blackbaud RE NXT handles this through gift attribution. Map your soft credit logic explicitly before migration, not during.
  • Recurring gift schedules mid-cycle. Migrating a recurring gift that is mid-schedule requires preserving both the payment history (completed msnfp_transaction records) and the future schedule (the msnfp_paymentschedule record with its frequency and next payment date). If the new platform regenerates the schedule from the commitment start date, donors may be double-charged or skipped depending on where in the cycle the migration falls. Validate active recurring gift state against the new platform's schedule logic before go-live.
  • Tax receipt numbering. Canadian official donation receipts need a unique serial number, and F&E numbers receipts through receipt stacks. UK Gift Aid Declarations and Gift Aid Returns also need to move with their history. If receipt numbers reset during migration, your finance team must reconcile discrepancies manually. Lock your receipt number sequence in the source system before migration and initialize the target system's sequence to continue from the last issued number.
  • Event registration history. Old event data is often the largest table by row count but lowest priority for active use. Decide explicitly whether you need full event history in the new system or whether historical event data can be archived to a data warehouse (Azure Blob, S3, BigQuery).
  • Designation hierarchies. F&E lets you nest designations under campaigns and appeals. If your target platform uses a flat fund structure (common in Blackbaud RE NXT and Bloomerang), you need a mapping table that preserves the original hierarchy in a custom field or external reference column so that historical reporting can reconstruct it.
  • Payment gateway callbacks. If any webhook or callback in your Stripe, Moneris, or iATS account points at F&E or its Azure services, update it to point to the new platform. If you decommission F&E first, payment confirmations can fire against a dead endpoint and gifts may not post correctly.

How long does a nonprofit CRM data migration take?

There are two clocks running in parallel, and confusing them causes almost every timeline dispute.

Clock 1: The data migration. This is the work of extracting records from one system, mapping and transforming them, validating field-level accuracy, and loading them into the target. For most nonprofit CRM datasets, this phase completes within 1–5 business days, depending on data volume, complexity, and API rate limits.

Small datasets under 10,000 records can finish in under 24 hours.

The bulk historical load runs on the working days before go-live while your team keeps working in F&E. Go-live is a Monday morning: F&E is frozen before the working day starts, a final delta of changed records runs in about 30 minutes, and staff log in to the new system that day.

Clock 2: The replatform project. This includes selecting and licensing the target platform, configuring it, rebuilding automations and reports, training staff, and going live. That is your project, run by your team or implementation partner, and it usually takes far longer than the data migration. The data migration is a defined phase within this larger effort, not a substitute for it.

If you have not started scoping, start now. The data migration itself takes days, but field mapping sign-off and sample migrations need your team's time before December 31, 2026.

Danger

Year-end fundraising season collides with the deadline. Support ends on December 31, the same weeks many nonprofits run their year-end appeals. Decide now whether to go live on a Monday in early December, before the final giving push, or to run year-end on F&E and accept a short period on unsupported software before a January go-live. Make that call with your finance and security teams, not by default.

The timeline that works

Working backward from the December 31, 2026 deadline:

When What
Now – late November 2026 Confirm the target platform. Data audit: count records, identify custom columns, map integrations, flag quality issues. Book migration scoping.
Late November – early December 2026 Field mapping signed off. Sample migrations run and validated against F&E.
The working days before go-live Bulk historical load runs while staff keep working in F&E.
A Monday go-live F&E frozen before the working day, final delta of changed records, staff log in to the new platform.
December 31, 2026 F&E support ends. Keep the Dataverse environment read-only as an archive only if you need it.

This timeline assumes your replatform project (platform selection, configuration, automation rebuilds, staff training) is already underway. The data migration is a defined phase within that larger effort — it cannot substitute for it and cannot begin productively until the target environment exists.

What this means for your Microsoft licensing

Only the Fundraising and Engagement application layer is retiring. Dataverse, Dynamics 365, and Microsoft 365 continue. If you stay on a Dynamics 365-native solution, your existing licenses likely still apply. If you leave the Microsoft ecosystem entirely, review your enterprise agreement — you may be able to reduce your Dynamics 365 Sales Enterprise seat count, but Microsoft 365 licenses (Exchange Online, Teams, SharePoint) are a separate SKU and commitment.

As of November 2026, Microsoft lists Dynamics 365 Sales Enterprise for eligible nonprofits at a discounted $23.80 per user per month (microsoft.com). Confirm whether your discounted pricing carries over to your chosen target platform before making a platform decision — some ISV solutions sold through the Microsoft ecosystem carry their own licensing fees on top of the Dynamics 365 base license.

How ClonePartner handles nonprofit CRM data migrations

ClonePartner specializes in CRM-to-CRM data migration as an engineering discipline, with 1,500+ successful migrations and 500+ integrations built. Our process for F&E migrations follows a defined sequence:

1. Scoping call and fixed-price proposal

We start with a free 30-minute scoping call to understand your F&E configuration, custom fields, integration footprint, and target system. This call produces a fixed-price proposal scoped to your specific data volume and complexity.

2. Migration mapping and data audit

A dedicated migration engineer — not a shared ticket queue — takes ownership of your project. That engineer maps the msnfp_ tables to your new schema, audits the source data for quality issues (duplicates, orphaned records, inconsistent designation codes), and flags anything that requires remediation before extraction begins.

3. Sample migrations

We extract a representative subset of your F&E data via the Dataverse Web API and push it to your target system's sandbox. You validate the relationships — confirming that a constituent's recurring gift is attached to the correct restricted designation and the correct tax receipt. We perform unlimited sample migrations until the data mapping is confirmed accurate.

4. Full migration and validation

Once the sample is approved, we execute the full extraction from Dataverse and push it to the target. Multi-stage validation compares record counts and financial checksums between source and target to confirm referential integrity before you go live.

5. Delta sync

After the bulk load, we execute delta syncs to capture records created or modified after the initial extract. This keeps F&E operational as your source of truth until go-live, when the final delta brings the target fully current.

Pricing

One fixed price per project, starting at $500. No hourly billing, no per-record metering, no change orders. Pricing is determined by data volume, schema complexity, and the specific source/target platform combination.

Security and compliance

ClonePartner is independently audited for SOC 2 Type II and ISO 27001 compliance. We maintain safeguards for GDPR, CCPA, and HIPAA. Data is encrypted using AES-256 at rest and TLS 1.2+ in transit. Staging databases auto-purge within 30 days of project close. Assurance reports are available under NDA through our Trust Center at trust.clonepartner.com.

Start planning now

The retirement of Microsoft Fundraising and Engagement requires immediate decisions. With support ending on December 31, 2026, the platform choice cannot wait, and a full replacement CRM — particularly for enterprise nonprofits moving to Salesforce or Blackbaud — may not be live by then. Moving the data early, onto a target you can keep building on, keeps your giving history off unsupported software.

Do not let data migration become an afterthought. Historical data mapping is consistently the highest-risk phase of any CRM implementation. The key technical decisions — resolving donor lookups correctly, maintaining strict relational links between constituents, transactions, and designations, handling token migration for recurring gifts, and preserving tax receipt numbering continuity — must be scoped explicitly before your implementation partner begins platform configuration.

The organizations that transition successfully will be those that treat data migration as a parallel engineering track alongside the replatform project, not a final step scheduled for the week before go-live.

For broader context on Microsoft's infrastructure changes, see our Dynamics CRM On-Premise End of Support guide, the Microsoft 2026 End-of-Support Timeline, or the 2026 Dynamics 365 Migration Handbook for tools and costs.

Frequently Asked Questions

When does Microsoft Fundraising and Engagement end of support?
Microsoft Fundraising and Engagement support ends at 11:59 PM Pacific Time on December 31, 2026. After that date, there are no security patches, no bug fixes, and no technical support. Microsoft announced the retirement in July 2024 and stopped licensing the solution to new customers on January 1, 2025. Separately, from February 1, 2027, Microsoft ends engineering support for select nonprofit solutions without naming which ones.
What replaces Microsoft Fundraising and Engagement for nonprofits?
Microsoft's retirement notices on Learn do not name a replacement product. Partner products built on Dynamics 365 and Dataverse, such as StratusLIVE 365 and SylogistMission CRM, target F&E customers, or a partner can configure Dynamics 365 Sales for fundraising. Nonprofits can also move to Agentforce Nonprofit (formerly Salesforce Nonprofit Cloud), Blackbaud Raiser's Edge NXT, or other standalone nonprofit CRMs.
Does Dynamics 365 still work after F&E is retired?
Yes. Only the Fundraising and Engagement application layer is retiring. Dataverse, Dynamics 365, and Microsoft 365 licenses all continue to function. Your data remains in Dataverse — you need a new application layer to manage it, not a new underlying platform.
How long does it take to migrate data from Fundraising and Engagement?
The data migration itself typically takes 1–5 business days depending on volume, complexity, and API rate limits. Small datasets under 10,000 records can finish in under 24 hours. Rebuilding your fundraising processes on the new platform is a separate project that you or your implementation partner run, and it usually takes longer than the data move.
Can I export my Dynamics 365 donor data to CSV for migration?
CSV exports are the least preferred option because they flatten relational hierarchies and strip away the unique GUIDs needed to resolve polymorphic lookups. If you have multiple donors with the same name, CSV exports cannot distinguish between them. Extracting data via the Dataverse Web API preserves referential integrity and is strongly recommended.

More from our Blog

Dynamics CRM On-Premise End of Support 2026: The Master Guide
Microsoft Dynamics 365

Dynamics CRM On-Premise End of Support 2026: The Master Guide

The final deadline for Dynamics CRM 2016 (v8.2) Extended Support is January 13, 2026. After this date, Microsoft will no longer provide security updates or technical support for on-premise deployments. This guide answers the most critical transition queries for IT leaders and stakeholders.

Raajshekhar Rajan Raajshekhar Rajan · · 5 min read