Microsoft Dynamics CRM Case Study

Microsoft Dynamics CRM

Online customer relationship management solution

4.28/5 (3,168 reviews)

Microsoft Dynamics CRM use case: Kyle Morgan

Kyle Morgan

Verified Reviewer  
17th of January, 2017
Not enough attention to bugs

We deployed Microsoft Dynamics CRM a little over a year ago and have very mixed feelings about it. We went with the cloud version of Dynamics instead of on-premise, leading to us having almost zero control over versioning and updates. Users report pop-up error boxes constantly on all platforms used to access it (Outlook, web, and mobile app).

What do you like best?

Can handle large amounts of data Cloud version is scalable on demand, including storage database No resource limits on # of users accessing system at the same time Easy to manage subscription-based licenses

What do you dislike?

Little to no control over version updates No warning on license structure changes Major platform updates can wipe out any customization that has been done Little to no support on Mac

Why did you end up selecting Microsoft Dynamics CRM over other applications?

It was part of a larger deployment of Office 365 and a migration to Exchange.

If so, why did you switch?

Integration with outlook and mobile apps, along with Office 365

What is your main use case with Microsoft Dynamics CRM?

Tracking lead generation and conversion to orders

Give one example how Microsoft Dynamics CRM has improved the way your organization functions

Live data on close rates, stale quotes

What is your ROI?

Still in the grey area

Likelihood to recommend


Recommendations to others considering Microsoft Dynamics CRM

Carefully consider your options and what you need out of a CRM program. Dynamics has its strengths but a significant amount of issues. I'm hoping the switch to Dynamics 365 will help improve the service.

Time used

1-2 years

Frequency of use


Rating breakdown

Value for money
Ease of use
Customer support