Skip to content

Microsoft Fundraising and Engagement Is Retiring

Microsoft Fundraising & Engagement retires Dec 31, 2026. Learn your migration options, timeline, and why StratusLIVE 365 is the natural upgrade path.

StratusLIVE10 min read

Key takeaway: Microsoft permanently retires Fundraising and Engagement (F&E) on December 31, 2026 at 11:59 PM PT. No extensions. No further enhancements. If your nonprofit runs on F&E, you need a migration plan now, not next quarter.

If your nonprofit runs its donor records and gift processing on Microsoft Fundraising and Engagement, this guide is for you. It covers what is happening, the paths open to you, how to judge a replacement, and how to plan the move from where you stand today.

December 31 is close, and it lands in the busiest days of year-end giving, the worst time to change systems. If you have not started, begin with scope: list what runs on F&E today and decide what has to move. Then set a cutover date your team can staff.

What Is Happening with Microsoft Fundraising and Engagement?

On July 15, 2024, Microsoft officially announced that its Fundraising and Engagement solution, the purpose-built nonprofit CRM module within Microsoft Cloud for Nonprofit, will be permanently retired on December 31, 2026.

Here is what that means in practical terms:

  • No new features or enhancements since July 2024: the platform is frozen
  • Security patches only will continue through December 2026
  • All technical support ends after 11:59 PM PT on December 31, 2026
  • No migration extension has been announced or is expected
  • Dataverse and Dynamics 365 continue: only the F&E layer is being removed

This is not a soft deprecation. Microsoft is fully sunsetting the product, meaning any organization still running F&E on January 1, 2027 will be operating an unsupported system with no security updates, no bug fixes, and no recourse for issues.

Why Is Microsoft Retiring F&E?

Microsoft has not provided a single public reason, but the context is clear. Fundraising and Engagement was part of Microsoft Cloud for Nonprofit, an industry cloud initiative that Microsoft has strategically refocused. Rather than maintaining a first-party nonprofit CRM, Microsoft is leaning into its partner ecosystem, encouraging ISVs (independent software vendors) to build purpose-built nonprofit solutions on top of Dynamics 365 and Dataverse.

This is actually positive news for nonprofits who felt constrained by F&E’s limited feature set. Purpose-built partner solutions like StratusLIVE 365 offer dramatically deeper functionality because they are built by teams who work exclusively with nonprofits, rather than as a side project within a massive enterprise software company.

Critical Timeline: Key Dates You Cannot Miss

DateEventImpact
July 15, 2024Retirement announcedNo new features; security updates and support continue through December 31, 2026
Oct–Dec 2026Year-end fundraising seasonScope and plan now; keep the cutover out of the busiest giving weeks
Dec 31, 2026F&E permanently retiredAll support ends at 11:59 PM PT
Jan 1, 2027+Unsupported systemNo security patches, no bug fixes, no help

If your cutover lands after December 31, plan for the gap. From January 1 until cutover, F&E runs without Microsoft security updates or support, so hold off on new customizations and put the cutover date on the calendar now.

Your Migration Options: What Are the Realistic Paths Forward?

Microsoft has identified several paths for F&E customers. However, not all paths are equal. Let us examine each option honestly.

This is the most natural migration path. Your organization already runs on Dynamics 365 and Dataverse. Your staff already knows the Microsoft ecosystem. Your data already lives in Dataverse. A Dynamics 365-native nonprofit CRM lets you keep everything that works and upgrade only the nonprofit layer.

Why this works best:

  • No new platform to learn: your team stays in the Microsoft environment they know
  • Data stays in Dataverse: no risky cross-platform data migration
  • Microsoft tools stay in place: Outlook, Teams, SharePoint, and Power BI keep working with your CRM
  • Licensing investments preserved: your Microsoft 365 and Dynamics 365 licenses still apply
  • Familiar admin tools: Power Platform, Microsoft Entra ID (formerly Azure AD), and security roles remain the same

StratusLIVE 365 is a nonprofit CRM built on Microsoft Dynamics 365. It was designed from the ground up for nonprofits and runs natively on the same Dataverse platform as F&E, so a move from F&E stays on the platform your team already runs.

Option 2: Move to a Completely Different CRM Platform

Some organizations will evaluate non-Microsoft CRM platforms like Salesforce Nonprofit Cloud, Bloomerang, Virtuous, or Blackbaud Raiser’s Edge NXT. This is a viable but significantly more complex path.

What this requires:

  • Full data migration from Dataverse to an entirely different database architecture
  • Re-integration of every connected system: accounting, email, website, events
  • Complete staff re-training on a new platform, new interface, new workflows
  • Loss of Microsoft ecosystem benefits: no native Outlook, Teams, or Power BI integration
  • New licensing costs on top of or instead of your existing Microsoft investment

For organizations deeply embedded in the Microsoft ecosystem, this path doubles migration complexity and cost. It may make sense for organizations already considering a broader technology shift, but for most F&E customers, it is the harder and more expensive route.

One more option from StratusLIVE itself. Ignite, the Active Intelligence Platform, is a separate product from StratusLIVE 365 and does not run on Dynamics 365. For an F&E organization that has decided to leave the Microsoft stack rather than stay on it, Ignite is the StratusLIVE path to evaluate: fundraising, finance, marketing, and engagement on one constituent record, with the migration verified in parallel before cutover.

Option 3: Build a Custom Solution on Raw Dynamics 365 Sales

Microsoft suggests customers can work with a partner to configure Dynamics 365 Sales for nonprofit use. While technically possible, this approach carries significant risk.

Challenges:

  • No nonprofit-specific data model: you must build donation tracking, gift processing, campaign management, and constituent management from scratch
  • Ongoing custom maintenance: every Dynamics 365 update may require re-testing your custom modules
  • No nonprofit community or roadmap: you are alone with your custom build
  • Higher long-term cost: custom development and maintenance typically exceeds packaged software

We recommend this option only for organizations with highly unique requirements that no packaged nonprofit CRM can address.

Why StratusLIVE 365 Is the Natural Upgrade Path from F&E

StratusLIVE 365 was purpose-built for nonprofits on the exact same platform as F&E: Microsoft Dynamics 365 and Dataverse. This is not a coincidence. It is by design. Here is why it matters:

CapabilityMicrosoft F&EStratusLIVE 365
PlatformDynamics 365 / DataverseDynamics 365 / Dataverse
Donor ManagementBasic constituent records360° donor profiles with engagement scoring, duplicate detection, household management
Gift ProcessingBasic donation entryFull gift processing with batch entry, recurring gifts, pledges, matching gifts, planned giving
Campaign ManagementLimitedMulti-channel campaigns with ROI analytics at every level
Online GivingNot includedStratusLIVE digital engagement: peer-to-peer, events, donation pages
AnalyticsBasic reportsEmbedded Power BI reporting, plus StratusLIVE IQ predictive segmentation for marketing
Events ManagementEvents with registration and seatingFull event setup, registration, volunteer assignments, reporting
Grants ManagementNot includedEnd-to-end grants: discovery, application, program management, accounting
Corporate Giving / CSRNot includedStratusLIVE Give at Work: workplace giving, matching gifts, volunteer tracking
Microsoft IntegrationNativeNative + deeper: Outlook tracking, Teams collaboration, Power BI dashboards, SharePoint
AI CapabilitiesNo new AI featuresMicrosoft Copilot in Outlook and Teams, on your constituent data (licensed through Microsoft)
Ongoing DevelopmentFrozen (no updates)Supported by StratusLIVE

The bottom line: StratusLIVE 365 keeps you on the same Microsoft platform your organization already uses and trusts.

Where the AI lives: on StratusLIVE 365, AI comes from Microsoft Copilot. It works on your Dataverse data inside Outlook and Teams, and you license it through Microsoft. Ignite’s AI agents belong to Ignite, a separate StratusLIVE platform, and do not run on StratusLIVE 365.

Step-by-Step: How to Migrate from F&E to StratusLIVE 365

How long the move takes depends on your user count, record volume, integrations, and data quality. The work runs in this order:

Phase 1: Discovery and Assessment

  • Audit your current F&E environment: document custom fields, workflows, integrations, reports, and data volumes
  • Identify data quality issues: duplicate records, incomplete fields, orphaned records
  • Map your requirements: what does your team actually use vs. what was configured but never adopted?
  • Engage stakeholders: fundraisers, data entry staff, finance, IT, and leadership all have migration input

Phase 2: Solution Design

  • Configure StratusLIVE 365 to match your operational workflows
  • Map F&E data fields to StratusLIVE 365 entities: constituent records, donations, campaigns, interactions
  • Design integration architecture: accounting system (e.g., Great Plains, Sage), website, email marketing
  • Plan report migration: identify which F&E reports to recreate and which to improve with Power BI

Phase 3: Data Migration

  • Extract and cleanse data from Dataverse (your data stays in Dataverse, so this is a schema migration, not a platform migration)
  • Run test migrations with a subset of records to validate mapping accuracy
  • Validate donor histories: ensure giving history, interactions, and campaign associations transfer correctly
  • Perform full migration with verification checkpoints

Phase 4: Testing and Training

  • User acceptance testing (UAT) with key staff from each department
  • Side-by-side validation: run both systems briefly to confirm data integrity
  • Role-based training: fundraisers, data entry, finance, and administrators each need tailored sessions
  • Create reference guides and quick-start documentation for your specific configuration

Phase 5: Go-Live and Optimization

  • Cutover to StratusLIVE 365 as your primary system
  • Decommission F&E components (Dataverse and Dynamics 365 remain)
  • Monitor adoption: track login rates, feature usage, and support ticket themes
  • Optimize and iterate: refine workflows after go-live based on how your team uses the system

Because both F&E and StratusLIVE 365 run on Dataverse, data migration is a schema mapping exercise, not a risky cross-platform export/import. This is the single biggest advantage of staying in the Microsoft ecosystem.

How to Evaluate Any F&E Replacement: Your Checklist

Regardless of which solution you consider, use these criteria to evaluate any potential F&E replacement:

Evaluation CriteriaWhy It MattersQuestions to Ask
Platform compatibilityMinimizes migration risk and preserves investmentsDoes it run on Dynamics 365 / Dataverse natively?
Nonprofit-specific designGeneric CRMs require expensive customizationWas this built for nonprofits or adapted from a sales CRM?
Data migration supportPoor migration = lost donor historyWhat is the migration process? What tools and support are included?
Integration ecosystemNonprofits depend on connected systemsDoes it integrate with our accounting, email, website, and payment processors?
Total cost of ownershipSticker price is not total costWhat is the 3-year TCO including licenses, implementation, training, and support?
Vendor track recordNonprofit CRM is a long-term partnershipHow long has this vendor served nonprofits? How many clients? Reference calls?
Product roadmapYour needs will evolveWhat is on the 12-month roadmap? How often are updates released?
Analytics and intelligenceThe future of fundraising is data-drivenWhat is included in the platform, and what costs extra?

Addressing Common Concerns About Migration

“We don’t have the budget for a migration right now.”

Consider the cost of not migrating. After December 31, 2026, you will be running an unsupported system. Any security vulnerability, data issue, or system failure will be entirely on your team to resolve, with no help from Microsoft. The cost of an emergency migration or a data breach in 2027 far exceeds the cost of a planned migration today.

“Our team is already overwhelmed.”

That is why the cutover date matters as much as the retirement date. A paced migration spreads the work across normal weeks. A cutover forced into late December asks for everything at once, in the busiest fundraising weeks of the year.

“What if we just keep running F&E after it’s retired?”

Technically, the software does not stop working on January 1, 2027. However, you will receive no security updates, no bug fixes, and no support. You will also fall behind on Dynamics 365 platform updates, creating increasing technical debt. Most critically, you will have no vendor support for donor data security, which is a serious liability for any organization handling PII and financial data.

“Our data is too messy to migrate.”

This is actually the best reason to migrate now rather than later. A well-managed migration includes a data cleansing phase that resolves duplicates, fills gaps, and standardizes records. You will emerge from migration with cleaner, more useful data than you have today. Delaying only makes the problem worse.

Frequently Asked Questions

Can we continue using Dataverse and Dynamics 365 after F&E retires?

Yes. Microsoft is only retiring the Fundraising and Engagement application layer. Dataverse, Dynamics 365, and your Microsoft 365 licenses all continue. A Dynamics 365-native nonprofit CRM like StratusLIVE 365 installs on top of the same platform.

Will our existing data be lost?

No. Your data lives in Dataverse, which continues to operate. A migration to StratusLIVE 365 maps your existing data to the new application’s schema within Dataverse. Scoping decides whether the move happens in your current environment or in a clean one.

What sets the length of a migration?

It depends on your user count, record volume, integration surface, and how clean your data is going in. Because F&E and StratusLIVE 365 share the Dataverse platform, the data work is a schema mapping exercise rather than a cross-platform export. Ask any vendor to scope your specific environment rather than quoting a generic timeline.

Does StratusLIVE offer migration support?

Yes. The StratusLIVE team scopes your F&E environment first, then runs the migration to StratusLIVE 365 in planned phases, with your team validating the data before cutover. Contact StratusLIVE for a free migration assessment.

What about our custom reports?

F&E reports built with SSRS or Power BI can be recreated and often improved. StratusLIVE 365 includes built-in dashboards and full Power BI integration for advanced analytics.

Ready to start? Request a free F&E migration assessment and get a personalized migration roadmap.

Put the ideas to work.

See how Ignite turns strategy into capacity. 30 minutes. Live demo.