The cost of a Dynamics 365 CRM has two parts. The first is licensing: a monthly subscription per user, priced by app (Sales, Customer Service or Field Service) and by plan tier. The second is implementation: one-time work whose scope depends on the number of processes and users, data migration, integrations with SAP, Priority ERP, telephony and WhatsApp, a portal, the amount of customization and training. Ongoing support and improvement come after that. The safe way to control cost is a focused first phase, out-of-the-box capabilities before custom development, and a POC on your own data.
How much does a CRM implementation cost?
In short: it depends on how much of your organization's work moves into the system in the first phase. A CRM for one sales team, with data from Excel and no integrations, is a completely different project from a service center with many agents, SAP sync, telephony, WhatsApp and a customer portal.
Zooz-Tech does not publish an implementation price list, because a generic range does not help you make a decision. What helps is understanding what the cost is made of:
- Licensing: a subscription paid to Microsoft per user, every month. This is a recurring cost that grows with the number of users.
- Implementation: requirements and design, configuration, migration, integrations, testing and training. One-time work, split into phases.
- Support and improvement: maintenance, changes and new development after go-live, according to a scope and SLA agreed in advance.
If you are still choosing a system, the comparison of Dynamics 365 and Salesforce helps you understand the differences before you get to cost.
How is Dynamics 365 licensing priced?
In short: a subscription per user per month, with an annual commitment. Each app, such as Sales, Customer Service or Field Service, is sold in several tiers, and the price rises with the capabilities.
Base licenses and attach licenses
According to Microsoft's Dynamics 365 licensing guidance, the first app for each full-access user is a base license, which is always the higher-priced option. Additional apps for the same user are bought as attach licenses, with the same capabilities at a lower price. So a user who works in both sales and service does not pay full price twice.
Not every user needs a full license
Users who only need basic capabilities, such as viewing data and making simple updates, can work with a Team Members license, under the terms Microsoft defines. There is also licensing per shared device, for example a workstation that several employees use in shifts. A Power Pages portal is priced separately, by authenticated users per month. The licenses include Dataverse storage capacity, and when your data grows beyond it, you buy additional capacity.
Microsoft list prices
As of 11.2026, according to Microsoft's official pricing pages for Dynamics 365 Sales, Customer Service and Field Service, these are the list prices in US dollars, per user per month, paid yearly:
| App and plan | List price per user per month |
|---|---|
| Sales Professional | $65 |
| Sales Enterprise | $105 |
| Sales Premium | $150 |
| Customer Service Professional | $50 |
| Customer Service Enterprise | $105 |
| Customer Service Premium | $195 |
| Field Service | $105 |
| Field Service Contractor | $50 |
Prices change, exclude VAT and discounts, and Microsoft notes they are for informational purposes and may vary by currency and country. Attach prices are lower and appear in the licensing guidance. Check the actual price in your organization's licensing quote.
What drives the implementation cost?
In short: the scope of processes, the state of the data, the number of systems to connect, and how far the system needs to depart from its built-in capabilities.
Number of processes and users
Every process, such as lead management, case handling or a work order for a technician, needs requirements, entities, views, permissions and testing. Several teams with different ways of working add security roles and test scenarios. The number of users affects development work less, and licensing, training and the phased rollout more.
Data migration
Moving data from a previous system, from Excel files or from several sources involves field mapping, cleansing, merging duplicates and trial runs. Clean data moves quickly. Data with duplicates, free-text fields and a long history needs more work, and sometimes it is better to migrate only what is actually in use.
Integrations with SAP, Priority ERP, telephony and WhatsApp
Every integration is a connection that has to be built, secured and tested: syncing customers and orders with SAP or Priority, connecting to the phone system so the agent sees who is calling, or sending WhatsApp messages from the CRM. A cloud system with a well-documented API is simpler. A system that runs on-premises needs a gateway or a middleware layer. Two-way sync is more complex than one-way sync, and you need to decide which system is the source of truth for each type of data. More on SAP and Priority integration.
A portal for customers, suppliers or residents
A Power Pages portal sits on the same data, so there is no API layer to build. There is still work in it: authentication, record-level permissions, forms, design and accessibility. Details in the guide to a Power Pages customer portal.
Customization vs out-of-the-box capabilities
Dynamics 365 comes with sales and service processes, queues, SLAs and reports. Anything you use as is costs less to build and maintain. Every code customization, plugin or custom interface is extra work now, and extra testing with every Microsoft release update.
Training and change management
Training for users and managers, short guides and close support in the first days. A CRM that employees do not use is the most expensive outcome, so this is not the place to save.
Support and SLA after go-live
Fixes, small changes, new development and checking release updates. The scope depends on the required response times, the hours of coverage and the volume of changes the organization plans.
What makes it more expensive, and how do you stay in control?
| Cost factor | What drives cost up | How to stay in control |
|---|---|---|
| Processes | Everything in one phase, and every team with its own process | A focused first phase and one standard process for all teams |
| Migration | Duplicates, free-text fields and a long history | Cleansing before migration, and only data that is in use |
| Integrations | Two-way sync with several systems, and on-premises systems | One source of truth per data type, and one integration at a time |
| Customization | Custom code instead of built-in capabilities | Out-of-the-box first, and development only where there is a real gap |
| Licensing | The top-tier plan for every user | Licensing by role: base, attach and Team Members |
| Adoption | Too little training, and users who go back to Excel | Role-based training, a phased rollout and support in the first days |
How do you reduce the implementation cost?
In short: start small, use what the system already has, and prove value before you expand.
- A focused first phase. One process with clear value, for example handling service cases, goes live first. More processes join after the first one works.
- Built-in capabilities before development. Adapt the way of working to the system where the difference does not matter, and develop only where there is a real gap.
- A POC on your data. A working version of one process, on the organization's data and systems, shows what works and what is missing before you commit to the full project.
- Data cleansing before migration. Every duplicate record that is not migrated saves work during the move and confusion after it.
- Licensing by role. Not every user needs the top-tier plan. Mapping who does what prevents paying for capabilities nobody uses.
What determined the scope in our projects?
Mekorot · CRM and customer portal: we took over development from a previous vendor. The scope was driven mainly by integrations: contact management synced with SAP, distribution of letters and WhatsApp messages, and intake of requests from the company website, alongside adapting the portal to mobile.
HaShomer HaChadash · CRM and two portals: Dynamics 365 and Dataverse as a single source of truth, with two Power Pages portals, for instructors and for parents, automated scheduling and reminders, and Power BI reports. Here the portals and automations are a central part of the scope.
Rishon LeZion Municipality · resident service connected to the CRM: every KESHER conversation is logged in the municipality's CRM, and the agent sees the full history. The connection between the service channel and the CRM was planned from the start, not added at the end.
How does Zooz-Tech provide a cost estimate?
In short: start small, on real data, with a scope and end date set in advance.
- Discovery. A workshop with process owners, users and IT. We map processes, systems and data, and agree on a success metric.
- POC on real data. A working version of the selected process, on the organization's data and systems. At the end we decide together: Go / No-Go. Even if you stop, you keep a grounded estimate of cost, benefit and timeline for the full project.
- Specification and phases. An approved specification with milestones and acceptance criteria. Development progresses in sprints, and scope changes are decided together, with their impact on time and cost.
- Phased rollout and support. First we go live with an initial group of users, fix what comes up in the field, and only then expand. After that comes a stabilization period with the same team.
The full process is described on the How we work: Delivery and POC page, and what the service includes on the Dynamics CRM services page. If you are also planning an AI agent on top of the CRM, its costs are covered in the guide to AI agent cost.
Frequently asked questions
How much does a Dynamics 365 CRM implementation cost?
It depends on the number of processes and users, data migration, integrations with other systems, a portal and the amount of customization. Zooz-Tech does not publish a price list, and provides a grounded estimate after a discovery workshop or a POC on the organization's data.
How is Dynamics 365 licensing calculated?
A subscription per user per month, with an annual commitment. A user's first app is a base license, and additional apps are bought as attach licenses at a lower price. Users with basic needs can work with a Team Members license.
What is the difference between licensing cost and implementation cost?
Licensing is paid to Microsoft every month, by number of users and plan. Implementation is one-time work covering requirements, configuration, migration, integrations, testing and training, followed by ongoing support and improvement.
What makes a CRM project most expensive?
Usually two-way integrations with systems such as SAP or Priority ERP, messy data that has to be migrated, and custom development instead of built-in capabilities. Each of these can be controlled already in the specification phase.
Can we start small and expand?
Yes, and that is the approach we recommend. Start with one process, go live with it, and add processes, integrations and portals in phases.
Founder & CEO of Zooz-Tech, solutions architect, Microsoft 365 Architect Expert.