Navision Vs Axapta

Many of us who are working on Microsoft Technologies are interested in the differences between GP, Axapta and Navision. In this search I came to the following annoted by Gerrit Combrink and Rene on the Microsoft.Public.Axapta newsgroup which might be helpful:

The focus areas of both products are around Manufacturing, Distribution and Services. The main differences are with functionality and technology.

(In Axapta, all this functionality is standard. There is no standard Services functionality in Navision. Such functionality needs to be built by ISVs.)

Axapta is aimed more towards the top end Mid market to corporate customers with complex requirements, while Navision looks after the lower to middle mid market segment with less complex requirements.

(Lower meaning: about 10 concurrent users. Above 20 users: Axapta)

Technology within Axapta also allows it to be a much stronger, more stable, higher performing competitor in a 3-tier environment as this is built into the existing architecture. You can also run a lot more concurrent users on a Axapta system than on Navision.

(Axapta's AOS technology (Axapta Object Server) provides scalability. Axapta has been tested from 1 user up to 3500 concurrent users.)


http://www.microsoft.com/BusinessSolutions/default.mspx

These are certain guidlines given by Oliver in deciding which product to use:



1. If the customer is more a technology freak -> Axapta
2. If the user need a vertical solutions -> Navision
3. If you need web services -> Axapta
4. If you have less than 30 Users -> Navision
5. If you have more than 500 Users -> run Axapta
The conclusion is that the use of Axapta or Navision is not decided on a rational basis, but on the basis emotions and sympathy for one of these products by the prospect.