The Nonprofit CRM Migration Playbook: 7 Decisions to Make Before You Touch Data

Most CRM migrations start with a spreadsheet and a deadline. 

The team pulls exports, cleans a few columns, and hopes the new system will magically create clarity. 

It won’t. 

A Microsoft-based CRM can absolutely unify operations and improve constituent relationships, but only if you treat migration like an operating model upgrade, not a data move.  

Here’s the playbook we use when a nonprofit wants to move to Microsoft-based CRM architecture (Dynamics 365 + Power Platform) and keep adoption strong long after go-live. 

Decision 1: What are you migrating for?

Pick one primary outcome. Not five. 

Examples: 

• “We need trusted fundraising and retention reporting.” 

• “We need consistent follow-ups across fundraisers.” 

• “We need fewer systems and less manual admin work.” 

When everything is a priority, the CRM becomes a junk drawer. A single primary outcome gives you a filter for every decision that follows. 

Decision 2: What is your constituent “source of truth”? 

In Microsoft-based CRM environments, you can design data around constituent-first operations and build apps for fundraising, programs, and impact on top. The Microsoft nonprofit accelerator, for example, is built on Dataverse and a nonprofit data model to support scenarios like fundraising and program delivery.  

Before you migrate, decide: 

• Where will a constituent record live? 

• Who “owns” constituent updates? 

• What fields are required vs optional? 

• What counts as a duplicate? 

This is not admin trivia. It is the difference between “the CRM is working” and “the CRM is a debate.” 

Decision 3: What data is worth bringing forward? 

Nonprofits often try to migrate everything because it feels safer. 

In reality, migrating “everything” often recreates the same clutter that made the old system hard to use. 

A smarter approach: 

• Bring forward what supports current operations and reporting 

• Archive what is legally necessary but operationally noisy 

• Document what you chose and why 

A clean system that people use beats a perfect museum of historical clutter. 

Decision 4: What are your definitions? 

If you want board-ready reporting, you need a few shared definitions that never drift: 

• What counts as a donor? 

• What counts as retained? 

• What counts as pipeline? 

• What counts as “active” stewardship? 

Microsoft’s nonprofit solutions emphasize data-informed decisions and impact reporting, but those outputs depend on consistent definitions.  

Write the definitions down. Put an owner next to each one. Make them part of training. 

Decision 5: What workflows must be non-negotiable?

If follow-ups are inconsistent today, your CRM needs to make consistency the default. 

Pick 3–5 workflows that will define success: 

• Major gift qualification and next steps 

• Renewal cadence and reminders 

• Event follow-up routine 

• Gift processing checkpoints 

• Stewardship touches (thank you, update, ask) 

Then build them intentionally. Microsoft’s nonprofit accelerator exists partly to help partners build applications centered around fundraising and program scenarios.  
The key is not the tool. The key is the routine. 

Decision 6: What will you integrate, and what should stay separate? 

Integrations feel like progress. Too many integrations become fragility. 

Before connecting systems, decide: 

• What data must move automatically? 

• What can stay manual because it is low volume and high risk? 

• Who will monitor data flow and exceptions? 

Make integrations serve one of your primary outcomes. If they don’t, skip them. 

Decision 7: What is your adoption plan? 

Adoption is not training day. It’s the first 90 days. 

A practical adoption plan includes: 

• Role-based training (fundraisers, ops, leadership) 

• Simple job aids (what to do, where to do it, how to do it) 

• Office hours 

• A governance routine (monthly review of duplicates, missing fields, reporting issues) 

Microsoft’s nonprofit ecosystem includes documentation and guidance across tools like Power Platform and Dynamics.  
Your adoption plan is where that guidance becomes real daily behavior. 

Closing thought 

A Microsoft-based CRM can give nonprofits powerful building blocks for fundraising, program delivery, and reporting.  
But migrations succeed when the nonprofit decides how it wants to work, then makes the system reflect that reality.