Microsoft Dynamics

Microsoft probably needs the shortest introduction compared to the other providers in this space because it is the clear leader in so many other industries.  The Dynamics division at Microsoft has been around longer than most of the other players in this market.

Being one of the oldest players in the market has its advantages and it’s distinct disadvantages.  They have one of the largest customer bases and so you will find a lot of materials available online from other customers like you who have faced similar problems in the past.  However, Dynamics is not a single product, but really a suite of products that all have unrelated origins.

Great Plains is one of their most popular and well known products, but it (like most of the other Dynamics Products) is based on technology from the 1990s.  While that may not seem that long ago, don’t forget that most people were using Windows 98 when this product was released.

Microsoft Dynamics is also known to be very modular.  Modules are divided and sold by the function (Accounting, Production, CRM, etc.)  This often leads to a disjointed implementation if you do not plan to implement all modules at once.  These modules are also built to operate independently, and therefore lack some of the integration that makes ERP stand out from independently managed system silos.

I like to work with products that have large customer bases because it means I have more customers out there testing my product and flushing out the bugs for me.  However, I would personally pass on any of the Dynamics products.  This software was built on old technology making upgrades, and system configuration much more difficult.  Microsoft is still working to integrate several fundamentally different products making these solutions feel more taped together than designed together.

Leave a Reply