Nexthink vs SAP Commerce Cloud (formerly SAP Hybris)

• Ease of data gathering
• Consolidation of multiple data points into one (previously, you'd have to request one thing from SCCM, one thing from JAMF, maybe something else from your Domain Controllers)
• Support. Nexthink has always provided great levels of support when needed.

Read full review

• Large scale product and user data management.
• Out of the box support for common eCommerce functionality.
• Robust platform that is supported well and consistently by the Hybris team who are available for direct support if needed.
• Integrates well with other services if Hybris does not meet all business needs.
• Localization for multi-national support was easy to implement.

Read full review

• The Finder is great but to utilize the product effectively it takes some getting used to. Very 'right click' heavy.
• Learning curve. Nexthink is very boolean based in their investigations (not a knock, most products are), but since they can track things at such a siloed level it's important to know specifically how they are classifying their objects (ex, a package vs. an application vs. an .exe vs. a binary) so you can understand what findings you're getting.
• Parity on Mac and Linux products. This is improving though.

Read full review

• CMS Cockpit is slow and inefficient for performing certain kinds of content management and template manipulation tasks. I often defer to the HMC, but this is not a feasible option for our client's content management team.
• The OOTB UI code that ships with v5.0.1 is several years behind industry standard front end technology. v5.1 shows no promise of significant improvements in this arena. Some things I'd like to see: Dropping the Blueprint framework in favor of something Like Bootstrap, Less Framework or AngularJS. Jquery and key dependent plug-ins need to be upgraded and large, over-featured plugins like JQuery UI abandoned. SASS + Compass should replace static CSS. Granule should be dropped in favor of better tools for JS dependency management, code minification, and file concatenation.
• Maintaining independent codebases for Desktop and Mobile views increases UI development hours by a margin of 30-50%. Natively supporting the option to configure a responsive design with a framework such as AngularJS would offer flexibility to serve up content and site chrome targeted at a wider range of device classes than just desktop machines and mobile phones.

Read full review

• Nexthink has been invaluable at quickly finding application roll-outs that could negatively affect our environment, in most cases before users even report them.
• Nexthink has helped us consolidate and gain visibility in our environment, further standardizing naming conventions, hierarchies, etc.
• Nexthink has integrated with our ITSM solutions, and is easy to use such that technicians no longer feel the need to request data from Engineers, they can just directly get it from Nexthink.
• There is a learning curve, so for good ROI you're going to need to invest the people and training hours to use Nexthink to it's fullest effectiveness. Note, that even a cursory use though would reveal a lot about your environment that will keep you busy.

Read full review

• Our business went through 3 major initiatives to migrate our legacy platform and data to Hybris over the course of several years with multiple tech leadership and dev teams. All 3 of these initiatives failed to launch, largely due to the complexity of the platforms and massively associated tech burdon. A 4th re-platforming succeeded in launching an MVP version with support from expensive consulting firms and to the tune of millions of dollars.
• Due to the inflexibility of the content management features, marketing teams are severely limited and have had to seek 3rd-party software to layer on top of Hybris to deliver modern customer experiences.

Read full review