We performed a comparison between Microsoft Dynamics AX and SAP ERP based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: In this comparison, users of both solutions share mixed opinions on deployment and support. The major difference between the two products is that Microsoft Dynamics AX users find the interface to be very functional, whereas SAP ERP users feel that the ERPs UI is complicated and frustrating. In addition, SAP ERP users agree across the board that it is an expensive product.
"The performance is good."
"AX is nearly a Tier One product, so implementations are long, but there's a lot of flexibility. Also, the ability to handle different issues found in larger organizations."
"In terms of features, GP offers a wide range of strong capabilities, particularly in the financial module."
"The accounting and inventory management features are valuable."
"The most valuable feature for us is the manufacturing module. It addresses our product costing for tuna canning."
"If anyone is familiar with Microsoft products then they can handle it easily."
"Almost all of the features that we use are efficient. Live master planning successfully handles all of our company's requirements."
"The most valuable feature is the workflow of the modules."
"The most valuable feature of SAP ERP is the integration. It can be seamlessly integrated across the board."
"I like the solution's ability to close plans and resource requirements in deals."
"MDG provides a central location for governance of the creation/updating processes of master data. It allows you to change several fields in the same object. For example, we can change a field on the purchasing view and change another field on an accounting view to the same material at the same time."
"SAP is a very process controlled application. It does not allow users to manage the data. Once the initial process is set, it works smoothly."
"This is a robust and feature-rich solution."
"From a long-term perspective, I can say that the solution can offer a return on investment, but it may take around three to four years for our company to experience it."
"I like SAP's premade workflows for various areas, such as supply chain, procurement, or finance."
"It gives us full control over each change, to the level of the individual field in a master record, including certificates."
"The manufacturing module in GP is quite basic, and those who require more advanced manufacturing capabilities often turn to third-party modules or tools."
"There is room for improvement when handling various currencies within the current Microsoft Dynamics AX system."
"The older version of Microsoft Dynamics AX that we are using is not as scalable as the newer version."
"Our version has performance issues so it gets stuck and is slow."
"From a consultant's point of view, I recommend an enhancement in terms of detailed documentation for the products on the website."
"Microsoft Dynamics AX can improve by having a more modern user interface. It should be more modular and dynamic. Additionally, the solution could be easier to connect with APIs with other technologies."
"The product needs better admin control. There is room for improvement in flexibility, reporting, and dashboards. Artificial intelligence should be incorporated. I have concerns regarding partners, specifically in the implementation and deployment of Microsoft Dynamics."
"It is being decommissioned."
"The speed to build and the speed to deliver could be better."
"When evaluating the current version I am using now, the SAP GUI is old-style and needs to be replaced with something more modern and easy to use. However, the SAP GUI is very optimized for connection networks and is extremely good. Many people would like to have a WebGUI or something else to have access in a different way. Additionally, there could be some drag and drop functionality added because these features are normally in any website that this solution does not have."
"SAP ERP could improve by having better integration with other platforms."
"The production system must be upgraded."
"ERP could use better integration with other systems."
"The system is very big. It is not exactly user-friendly, due to the fact that it's so massive and complex."
"It should be less complex. It should also have better integration capability. I am using the ACC version, and in this version, the integration and the communication are very difficult and complicated."
"The warehouse management could be better."
Microsoft Dynamics AX is ranked 6th in ERP with 51 reviews while SAP ERP is ranked 1st in ERP with 100 reviews. Microsoft Dynamics AX is rated 7.6, while SAP ERP is rated 8.2. The top reviewer of Microsoft Dynamics AX writes "A stable product that offers excellent ROI and reliable technical support". On the other hand, the top reviewer of SAP ERP writes "The amazing, robust framework with unlimited scalability earns its #1 status". Microsoft Dynamics AX is most compared with Microsoft Dynamics 365 Business Central, SAP S/4HANA, Oracle E-Business Suite, Oracle Fusion Cloud ERP and Microsoft Dynamics GP, whereas SAP ERP is most compared with SAP S/4HANA, Anaplan, SAP Business One, Infor M3 and Infor LN. See our Microsoft Dynamics AX vs. SAP ERP report.
See our list of best ERP vendors.
We monitor all ERP reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
For starters, I would stop comparing tools, and start looking at my business and what I want to achieve. So identify objectives and what's blocking achievement, define quality outcomes for the obejctives you want to achieve and build your businesscase on efficiency improvement. What earnings, savings, benefits are achieved when meeting your obectives.
Based on the blocking issues you identified, build use cases and challenge vendors to prove their outcome by building a PoV (Proof of Value).
Basically start looking for what improvement your business and processes need, rather than start looking for a tool. After all a tool is just a tool.
As a followup, I would not 'assume world class ERP has these features covered'.
We've seen several actual cases of RFP's (which is why we no longer rely on this outdated capital procurement process to evaluate strategic deployments) - but we've seen where several vendors will check YES to the RFP question concerning a certain feature. Company A does the certain feature well, with a single click. A couple other vendors do it OK, and a couple of the YES answerers require everyone to log out of the system, balance the outlying modules, jump through 6 undecipherable processes, and then YES - it does that.
If that particular feature is something you need 15 or 20 times a day, well, you're probably starting an expensive and long running development effort if you picked the wrong ERP.
The main point is, ERP evaluations need to be a defined process by which you don't make assumptions, skip steps, and your methodology should be repeatedly proven across multiple instances, industries, and shown to deliver with different internal teams (who's mileage may vary).
ERP has the potential to be wildly successful and given a solid business case, provide the tools for your staff to create substantial returns. It also has the potential for abject failure, and that potential for failure is north of 80%, industrywide. So your choices are whether you are comfortable with a big pile of money or a large vat of risk.
Only you can determine your comfort zone.
1. Your business is well defined?
SAP ERP = Company has to organize my directions. Microsoft ERP = I have to organize the company's directions.
2.Which industry do you stay in? In the SAP is more suitable for "Manufacturing", ERP is more suitable for "Retail and Distribution". The rest of the industries are the same difference.
3. Your business logics are too complicated? Microsoft Dynamics can be adapted easily.
4. On-Premise vs Cloud? On-Premise = SAP, Cloud = Microsoft
5. Reporting? It's too hard to access Microsoft Data today. Because no one can be accessed the operational data directly.
6. Commerce? Microsoft Commerce platform is well defined for omnichannel commerce.
I think.
Do you want to do it for a specific purpose or to tick a box?
Lets assume you are looking for system deployment. I would focus on the key areas of your business rather than what Gene has listed below, which is looking at point for point comparisons. (The Panorama report is SUPERB for getting up to speed....)
Then look at weighting for specific key business differentiation opportunities - such as single global instance for multiple companies, integrated CRM into Finance and Operations, off-line capabilities for customer facing processes, seamless transfer of customer conversations from one channel to another.
Then ask for client references to answer 5 key questions:
- Are they live?
- how was the deployment support from the OEM/partner and what was the % work split required to go live (as in your input vs partner vs OEM)
- how many customisations were requried to achieve xxx (your key areas)
- would they use the OEM again and what would they change going forward
Then look at demonstration from the OEM and costing for the solution
I would not go on a tender for each and every feature and function because we assume world class solutions have these typical areas covered.
Happy to discuss how to do this practically if required. Daniel@liferocksconsulting.co.za
I think Panorama Consulting Group publishes some of their ERP shootouts comparing SAP/Oracle/Microsoft with Infor thrown in as a bonus.
Our firm is more of a boutique operation that compares internal company requirements then picks software known for its propensity to work well in those industries/environments. But if you get to the stage where you need some guidance on who some of the top partners and resources are for those software packages, hit us up.