Mission-driven organisations deserve systems that support their work, not slow it down.
If you’re an NGO in the DACH region, you’re likely balancing ambitious goals with limited time, tight resources and increasing expectations around transparency and reporting. The right CRM can help but only if it’s implemented with a clear purpose, clean data and a realistic plan for adoption.
Microsoft Dynamics 365 can be a strong foundation for donor management, supporter engagement and operational reporting. This checklist is here to help you plan a Dynamics 365 CRM project that protects supporter data, supports recurring giving (including SEPA Direct Debit) and gives your team reporting they can actually use.
Who this checklist is for?
This guide is for NGOs, foundations and associations in Germany, Austria and Switzerland that are:
- Considering Microsoft Dynamics 365 as their CRM
- Replacing spreadsheets or a legacy donor database
- Struggling with inconsistent supporter data and unclear reporting
- Planning integrations across fundraising, communications and finance
If you’re early in the process, use this as a scoping tool. If you’re already mid-project, use it as a quick health check.
Step 1: Start with outcomes (not features)
Before you discuss modules, licences or integrations, agree what success looks like in plain language.
Common outcomes for NGOs include:
- A single, trusted view of each supporter and their giving history
- More reliable recurring donations and fewer payment failures
- Faster campaign reporting and clearer ROI
- Better coordination between fundraising, programmes and finance
- Stronger data governance and GDPR-aligned processes
A simple prompt that works well: what are the top 5 decisions your leadership team wants to make each month and what data would make those decisions easier?
Step 2: Run a focused requirements workshop (must-have vs nice-to-have)
A short, structured requirements workshop prevents scope creep later and helps you prioritise what matters.
Capture requirements across:
- Fundraising: campaigns, events, major donors, corporate partners
- Supporter journeys: email preferences, segmentation, engagement tracking
- Recurring giving: schedules, payment methods, failed payment handling
- Programmes: beneficiaries, outcomes, case notes (where relevant)
- Finance handoff: coding, reconciliation, audit trail expectations
- Reporting: board packs, operational dashboards, compliance reporting
Deliverable: a prioritised requirements list plus a first-pass process map.
Step 3: Audit your supporter data (and plan the migration)
Most CRM projects succeed or fail on data.
Before migration, assess:
- Duplicate records and inconsistent naming
- Household or organisation relationships (who is connected to whom)
- Missing contact details and outdated addresses
- Consent history and communication preferences
- Historical transactions and campaign attribution
- Data you should not migrate (obsolete, low-quality, non-compliant)
Minimum deliverables:
- A data dictionary (what each field means)
- A deduplication approach
- A migration plan with test cycles
- Clear ownership: who signs off the migrated data
Step 4: Design the fundraising workflow your team will actually use
Dynamics 365 should reflect how fundraising works in your organisation, not how a generic CRM demo looks.
Key questions:
- How will you track campaigns, appeals and events?
- How will you segment supporters and who owns the segments?
- How will you manage major donor pipelines?
- How will you handle corporate partnerships and sponsorships?
- Recurring giving via SEPA Direct Debit
- Clear handling of payment failures and supporter communications
Step 5: Plan donation receipts and the audit trail
Even if your finance system is separate, your CRM should support a clean audit trail.
Define:
- What data is required to issue donation receipts or confirmations?
- How you will store receipt status and references
- How you will handle corrections and cancellations
- How finance will reconcile CRM transactions to bank statements and accounting
Keep it simple: the goal is traceability and confidence, not complexity.
Step 6: Map integrations (website, email, finance, analytics)
Integrations are where CRM projects often get delayed.
Create an integration map covering:
- Website donation forms and lead capture
- Email marketing and supporter communications
- Finance, accounting or ERP
- Document management
- Power BI reporting
For each integration, define:
- What data moves between systems
- Direction (one-way or two-way)
- Frequency (real-time, daily, weekly)
- Ownership (who maintains it)
Step 7: Define security, roles and GDPR-aligned governance
You dont need to be a legal expert to build sensible governance. You do need clarity.
Decide:
- Who can view, edit and export supporter data
- How you will manage access for volunteers, temporary staff and partners
- What data is sensitive and needs extra controls
- Retention rules (what you keep, for how long, and why)
- How you will handle subject access requests and deletion requests
Practical rule: restrict export permissions. Most data leaks happen through downloads, not hacking.
Step 8: Build reporting that leadership will actually use
Start with a small set of dashboards that answer real questions.
Examples:
- Fundraising performance by campaign and channel
- Recurring giving health (new, retained, churned, failed payments)
- Major donor pipeline and next actions
- Programme outcomes (where applicable)
- Month-end reconciliation status
If youre using Power BI, agree the source of truth for each metric and document it.
Step 9: Create an adoption plan (training, champions, rollout)
A CRM implementation is a change programme.
Plan:
- Role-based training (fundraising, finance, leadership)
- A small group of CRM champions to support colleagues
- A phased rollout (pilot team first, then scale)
- A feedback loop for the first 68 weeks
Measure adoption with simple signals:
- Are people logging activities consistently?
- Are reports being used in meetings?
- Are fundraising processes faster and more reliable?
Common pitfalls (and how to avoid them)
- Trying to automate broken processes: fix the process first, then systemise it.
- Migrating everything: migrate what you trust and what you need.
- Underestimating change management: adoption is usually the real bottleneck.
- Unclear ownership: every process and dataset needs an owner.
- No definition of ‘done’: agree success criteria early.
Build or Buy?
Dynamics 365 CRM is a very comprehensive tool and comes with many building blocks to help NGOs. However, at the end of the day, it was designed for commercial organisations and therefore requires a fair bit of customisation to work for NGOs. Given that the richness of functionality comes at a cost, we often find that building a solution from scratch using Power Apps (a component of Microsoft’s Power Platform) is a more cost effective approach, as the Microsoft licencing is much cheaper.
We have taken that one step further by building out a repeatable set up products – our Rapsi 365 suite. This consists of:
- Fundraising Management
- Grant Management
- Financial Management
These are built in Power Apps, giving a significant headstart in functionality, rather than starting with a blank page.
Next step: a practical CRM readiness call
If youre planning a Dynamics 365 CRM (or Power Platform) project for an NGO in the DACH region, we’d love to help you pressure-test your plan.
In a short readiness call, we’ll cover:
- Your outcomes and constraints
- Data and migration risks
- Integration complexity
- A realistic phased rollout approach
