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."
"Flexibility is the best feature. Because we have the source code, we can develop our ideas. It enables us to develop new functions."
"It's scalable."
"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."
"I like that it's a complete ERP solution from production level to branch level."
"The most valuable feature of Microsoft Dynamics AX is customization."
"The product is easier to use and has more efficient workflow management features than other vendors."
"The power of ABAP Development Tools is the main valuable feature in the SAP ECC system. Every couple of years SAP upgrades ABAP technology significantly, which facilitates developers' work."
"If you are well versed in SAP, the initial setup is pretty simple."
"It is a comprehensive and robust solution. It can provide lots of functional features."
"The payroll solution and the localization for advances are valuable."
"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 solution is quite scalable."
"The stability and performance are good."
"It gives us full control over each change, to the level of the individual field in a master record, including certificates."
"The product needs improvement in procurement planning. It also needs to include a production scheduling feature."
"The on-premises and desktop versions are not user-friendly."
"At times there are issues related to reporting, sometimes with the integration between two or three modules, and sometimes to the logic itself."
"Microsoft could provide more flexible hardware requirements that can scale with the volume of data being processed rather than providing only a minimum requirement."
"There is no Arabic interface in Microsoft Business Central, which is a big weak point."
"The general speed of the solution needs improvement."
"It could be more scalable and stable. It would also be better if the interface were more integrated with the Microsoft ecosystem because 2012 is not really integrated."
"It needs better financials and reporting from the system, not through Excel."
"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."
"The power of ABAP Development Tools is the main valuable feature in the SAP ECC system. Every couple of years SAP upgrades ABAP technology significantly, which facilitates developers' work."
"Their support should be improved. Instead of giving a general solution, their consultants should first try to understand the problem and then resolve the same. They should properly investigate the issue before providing the solution."
"We will not make any major changes, and we are not expecting any enhancements or new features from SAP because they already have a new solution. No development is happening on SAP ERP because SAP has come up with a new version called SAP S/4HANA, which is memory-based technology. We are planning to upgrade to SAP S/4HANA, but we don't know when it will happen. We are in the preparation phase."
"It was not designed to service all industries."
"Sometimes the cost is not reasonable, such as in the case of budgeting."
"The user interface could be improved. For example, sometimes you're missing some data and can't complete a task. There should be some built-in support and suggestions on how to solve your problem. I would also like the interface to be optimized to work better with mobile devices like tablets and smartphones."
"It's difficult to code; structured language is difficult."
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.