Acquia Digital Experience Platform vs Salesforce CMS

• The Acquia Cloud Hosting (enterprise) provides a three-server solution. You have a Development, Staging (or UAT), and Production servers with a clear path of deployment straight up the chain. You may use Acquia's own Cloud Hooks, or their web admin UI interface to deploy to any or all of the servers.
• Git is one of the foundation services built-in to the management of the website codebase. Allowing a developer, or well-trained end user (university employee) to easily deploy a tag or branch to any one of the servers, makes it very easy for us to offload the server / account management to the school, while we focus on improving their site.
• Not only does Acquia Cloud provide a multi-datacenter failover disaster recovery solution, but they also maintain a multi-region failover as well, which allows for a fully redundant enviroment to be maintained in two geographic regions. No fear of losing any database changes or form submissions from students.
• Lastly, the onboarding process is constantly being improved, and as I have been a third-party vendor involved in many of our hosting negotiations, I have seen it firsthand. Each enterprise client is assigned a small team of engineers, technical leads, and a pseudo-project-manager to explain the process in layman's terms to the client (university / college for my example), but they also perform a number of code reviews and best-practice analysis of a site prior to launch.

Read full review

• Easy to use, just like Salesforce's other products. Many users can sit down and figure it out in no time, and with a little training become power users.
• Fast and secure - Salesforce is a leader in the cloud world so you get consistently fast results and security that is top notch in the industry.
• Accessible from anywhere - if you use cloud CMS already this is a no-brainer, but for those that do in-house CMS still, this is a major difference. Mobile access from anywhere on the planet without a VPN is something you just can't do without the cloud.

Read full review

• Responses from tickets aren't always from the same person, and can vary in effectiveness of solving your problem
• While documentation is robust, it can be difficult to find exactly what you need
• Provided forums are not monitored frequently, and are not as useful as they could be

Read full review

• Trailhead - I have run into several issues with Trailhead articles directing me to an Error 404 page, and with inconsistent product naming conventions (Community Cloud vs Experience Cloud etc) which make for a confusing journey when implementing.
• Salesforce Inbox - the integration for Gmail/Salesforce for logging emails is rather archaic and step-heavy. It would be ideal to implement some AI that can detect the account & opportunity outright, as well as fast-track the ability to create new contacts.

Read full review

• Our website isn't a revenue generator, so we don't have specific ROI calculations.
• The new website is helping us move off of a legacy on-prem server environment. The reduction of cost in maintaining those will be beneficial.
• We have had to invest in some training for our developers to learn Drupal.

Read full review

• It helps us to keep track of any potential conflicts between sales organizations.
• It allows us to have robust reporting for every sales team and the overall organization.
• It gives us a solid platform for our day-to-day work rather than using multiple software.

Read full review