Adobe Experience Manager vs Microsoft Office SharePoint Server comparison

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

"Adobe Experience Manager is pretty stable."

"Adobe Experience Manager is quite a powerful product that you can use to design files and export them."

"It's a complete package. You don't need to look elsewhere for digital marketing."

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

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

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

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

"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 implementation and configuring of the resolution are very easy in the online version."

"The most valuable features for us are their document management list and hybrid forms. and We also use third party ad-dons to achieve workflows and other recent apps."

"The most valuable aspect of the solution is the fact that it doesn't require coding. You just need to configure it. You don't need to code before getting something running. It makes it very fast."

"The solution's most valuable features is its document management. It allows sharing with external users and integrates well with Office apps and Microsoft Flow."

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

"The software is friendly to use for mixing data and analyzing it."

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

"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."

"I haven't seen any areas for improvement in Adobe Experience Manager as it's a full-fledged CMS tool, and Adobe is already working on enhancements for the solution. Adobe is working to make Adobe Experience Manager more valuable and easier to use for any user, even non-technical ones, through multiple components and templates. Day by day, Adobe provides the latest update to Adobe Experience Manager, and if my team needs any particular change, it just needs to be reported to the Adobe team. As Adobe Experience Manager has a broad scope and a lot of use cases and features, it's a solution that requires some time and effort from you in terms of learning, especially if you're implementing it for different clients, which could be an area for improvement."

"Programming model could be improved, it's a monolithic solution."

"There is a feature missing where if content is created on the UAT environment and needs to be transferred or synced to the production environment, there is no direct way of doing the sync."

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

"Adobe Experience Manager could improve by allowing the reuse of components like a progress bar across multiple pages to make the development process more efficient."

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

"In comparison to other CMS products, Adobe Experience Manager is missing some capabilities such as proper versioning or a better versioning system and backend connectivity. If something is deleted in AEM, the user cannot recover it. You have to call technical support, and they will need to recover the whole instance. So, it's really difficult. For example, if you delete a page, you cannot recover it. There should be an option to recover it. In AEM, you have to go to the previous state of the instance itself or the virtual machine, and you have to restore everything, which is not good."

"The GUI is outdated."

"The product is behind in development and lacks some features."

"The solution is like a CRM, so the initial setup is complex. It takes a few days to deploy the solution and the length of time depends on how large the company's topology is and what the client's demands are."

"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."

"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."

"The areas around security, such as protection, need to be included."

"Workflows could be simplified."

"Technical support could be improved. They are not fast enough, especially when we'll go deeper in the product itself. More complex issues make it very tough to find someone that can help you."

"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."

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

"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."

"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."

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

"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."

"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."