SAP Hybris Marketing – different deployment options or entirely different solutions?

Important topics to consider when choosing between cloud or on-premise

2. maj 2018

af Julie Hannerz

Numerous sources are available to find information pertaining to the functionality and capabilities of the up-and-coming marketing tool SAP Hybris Marketing. As for the deployment options, generally two choices are available; on-premise and in the cloud. Traditionally, deployment options refer solely to how an application is deployed and hosted, but particularly with SAP Hybris Marketing “deployment options” might not be the entirely correct choice of words. Hence, I dedicate this blog to shed light on some of the key differences, which are important to consider before deciding on a deployment option or – as I would like to say – solution.


Release Schedule

Let’s start with something simple – the release schedule. As for SAP Hybris Marketing (on-premise), SAP will provide a release each September along with the possibility of a support package in February. SAP Hybris Marketing Cloud on the other handis updated with new functionality quarterly. In accordance with SAP’s “Cloud First” approach, functionality will become available in the cloud before it is made available on-premise.

So, ask yourself: How long can I wait for new functionality to be released, and would I be able to manage regression testing up to 4 times a year?



Probably the most notable or striking difference between the deployment options (or solutions) is the way they are configured. The configuration of SAP Hybris Marketing (on-premise) is performed in a traditional SAP GUI, whereas the configuration of SAP Hybris Marketing Cloud is performed in a Configuration App located in the Fiori Launchpad. Practically, this means that the configuration of SAP Hybris Marketing Cloud is significantly less time-consuming, but also less flexible. Besides some custom business objects, one is quite limited to standard functionality in the cloud solution. Since the configuration is so fundamentally different in SAP Hybris Marketing Cloud compared to SAP Hybris Marketing (on-premise), different types of resources are required. If you already have in-house technical resources and competencies who are used to handle on-premise SAP systems, e.g. integration wise, then the on-premise solution might be the more obvious choice. On the other hand, if you do not have any traditional SAP resources available in-house, then SAP Hybris Marketing Cloud solution might be more feasible.

Nevertheless, ask yourself: What is the planned timeframe of the implementation project and would the standard functionality of SAP Hybris Marketing Cloud suffice? What kind of resources do I have available in-house? Do I have a need for complex integrations?


Tenant Landscape and Transportation Management

Last, but not least, I would like to address some less sexy but quite essential topics: tenant landscapes and transportation management.

SAP Hybris Marketing (on-premise) allows for a traditional multi-tier landscape, and transportation management is configured just like in any other on-premise SAP application. You can organise configuration into any amount of transports and move these between the systems.

SAP Hybris Marketing Cloud works quite differently. Upon purchase of the solution one is provided with a so-called “starter system”. As indicated by the word “starter”, the tenant is purely meant as a first glimpse of the core functionality, meaning that one is limited with regards to the configuration options, which is also why I would not equate the starter system with what is typically referred to as a sandbox.

You can use the starter system until you deploy a production tenant – meaning that SAP Hybris Marketing Cloud is only foreseen as a 2-tier landscape. Once you are live with the solution, you will only have a test- and a production tenant. Now, in SAP Hybris Marketing Cloud, a lack of (what IT enthusiasts would call) transportation management practically means that you cannot move single configurations from the test- to the production environment. Instead, you have to move all configuration at once. In addition to that, the quarterly release schedule also requires configuration to be released before the system is upgraded. This concept reduces the length of configuration phases and thereby encourages smaller and faster release cycles for your configuration.

Here, ask yourself the question: Do I need to be able to run different (configuration) projects in parallel, and would I be able and willing to adjust the configuration projects into smaller and more agile release cycles?

Obviously, there are a lot more questions to be answered prior to deciding which one of the solutions (as I like to call them) your company would like to implement. However, what I would like to be the take-away from this read is that the solutions differ too much for you to solely base the decision on how the solution should be deployed – on-premise vs. cloud. You really should be thinking about the future use of the solution – because choosing the wrong solution could result in quite some challenges with regards to the implementation and even more importantly the user adoption.

Julie Hannerz

Julie Hannerz

Is a consultant specialized in SAP Hybris Cloud for Customer and SAP Hybris Marketing.

Share This
Call Now Button35 55 55 75