Dynamics 365 for Nonprofits and Associations: Platform Fit Assessment
Membership, donor and grant management on Dynamics 365 with the Nonprofit Accelerator: what it really gives you, what you have to build, and how to tell whether you should buy something else instead.
Dynamics 365 with the Nonprofit Accelerator can run membership, donor and grant management for a nonprofit or a membership association, but only once you know what the accelerator actually gives you. It gives you a data model on Dataverse for constituents, donations, fundraising, awards and program delivery. It does not give you membership. Dues, tiers, renewal cycles, chapters, benefits and a join and renew portal are a build on top of the platform rather than a module you switch on. This page is a fit assessment against your budget and your internal skills, then the phased path we would implement. Where a purpose built association product is the better buy, we say so and explain how to tell.
The short answer
- What the platform gives you. Dynamics 365 Customer Engagement on Dataverse, extended by the free Nonprofit Accelerator solution, which carries the Common Data Model for Nonprofits: constituents and households, donor commitments and transactions with designations, fundraising campaigns and appeals, awards and the grant lifecycle, and program delivery with results and indicators. Around it sit Power Apps, Power Automate, Power Pages, Power BI and custom PCF controls.
- What it does not give you. A membership system. There is no dues engine, no renewal cycle with notices and a grace period, no membership tier with entitlements, no chapter or section structure, and no payment gateway. For an association, that is most of the requirement, and it is configuration and code on Dataverse rather than a switch. Confirm this against the release notes of the accelerator version you install, since it does change.
- What decides fit. Not features. Whether you will have one internal owner who holds the system after go live, and whether your constituents genuinely overlap, meaning the same person is a member and a donor and a volunteer and an event attendee. If both are true, the platform pays back. If neither is, a purpose built association or fundraising product will serve you faster and cheaper and we will tell you so.
- How we would start. A fit assessment of roughly two to three weeks, fixed scope and fixed price, that ends in a written verdict against your own membership rules and your own data, including the verdict that says do not buy this. Then a phased build that puts the renewal cycle in early, because that is where the staff time actually goes.
If the question underneath yours is whether a platform of this size is right for a team of your size at all, our comparison of Dynamics 365 against Pipedrive and HubSpot for small teams answers it first, in commercial terms.
What the Nonprofit Accelerator actually is
Most of the confusion in this sector comes from one word. An accelerator is not a product. It is a head start on a data model, published free, that you install and then extend. Knowing exactly what is inside it is the difference between a plan that holds and a business case that falls apart in month two.
It is a solution you install, not a product you buy
The Nonprofit Accelerator is a free solution published by Microsoft that you import into a Dataverse environment on top of Dynamics 365. It arrives as tables, relationships, forms, some sample apps and sample data. You then extend it. That is a genuinely useful head start on the data model, and it is a very different thing from buying a finished application with a roadmap and a support line.
The Common Data Model for Nonprofits underneath it
The value is the shared vocabulary. Constituents and households rather than raw contacts and accounts, donor commitments separated from the transactions that satisfy them, designations so a gift can be split across funds, fundraising campaigns, appeals and packages, awards for the grant lifecycle, and program delivery with delivery frameworks, indicators, results and beneficiaries. If you are an international development organization, the model also carries the fields for aid transparency reporting.
Support is not what people assume it is
An accelerator is published as an open community asset rather than as a licensed product with a service level agreement behind it. Issues are raised in the open repository, not on a support contract. Plan for that in your risk register, and never scope a build on a nonprofit specific capability without first confirming its current availability and support status directly with Microsoft, because the shape of these offerings has been repositioned more than once and pieces have moved between first party and partner led.
Take the model, question the rest
Our normal recommendation is to adopt the parts of the model you will really use and leave the rest uninstalled rather than importing everything because it is free. Every table you take on is a table somebody has to secure, maintain through release waves and explain to a new administrator in three years. A slim environment that matches your operation beats a complete one that matches a reference architecture.
The word membership does not appear in it
This is the finding that surprises people. The model is built around giving, granting and delivering programs. An association whose core object is a member with a term, a category, a fee and a renewal date will find nothing in the accelerator that represents that. It is not a gap in the accelerator so much as a scope boundary, but if nobody tells you before procurement it becomes a very expensive surprise in month two.
Products built on the platform are a third option
Between building on bare Dynamics 365 and buying a self contained association product sits a middle route: association management products built by specialist software vendors on top of Dynamics 365 and the Power Platform, which give you a membership module and leave you on Dataverse. That is worth evaluating alongside the other two, and we will help you evaluate it even though it is not us doing the building.
The one sentence worth taking away
For a fundraising nonprofit, the accelerator covers a real and useful share of the data model. For a membership association, it covers the smaller half of the requirement, and the membership half is a build. Neither of those is a reason not to choose the platform. Both are reasons to know which project you are actually funding.
Membership management: what has to be designed and built
This is the section a vendor demo skips. None of it is exotic and all of it is normal Dataverse and Power Platform work, but every item below is a decision somebody has to make deliberately, and several of them are expensive to reverse once data is in. If a partner cannot discuss these without prompting, that tells you something useful.
Membership is a term dated record, not a field on the contact
The first design decision, and the one that is most expensive to undo. If membership is a status field and an expiry date on the contact, you can answer who is a member today and nothing else. You cannot answer who lapsed in 2023 and rejoined in 2025, what they paid each year, or how many members you had at any date in the past. Membership belongs in its own table with a start, an end, a category, a status and a link to the person or organization, so that history is a row rather than an overwrite.
Individual and organizational membership are two different shapes
A corporate or institutional membership is held by the organization and consumed by named individuals who join and leave during the term. That means a roster with seats, someone at the member organization who administers it, and a rule for what happens to an individual when they change employer, which is the question every association eventually gets wrong. Model the seat as its own record from the start and staff stop maintaining it by hand.
Dues pricing is a rules engine, not a price list
Real dues have categories, banded rates by income or headcount or seniority, joint and household rates, student and retired and life rates, introductory offers, chapter supplements and proration for a mid year join. Put those rules in one place that finance can read, because they will change annually, and the version that lives only inside a Power Automate flow is the version nobody can audit at budget time.
Anniversary renewal and calendar year renewal are different systems
If everyone renews on the first of January you have one peak, one notice run and one reconciliation. If everyone renews on the anniversary of their own join date you have a rolling engine running every day. Both are perfectly buildable and they produce different designs, different portal load profiles and different finance conversations. Choosing this deliberately, on paper, before anything is built, saves a rebuild.
The lapse cycle is where the staff time actually is
Notices before expiry, a reminder on the day, a grace period during which benefits continue, then lapse, then a reinstatement rule that decides whether a returning member keeps continuous service. Every one of those is a state transition with an email attached and a definition of good standing that governs what the member can still do. This is unglamorous and it is the single largest source of recovered staff hours in an association build, which is why we put it in phase three rather than phase six.
Benefits and entitlements need a place to be enforced
A membership tier that unlocks discounted event pricing, restricted content, a directory listing, a certain number of job postings or a vote at the annual meeting has to enforce that somewhere. In practice that is web roles and table permissions on the portal plus a small amount of logic in the applications behind it. If entitlements live only in a policy document, staff will apply them inconsistently and members will notice.
Chapters, sections and interest groups are a second dimension
Many associations have geography and specialism on top of the core membership, sometimes with their own fees, their own committees and their own local administrators who must see their own members and nobody else. That last part is a Dataverse security question, business units, teams and hierarchy, and it is a much better question to answer during design than to retrofit after a chapter chair sees the national list.
Money in needs a gateway, and the platform does not ship one
Dynamics 365 has no built in payment processing. Card payments, recurring dues, direct debit mandates, failed payment retries and refunds come from integrating a payment provider or buying a component that wraps one. Build it as a proper integration with idempotent posting and an exception queue rather than a flow that calls an API and hopes, because the failure mode is a member charged twice, and that is the failure your board hears about.
The finance system stays the book of record
We draw this line early on every engagement. The platform is the master of who the member is, what they are entitled to and what was asked of them. Your accounting system stays the master of the ledger, the receipt and the tax treatment, including gift acknowledgement and any local relief scheme you claim under. Agree the boundary, the direction of each interface and the reconciliation report during design, or it surfaces at year end in front of your auditor.
Self service is the whole business case, and it is a portal
Join, renew, pay, update your details, download an invoice or receipt, manage your organization roster, register for an event. That is Power Pages, secured against Dataverse with web roles and table permissions, authenticated through Microsoft Entra External ID or an identity provider you already run. It is a real project in its own right rather than a page you add at the end, and it is also the thing that decides whether the whole programme repays itself.
The portal half of that list is a discipline of its own, described on our Power Platform and Power Pages page. Where the standard interface cannot express something, such as a chapter picker or a roster grid, we write a custom PCF control rather than trim the requirement. And before you model anything at all, our guide to the customization mistakes that cost the most to undo is worth an hour, because the membership as a status field mistake is the sector specific version of exactly that pattern.
Where the platform wins and where a packaged product wins
Comparing Dynamics 365 against a purpose built association management system or fundraising product, row by row. We concede the rows we lose, because a comparison that only ever concludes yes is a sales process wearing an analysis costume.
| What you are comparing | Dynamics 365 and Power Platform | Purpose built association or fundraising product |
|---|---|---|
| Membership, dues and renewals on day one | Built. Weeks of design and configuration before the first renewal notice sends. | Wins clearly. It is the reason the product exists and it is there when you log in. |
| One record for member, donor, volunteer and attendee | Wins clearly. One Dataverse record with every relationship hanging off it. | Often several products with an integration between them, and a person in two of them. |
| Unusual membership rules your product fights | Wins. The model is yours, so an odd category or a two dimensional chapter structure is a design choice. | Depends entirely on whether the vendor anticipated your case. If not, you change your rules. |
| Time to first value | Months. There is a build between you and the first useful screen. | Wins. Weeks, sometimes days, for the standard association shape. |
| Case management for member enquiries | Wins. Dynamics 365 Customer Service is a mature queue, routing and service level engine. | Usually a shared inbox or a light ticketing feature bolted on. |
| Grantmaking, program delivery and outcome reporting | Wins. The accelerator model plus a Power Pages application portal and approvals. | Rarely present in an association product. A separate grants system is common. |
| Total cost in year one | Higher. Most of it is implementation rather than licence. | Wins for the standard case. Subscription, configuration, go live. |
| Total cost across five years, if you keep changing | Often wins, because change is configuration you control rather than a vendor request. | Predictable while your needs match the product, and painful at the point they stop matching. |
| Living inside Microsoft 365 and Entra | Wins. One identity, one security model, native Teams, Outlook and Excel behaviour. | Varies from a good single sign on integration to a separate login staff resent. |
| Running it with no internal technical owner | Loses. The platform assumes somebody owns environments, solutions and release waves. | Wins. The vendor upgrades it whether or not anybody on your side is paying attention. |
Read the last row twice. It decides more of these projects than any feature comparison does.
Score yourself before you talk to anybody
You do not need a consultant to get most of the way to this answer. Read both lists and count. If the first list describes you and the second mostly does not, the platform is worth a serious assessment. If the second list is where you keep nodding, buy the product that already does what you need and spend the difference on your mission.
Signals the platform fits you
- +The same people appear in more than one role, so a member is also a donor, a volunteer, a delegate and sometimes a grant applicant, and today that means they exist in three systems with three spellings of their name.
- +You are already on Microsoft 365 and Entra, staff live in Outlook and Teams, and a separate login with a separate directory is a real friction cost.
- +Your membership model has something in it that packaged products keep saying no to, such as an unusual category structure, a two dimensional chapter and section arrangement, or dues arithmetic nobody else uses.
- +You need proper case management for member and beneficiary enquiries, with queues, ownership and service levels, alongside the membership record.
- +You run grants or programs as well as membership, and you want outcomes reported against the same constituents rather than in a spreadsheet nobody else can open.
- +There is one named internal person who will own the system after go live, with time protected for it, or you have budget for a managed support arrangement that plays that role.
- +You expect to keep changing: new membership products, new engagement models, a merger with another body, and you would rather own that change than raise a request with a vendor.
Signals you should buy something else
- xA small team, no technical staff, and no realistic budget for an implementation partner or ongoing support. The platform will outlive your capacity to look after it.
- xYour requirement really is standard: members, dues, events, a newsletter and a website, with nothing unusual in it. Buy the product that already does that.
- xYou need to be live in six weeks because the current system is being switched off. That is a timeline for buying, not for building.
- xNobody on the staff will own it. A platform with no owner degrades into an expensive database that only the person who left knows how to change.
- xThe budget covers phase one only. Half an implementation is worse than none, because you will have migrated the data and not yet automated anything.
- xThe board has been promised nonprofit features on day one. Manage that expectation before procurement or the project starts with a credibility deficit it never recovers from.
The same question in general form, whether you need a partner at all or can configure this yourself, is worked through on our hire a consultant against do it yourself decision guide.
Budget and skills, honestly
Nonprofit and association budgets are scrutinised harder than commercial ones and the money is answerable to members, trustees or funders. That is a good reason to be precise about the line items people miss rather than talking about value in the abstract. We do not publish prices here because they depend on your organization and on Microsoft terms that change, but every item below is something you can go and check yourself this week.
Check the nonprofit licensing terms yourself, in writing
Microsoft runs a nonprofit programme with grants and discounted rates across its cloud products, and eligibility is assessed against the organization rather than assumed. Registered charitable status in your country is not automatically the same thing as eligibility, and associations and professional bodies frequently do not qualify at all. Get your eligibility confirmed and the current rate quoted before it goes in a budget paper. Do not plan around a discount somebody mentioned on a call.
The licence is the small number
Even at full price, seats for a small back office team are rarely what decides the business case. Implementation, data migration and the ongoing ownership are. When a board paper compares a discounted licence against a commercial association subscription and stops there, it is comparing the least significant line in both columns.
Model the portal cost before you design the portal
A member self service site is licensed on external users or capacity rather than on your staff seats, so a portal serving twenty thousand members is a materially different commitment from an internal app for twenty staff. This is the single most common budget surprise in an association build. Get the numbers for your actual member count and your actual login pattern early, because the answer sometimes changes what you put in the portal at all.
Marketing and renewal email is its own licence and its own limits
Renewal notice runs and fundraising appeals through Customer Insights Journeys sit outside the core seat and come with their own contact and interaction allowances. If your renewal design sends five notices to every member every year, that volume belongs in the budget model on day one rather than being discovered when a send is throttled during the renewal peak.
Somebody has to hold it, and that is a skills question
Environments, managed solutions, a deployment path that is not somebody editing production, and two release waves a year that change behaviour whether you are ready or not. If you have a systems person who can learn this, protect their time formally. If you do not, price a managed support arrangement into the running cost from the beginning instead of discovering the need eighteen months in.
Budget for the second phase before you commit to the first
The pattern we see in rescues is an organization that spent everything on migrating data into a new platform and had nothing left for the automation that was the reason to move. Data in a new system saves nobody any time. The renewal engine and the self service portal are where the hours come back, so if the budget cannot reach them, the honest answer is to wait or to buy something smaller.
When the renewal quote arrives and the numbers no longer look like the ones in the original business case, our licensing cost and renewal negotiation guide covers what is actually negotiable and what is not.
The phased implementation path
Seven phases, each with a deliverable that has a name, so the plan is something you can check rather than something you have to trust. Two ordering decisions in here are deliberate and both are contrary to how these projects are usually sold: the assessment is allowed to conclude do not buy this, and the renewal engine is built before the member portal.
- 0
Phase 0: the fit assessment, and an answer that is allowed to be no
Two to three weeks, fixed scope and fixed price agreed in writing first. We take your membership rules as they really are, including the exceptions staff handle manually, your current data extracts, and an hour each with the people who process joins, renewals and enquiries. We map that onto Dataverse and the accelerator model on paper, name every place your operation does not fit, and cost each one. The deliverable is a written verdict: build on this platform, buy a purpose built product, or evaluate an association product built on the platform, with the reasoning attached. If the verdict is buy something else, you have spent the price of an assessment rather than a programme to find out.
- 1
Phase 1: one record per person, and the identity model underneath it
Before any membership logic, decide what a person is, what an organization is, and how the relationship between them is represented when someone changes employer, holds a role on a committee, or is both an individual member and a contact at a corporate member. Then deduplicate. Every organization we have migrated has had the same person three times with three spellings, and merging that after the build is far harder than before it. The deliverable is a clean constituent model with a documented merge rule and a duplicate detection configuration that stays on afterwards.
- 2
Phase 2: the membership object and its state machine, before any money moves
Build membership as a term dated record with categories, statuses and the transitions between them: applied, active, in grace, lapsed, reinstated, resigned, and whatever your constitution adds. Include the seat model for organizational members. Load history so past terms are real records rather than a single current status. The deliverable is a system that can already answer how many members you had on any given date, which is a question your board asks and most legacy systems cannot answer.
- 3
Phase 3: dues, the renewal engine, and the notice schedule
Now the pricing rules, the invoice or dues request, the payment integration with idempotent posting and an exception queue, and the renewal cycle with its notice schedule, grace period and lapse rules. Reconciliation to the finance system is designed here, not later, with the boundary written down. We put this before the portal deliberately, because it is where the recovered staff hours are, and because a portal in front of rules nobody has agreed just moves the confusion outside the building.
- 4
Phase 4: member self service on Power Pages
Join, renew, pay, update details, download the receipt, manage the organization roster, see what the membership entitles you to. Table permissions and web roles are reviewed record by record before go live, because a permission mistake on a member portal is a data breach rather than a bug. We load test the renewal peak specifically, since a portal that is comfortable on a Tuesday and falls over on the first of January has failed at the only moment that counted.
- 5
Phase 5: fundraising, grants and program delivery where they apply
This is where the accelerator earns its place. Donor commitments and transactions with designations for the giving side, and awards, applications and the grant lifecycle for grantmakers, with an application intake portal and structured review and approval. Program delivery with indicators and results if you report outcomes to funders. Take only the parts of the model you will genuinely use, and leave the rest out of the environment.
- 6
Phase 6: reporting, and the handover that makes it yours
Membership numbers over time, retention and lapse rates, income by category, campaign and fund performance, and the operational views staff use daily. Then the handover: managed solutions, a documented environment and deployment path, an administrator who has been trained rather than shown, and a written note of every decision that will look arbitrary to whoever inherits it. If you continue with a different partner or take it in house, everything works without us.
Phase 1 is a data migration project in its own right. If you are coming off a legacy association system or a set of spreadsheets, the mechanics of moving history without losing it are in our data migration guide, which is written around a Salesforce source but is mostly source agnostic, and the throughput side, meaning why a load is still running on day three, is in our Dataverse bulk import strategy. For the notice runs in phase 3, our troubleshooting guide on contacts stuck in Customer Insights Journeys is the one you will want bookmarked during your first renewal peak.
How we work, and what we are not
Solzet is a Microsoft Dynamics 365 Customer Engagement and Power Platform consultancy based in Yerevan, Armenia. We work directly with organizations across Europe, the UK and the US, and white label underneath other Microsoft partners who have won a project and need senior delivery capacity under their own brand. Engagements are B2B with a mutual non disclosure agreement, a data processing agreement that meets GDPR, and IP ownership stated in the statement of work. Armenia is UTC+4 with no daylight saving, so our working day opens before a Western European one and a morning question gets a morning answer.
We will be straight about the shape of our published work. Our case studies are a bank, a manufacturer, a management consultancy and a Microsoft partner rather than a wall of association logos, and we are not going to invent sector references we do not have. What transfers is the engineering underneath, and it is the same engineering in every one of those builds: Dataverse modelling and security, migration and deduplication of messy historical data, integrations built to survive retries and late syncs, Power Pages portals with permissions reviewed record by record, and custom controls where the standard interface stops. The management consultancy build is the closest analogue in structure, because it is the same problem of one constituent record with many overlapping relationships hanging off it.
We also stay inside our own boundary. We do the Customer Engagement side of Dynamics 365 and the Power Platform. We do not implement the Microsoft finance and enterprise resource planning products, and we would rather integrate cleanly with whatever your finance team already runs than claim ground we do not hold. For a membership organization that boundary is a feature, because it forces the conversation about which system is the book of record to happen during design instead of at year end.
More on who we are and how engagements run is on our Dynamics 365 partner page, and the white label arrangement for other Microsoft partners is described on our subcontracting page.
Frequently Asked Questions
Can Dynamics 365 do membership management for a nonprofit or association?
Yes, but as a build rather than out of the box. Dynamics 365 Customer Engagement on Dataverse is a strong foundation for it: the constituent record, case management for member enquiries, marketing and renewal communications, a Power Pages self service portal, and reporting all exist as mature capability. What does not exist as a ready made module is membership itself, meaning the term dated membership record, dues pricing rules, the renewal and lapse cycle, chapters and entitlements. Those are designed and configured on Dataverse, typically over a few months. If your requirement is standard membership and nothing else, a purpose built association product will be faster and cheaper. If your members, donors, volunteers and event attendees are the same people and you are already inside Microsoft 365, the platform usually wins over a five year horizon.
Does the Dynamics 365 Nonprofit Accelerator include membership management?
No. The Nonprofit Accelerator is built around the Common Data Model for Nonprofits, and that model is shaped for giving, granting and delivering programs: constituents and households, donor commitments and transactions with designations, fundraising campaigns and appeals, awards and the grant lifecycle, program delivery with delivery frameworks, indicators and results, and fields for international aid transparency reporting. There is no membership table, no dues engine, no renewal cycle and no chapter structure in it. For a fundraising nonprofit that model is a genuine head start. For a membership association it covers the smaller half of the requirement, and the membership half has to be built. Confirm this against the release notes of the version you install, because the accelerator does change, but plan on the assumption that membership is your build.
What exactly is the Nonprofit Accelerator, and does Microsoft support it?
It is a free solution published by Microsoft that you import into a Dataverse environment on top of Dynamics 365. It gives you tables, relationships, forms, sample apps and sample data implementing the Common Data Model for Nonprofits, and you extend it from there. Treat it as a community published asset rather than as a licensed product with a service level agreement behind it: issues go to the open repository rather than to a support contract. Microsoft has repositioned its nonprofit specific offerings more than once and capabilities have moved between first party and partner led, so before you scope a build around any nonprofit specific capability, confirm its current availability and support status directly with Microsoft. That check takes an afternoon and it has saved projects.
Is Dynamics 365 cheaper than a purpose built association management system?
Not in year one, and often yes across five. In year one you are paying for an implementation as well as licences, while an association product is a subscription plus configuration, so the packaged route almost always wins on first year cost for a standard requirement. The comparison changes over time and it changes on one variable: how much you expect to alter. On the platform, a new membership category, a different renewal rule or an extra portal journey is configuration you own. On a packaged product it is either included, or a change request, or impossible. Compare the two on total cost of ownership with an honest estimate of how often you change, and be careful not to compare a discounted licence against a commercial subscription and call that the analysis, because the licence is the smallest number in both columns.
Do nonprofits get discounted Dynamics 365 and Power Platform licensing?
Eligible nonprofits can access grants and discounted rates through the Microsoft nonprofit programme, but eligibility is assessed against the organization and is not the same as holding charitable status in your country. Professional bodies, trade associations and membership organizations frequently do not qualify. Get your eligibility confirmed and the current pricing quoted in writing before it appears in a budget paper. Two related costs are missed more often than the seat price: a Power Pages member portal is licensed on external users or capacity rather than on your staff seats, which matters a great deal at twenty thousand members, and renewal or appeal email through Customer Insights Journeys carries its own allowances. Model those two before you design either.
When should we not choose Dynamics 365 for this?
When you have a small team, no technical staff and no budget for an implementation partner or ongoing support, because the platform assumes somebody owns environments, solutions and two release waves a year. When your requirement genuinely is standard, meaning members, dues, events, a newsletter and a website with nothing unusual in it. When you have to be live in six weeks. When nobody will own the system after go live. And when the budget only reaches phase one, because migrating data into a new platform without reaching the renewal automation leaves you with the same manual work in a more expensive place. Any of those on its own is a reason to buy a purpose built product instead, and we would rather tell you that in an assessment than discover it together in month seven.
Can members, donors, volunteers and grant applicants live in one system?
Yes, and it is the strongest argument for the platform. One Dataverse constituent record carries every relationship: the membership terms, the giving history, the volunteer assignments, the event registrations, the enquiries raised, the grant applications submitted. That is what makes it possible to see that a lapsing member has given for nine years, or that a volunteer coordinator is also the billing contact for a corporate membership, which is exactly the insight that gets lost when those roles live in separate products with a nightly sync between them. It also concentrates your data protection obligations in one place, which is easier to govern properly and harder to be casual about.
How do we take dues and recurring donations? Is there a payment gateway?
Dynamics 365 does not ship payment processing, so payments come from integrating a provider or buying a component that wraps one, and that integration is a real piece of the project rather than a connector you switch on. We build it with idempotent posting so a retry cannot charge twice, an exception queue with the reason attached for anything the provider rejects, and a reconciliation report against your finance system. Recurring dues and regular giving add mandate handling, failed payment retries and the dunning sequence that follows. The line we draw on every engagement is that the platform is master of who the member is and what was asked of them, while your accounting system stays master of the ledger, the receipt and the tax treatment.
Can members join and renew online themselves?
Yes, on Power Pages, and it is usually where the business case actually lives. The site sits on the same Dataverse as the staff applications, secured with web roles and table permissions and authenticated through Microsoft Entra External ID or an identity provider you already run. Typical journeys are join and pay, renew and pay, update details and communication preferences, download an invoice or receipt, manage an organization roster for corporate members, and register for events. Two things we insist on: a permission review record by record before go live, because a mistake on a member portal is a data breach rather than a bug, and a load test aimed specifically at your renewal peak, since a portal that is comfortable on a Tuesday and collapses on the first of January has failed at the only moment that mattered.
How long does an implementation take, and in what order?
For a mid sized organization, plan in phases across several months rather than in one release. The order we use is a fit assessment first, then one clean constituent record with deduplication done properly, then the membership object and its state machine with history loaded, then dues and the renewal engine with the payment integration, then the self service portal, then fundraising, grants or program delivery where they apply, then reporting and handover. The renewal engine comes before the portal on purpose, because that is where the staff hours come back, and because putting a portal in front of rules nobody has agreed only moves the confusion outside the building.
Can you take over a nonprofit or association CRM project that has stalled?
Yes, and it is one of our regular service lines. It starts with an audit of what is actually in the environment, what is configured, what is custom, what is load bearing and what is only risk, followed by a fixed scope reset. The two patterns we see most in this sector are membership modelled as a status field on the contact, which means the history is gone and has to be reconstructed from whatever exports still exist, and a half migrated data set where the new system and the old spreadsheets are both live and neither is trusted. Both are recoverable. Our project rescue and takeover service covers the shape of that work and our health check and technical audit is usually the step before it.
Who are you, and do you work with nonprofits outside Armenia?
Solzet is a Microsoft Dynamics 365 Customer Engagement and Power Platform consultancy based in Yerevan, Armenia, working with organizations across Europe, the UK and the US on B2B contracts, and white label underneath other Microsoft partners who need delivery capacity under their own brand. We are honest about the shape of our published work: our case studies are a bank, a manufacturer, a consultancy and a Microsoft partner rather than a wall of association logos. What we bring to this sector is the engineering underneath it, which is the same in every one of those: Dataverse modelling, migration and deduplication, Power Pages portals with a serious approach to permissions, integrations that survive retries, and custom PCF controls where the standard interface stops. What we do not do is the Microsoft finance and enterprise resource planning products. We stay on the Customer Engagement side and integrate cleanly with whatever your finance team already runs.
Start with a fit assessment
Tell us how many members or donors you have, how renewals work today, and what the current system is. We will come back with what we would put in the scope note, what the assessment would cost, and an honest read on whether Dynamics 365 is the right platform for you at all. If the answer is that you should buy a purpose built product instead, that is a perfectly good outcome and you will hear it from us in writing.
Already mid project and stuck, or holding an environment somebody else built? See our project rescue and takeover service and our health check and technical audit, which is usually the step before any decision about what to keep.