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.
"In terms of features, GP offers a wide range of strong capabilities, particularly in the financial module."
"The stability is very good."
"I am impressed with the tool's vendor collaboration. It is also easy to connect with third-party applications."
"Microsoft Dynamics is very stable."
"The product's most valuable features are its day-to-day operations, Power BI-driven workspaces, and homepage."
"There's a moderate amount of scalability available."
"The most valuable feature I've found is the UI functionality."
"The most valuable feature is the workflow of the modules."
"Its integration is most valuable."
"The solution has a lot of good integrated modules."
"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."
"It is a utility-focused solution, and the deployment is very much aligned with utility service providers. If you look at the supply chain and the overall business model of a utility service provider, SAP is something that fits very well. That's because the company has invested tremendously in creating appropriate workflows pertaining to this segment or domain."
"SAP is already working on improvements by doing annual releases with enhancements."
"There are many interfaces, so you really can build satellites around it like with other SAP stuff or even third-party stuff."
"It integrates everything into one process."
"The solution has made the most significant impact on our human resources function, specifically in HR operations and HR analytics. One feature of SAP ERP that I found most valuable is its use of codes for accessing specific functions."
"The UI has room for improvement and can be more user-friendly."
"The product is standardised across industries so it is not a good fit for all types of sectors."
"We do not have access to daily projections."
"There is no Arabic interface in Microsoft Business Central, which is a big weak point."
"The on-premises and desktop versions are not user-friendly."
"The solution in general just needs a few quality improvements."
"There is room for improvement in the licensing model and associated costs of this solution."
"Microsoft Dynamics AX can improve system performance and security. The security is basic and needs a lot of improvement."
"It needs to incorporate the new features from the SAP S/4HANA release, such as, utilizing data processes, which is quite nice."
"It could be more flexible, and the company should be able to adapt the system. Not the other way around. It's very rigid and difficult to change. Reporting could also be better."
"They need to improve a few processes, including transformation, intelligence, governance, modeling, etc."
"The service could be more user-friendly in the area of transition codes."
"Functionality could be improved."
"The problem with SAP is that whenever there is a modification, or if a new field needs to be added, they charge tens of thousands, hundreds, or even two hundred thousand dollars. That is not anything in which I am really interested. For instance, consider a single-use case. I have to enter the root causes for a certain operation or failure. That option does not exist anywhere in SAP, not in manufacturing, not in logistics, not in anything. It is completely missing. The root cause analysis is very common across industries, yet SAP does not offer this option. A line field or a metaparticle, for example, was delayed. If you have the choice to input the warehouse operator or if the person who submitted the document has the opportunity to enter, this has been postponed for N, X, Y, or Z reasons."
"It has a high cost."
"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."
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, Microsoft Dynamics GP and Oracle Fusion Cloud ERP, 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.