Adobe Experience Manager vs Microsoft Office SharePoint Server comparison

"If you want to use content in a mobile application and you want the content in some other application, you can simply expose it from the CMS to different clients or different systems. It's easy. On top of that, the technology underlying AEM is open-source and is very powerful like Apache Sling and JCR."

"It is easy to learn. You don't need to be an advanced Java developer."

"I like the native applications such as Adobe Target, Adobe Analytics, and Adobe Experience Platform. Because of these, it's very easy to connect and obtain reports on how my website is doing, how many have visited it, how frequently, etc. The multiple publisher concept is one of the best parts of this solution."

"Easy to work with the solution."

"The integration of customer behavior and website setup is impressive."

"The most valuable features of Adobe Experience Manager include its capability to manage content and create reusable fragments."

"I like the profiling and segmentation."

"Adobe Experience Manager is a content management system, and we use it to create and manage a website."

"Document management and records management features are the most valuable."

"The most valuable feature is the "Alert Me", which provides the ability to set an alert when content is either added or changed and that the alerts can be either real-time or aggregated for the day or the week."

"The solution's most valuable aspects are its collaboration capabilities, its communications site and the innovation within the product itself."

"The most valuable feature of this solution is the Communication Site."

"The implementation and configuring of the resolution are very easy in the online version."

"This solution has provided us with a collaborative workspace to allow everyone to work together and be on the same page."

"The level of stability is good."

"The solution is pretty easy to use for the most part."

"The solution's pricing and stability could be improved."

"A little bit of background knowledge of coding and website structure is required."

"Tool-wise, the Adobe Experience Manager support team is not very responsive when the user face issues in AEM as a Cloud Service."

"The latest trend is to render everything in the client-side framework. For example, SPA or single page application. This is a feature that needs improvement. The cloud deployment pipeline needs to be improved as well."

"Adobe's technical support is so-so."

"The licensing model is opaque, and technical support could be improved, especially for smaller companies."

"Adobe Experience Manager's pricing could be improved."

"The licenses are very expensive."

"Workflows could be simplified."

"The user interface needs improvement because there is a lot of stuff in there. I use five to eight navigation buttons. It should be more user-friendly. Frequently used menu items should be arranged in a proper way. That would be helpful."

"Sharepoint doesn't integrate well with Oracle, and we use a lot of Oracle products at our company. Therefore, it makes more sense for us to go to Oracle instead of continuing to use Sharepoint."

"The product could be improved by accommodating different technologies, particularly integration."

"The solution needs to have more flexibility. The classic version had more flexibility, however, the modern version has many more limitations."

"It is a bit restrictive to develop in the cloud version. A lot of features are in the cloud now, and you have to develop on the outside. As far as the platform and the programming side of things are concerned, it is moving more towards configuration management rather than programming. When we are doing solutions, we are basically just configuring it to make solutions happen rather than actually using the Visual Studio code and developing from scratch in the cloud. It is almost like creating an app. You have created an app for your phone, but the app doesn't really sit on your phone. It sits somewhere on a server, and the database sits on another server. The app is just pulling and pushing information. The whole development has changed. We used to install things directly on the server and then run the application from the server. Now, it is more of a modular architecture."

"This solution is not very stable. It is useful to arrange data but it's not the best for big data. Sometimes we have issues with our reports as a result."

"The solution needs to be more collaborative. I believe they are just coming up with the themes for this right now."

"There's a free trial for one month for Adobe Experience Manager, which you can use for learning purposes, then, after the trial period, you'll need to purchase the license. Adobe offers a few plans for Adobe Experience Manager, but I'm unaware of how much my company is paying."

"It's really costly."

"Users have to pay a yearly licensing fee to use the solution, which is highly-priced."

"It's a costly solution. I would rate the price at two out of five on a scale from one to five, where one is the most expensive and five is the most competitive."

"One of the reasons why we don't recommend the cloud version of SharePoint is the cost. With the on premise version, you pay for the license once. For the cloud version, there is a recurring fee. It is very expensive. They expect everyone to pay $20 or $30 per user per month."

"Pricing plans may be flexible depending on volume usage and your corporate relationship with Microsoft."

"There are some aggressive discounts offered by Microsoft for organizations that are not for profit, which we are, and it makes it quite attractive to consider."

"It can be expensive for on-premises deployments, especially when you have to support SQL Server as your backend database. That's where the cost comes into play. SQL Server has its own licensing, which Microsoft keeps on changing. Therefore, it can become costly. In the earlier versions of SharePoint, version 2007 or 2010, they had an express version where the SQL Server licensing was free. It wasn't like a full-blown SharePoint. It was only a slimmed-down version. It used to be whatever your hardware costs. You would install the free software and work with it, but you were very limited in what you could do in SharePoint. If you wanted the SharePoint Enterprise Server with all the bells and whistles, then you had to pay more to get the SQL Server license based on the number of users or servers. The subscription model is different for cloud deployments. Licensing is per user and per month. The cost also depends on the storage required. If you have a lot of sites or documents, then you need to expand it based on your needs."