The easy way into the SAP Commerce Cloud

The easy way into the SAP Commerce Cloud

Achieving precision with a 3-step plan

SAP Commerce Cloud

Transparent process simplifies cloud migration

In a previous article, my colleague Markus Schlautmann already explained how SAP motivates the move of its commerce solutions to the cloud and which advantages arise for companies as a result of the technology change. His conclusion: "While the SAP Commerce Cloud provides the basis for growth and continuous change, it is now only necessary to ensure that the technological potential of the platform can be fully exploited in its environment - and this is where the right partner can provide support. The goal is a strong and individual market position."

 

In my contribution, I would now like to give an example of how a structured, easy-to-follow process can pave the way to the SAP Commerce Cloud. 

 

 

Is migrating e-commerce infrastructure to SAP Commerce Cloud right for my business?

When a customer asks me whether migrating the e-commerce infrastructure to SAP Commerce Cloud is really the right solution for their company, I like to respond - for once - with a few counter-questions:

Coinage with numbers shown in the foreground

Is your on-premise system causing serious cost pressure?

Eine Person zeigt auf einen Laptop mit dem Handy in der Hand

Is your DevOps team tied up in admin tasks too often? Does maintenance work lead to overload?

Eine Figur springt auf aufsteigendem Pfeilen nach oben

Is your platform prone to unexpected bouts of weakness? Does the performance collapse under increased load?

Zwei Männer unterhalten sich im Büro

Is your environment gradually growing into a patchwork landscape with more and more new special functions?

Eine Hand hält einen virtuellen Chatbot hoch

Are you struggling to deliver an end-to-end, highly personalised omnichannel experience to your users?

Coinage with numbers shown in the foreground

Is your on-premise system causing serious cost pressure?

Eine Person zeigt auf einen Laptop mit dem Handy in der Hand

Is your DevOps team tied up in admin tasks too often? Does maintenance work lead to overload?

Eine Figur springt auf aufsteigendem Pfeilen nach oben

Is your platform prone to unexpected bouts of weakness? Does the performance collapse under increased load?

Zwei Männer unterhalten sich im Büro

Is your environment gradually growing into a patchwork landscape with more and more new special functions?

Eine Hand hält einen virtuellen Chatbot hoch

Are you struggling to deliver an end-to-end, highly personalised omnichannel experience to your users?

The more often "yes" remains as the only answer option, the more urgent the move to a powerful cloud platform that is flexible, resilient and can easily cope with increasingly complex requirements.

Once the decision to move to the cloud has been made, the worry about the upcoming migration effort usually follows immediately. Once you have found the right partner for the migration, they take on the role of pacemaker and lead you from an initial inventory directly to an operational e-commerce platform with ready-to-go functionality.

A straightforward path for the migration to the SAP Commerce Cloud gives you a secure orientation: For example, when it comes to individual customising, you depend on reliable guides.
Stefan Metzger Managing Partner

Migrate faster and more sustainably with the 3-step plan:

A stringently organised 3-step plan provides you with reliable orientation, and you keep track of the migration distance already covered and still to come.

Make your appointment!

Step 1

Alignment

In the first step, an alignment phase clarifies important framework conditions for the start of the platform change.
Check status quo now!

Step 2

Assessment of the initial situation

The second step aims at a detailed, tailor-made assessment of the initial situation. Your deliverables at this point should be: a detailed action plan with cost details, a precise timeline, an estimate of cost savings plus recommendations for the best time to migrate.
Whitepaper Roadmap to efficient cloud migration

Step 3

Implementation phase

The third step leads into the implementation phase: The first step should be a precise examination of the existing infrastructure, resulting in precise process, interface and data models. Tool-supported code checks also provide comparative values for later performance measurements.

The results of the analysis phase serve as a guideline for the entire migration. They form the basis for test scenarios that check the integrity, plausibility and performance of the new platform functions.

Transformation is not a routine

Although a highly standardised logic guides the process, each cloud migration is an individual event with company-specific implications. Therefore, it is crucial to never let the transformation become a routine. Let yourself be guided every step of the way! Get vigilant support even in the period after the cloud platform goes live - Hypercare services offer a high level of security.   

Hohe Leistungsfähigkeit der SAP Commerce Cloud

Conclusion: SAP Commerce Cloud offers reliable standardised processes and at the same time creates room for individual company development. 

The highly flexible performance and environmental behaviour allows the expansion of tried and tested structures with individualised processes. However, the potential can only be exploited if a migration plan precisely geared to the individual case guides the development of the cloud infrastructure. Achieve your promising cloud ecosystem on secure paths!

More Insights

Everything that is important and becomes important.

SAP Commerce moves to the cloud

Instant Insight

SAP Commerce moves to the Cloud - Part 1

SAP Commerce is powerful, a reliable e-commerce platform. And yet SAP has decided to change the operating principle. All system components are to move to the cloud by 2023. We ask: What do we gain from a cloud-based system compared to an on-premise solution?
E-commerce anytime and anywhere

SAP Commerce Cloud

Your SAP Commerce Cloud Migration

With SAP Commerce Cloud, you no longer have to worry about - or even pay for - maintenance, hosting, deployment or support. By upgrading to the cloud, you can significantly reduce your previous operational costs associated with on-prem and create unique omni-channel shopping experiences.
Process Mining

Instant Insight

How does process mining achieve fast and efficient results?

From the ordering process to delivery and receipt of payment, many things can go wrong. With sufficient available data, we make predictions, correct deviations or at least plan for them. What might this look like for the complex area of logistics?

Privacy settings

We use cookies on our website. Some of them are essential, while others help us to improve this website and your experience. With your consent, we use cookies to analyse the usage of our website.

We also use cookies for marketing to help us measure the success of our marketing efforts. In the settings you will find detailed information about the individual cookies, and you can refuse the use of cookies.

You can change or revoke your selection at any time on any KPS.com page in the footer under Privacy Settings.

Essential Cookies

Essential cookies enable basic functions and are necessary for the proper functioning of the website.

Cookie Banner

  • Cookie Name: kps-privacy-settings
    Value: PrivacyLevel_0#a
    Storage Duration: 4 weeks
    Description: This cookie is required to save cookie settings. It is a purely technical cookie.

HubSpot:

  • Cookie Name: __hs_opt_out
    Storage Duration: 6 months
    Description: This cookie is used by the opt-in privacy policy to prompt the visitor to accept cookies again. It is set when you allow visitors to disable cookies. It contains the string "Yes" or "No."

  • Cookie Name: __hs_d_not_tracking
    Storage Duration: 6 months
    Description: This cookie can be set to prevent the tracking code from sending information to HubSpot. It contains the string "Yes."

  • Cookie Name: _hs_initial_opt
    Storage Duration: 7 days
    Description: This cookie is used to prevent banners from being displayed every time visitors access your website in strict mode. It contains the string "Yes" or "No."

  • Cookie Name: __hs_cookie_cat_pref
    Storage Duration: 6 months
    Description: This cookie is used to capture the categories a visitor has consented to. It contains data about those categories.

  • Cookie Name: __hs_gpc_banner_dismiss
    Storage Duration: 3 months
    Description: This cookie is used when the Global Privacy Control banner is dismissed.

  • Cookie Name: hs_ab_test
    Storage Duration: Until the end of the session
    Description: This cookie is used to ensure that visitors see the same version of an A/B test page they were shown previously. It contains the ID of the A/B test page and the ID of the variant selected for the visitor.

  • Cookie Name: __cfruid
    Storage Duration: Until the end of the session
    Description: This cookie is set by HubSpot's CDN provider in accordance with its rate-limiting policies.

  • Cookie Name: ___cfuvid
    Storage Duration: Until the end of the session
    Description: This cookie is set by HubSpot's CDN provider in accordance with its rate-limiting policies.

  • Cookie Name: ___cf_bm
    Storage Duration: Until the end of the session
    Description: This cookie is set by HubSpot's CDN provider in accordance with its rate-limiting policies.

Functional cookies

Functional cookies are used by third parties or publishers to display personalised advertisements. They do this by tracking visitors across websites.

Google Analytics

Cookie Name: _ga
Storage Duration: 2 years
Description: Used to distinguish between users.

Cookie Name: _gid
Storage Duration: 24 months
Description: Used to distinguish between users.

Cookie Name: _gat
Storage Duration: 1 minute
Description: Used to throttle the request rate. If Google Analytics is provided via Google Tag Manager, this cookie is named dc_gtm<property-ID>.

Cookie Name: hide-cookieinfo
Storage Duration: 30 days
Description: Cookie set for querying the cookies.

HubSpot

Cookie Name: __hstc
Storage Duration: 6 months
Description: The main cookie for visitor tracking. It contains the domain, the user token (hubspotutk), the first timestamp (of the first visit), the last timestamp (of the last visit), the current timestamp (for this visit), and the session count (increases with each subsequent session).

Cookie Name: hubspotutk
Storage Duration: 6 months
Description: This cookie tracks the identity of a visitor. This cookie is passed to the HubSpot software when submitting a form and is used for deduplicating contacts. It contains an opaque GUID to represent the current visitor.

Cookie Name: __hssc
Storage Duration: 30 minutes
Description: This cookie tracks sessions. It is used to determine whether the HubSpot software needs to increment the session count and timestamps in the __hstc cookie. It contains the domain, the number of page views (viewCount, increases with each page view in a session), and the session start timestamp.

Cookie Name: __hssrc
Storage Duration: End of session
Description: Whenever the HubSpot software changes the session cookie, this cookie is also set. It determines whether the visitor has restarted the browser. If this cookie is not present when HubSpot manages cookies, it is considered a new session. It contains the value "1" if present.

External media

Content from video platforms and social media platforms is blocked by default. If cookies from external media are accepted, access to this content no longer requires manual consent.

LinkedIn Tag

Cookie Name: bcookie
Storage Duration: 365 days
Description: Browser Identifier cookie to uniquely identify devices accessing LinkedIn to detect abuse on the platform and for diagnostic purposes.

Cookie Name: bscookie
Storage Duration: 365 days
Description: Used for remembering that a logged-in user is verified by two-factor authentication and has previously logged in.

Cookie Name: JSESSIONID
Storage Duration: Session
Description: Used for Cross-Site Request Forgery (CSRF) protection and URL signature validation.

Cookie Name: lang
Storage Duration: Session
Description: Used to remember a user's language setting to ensure LinkedIn.com displays in the language selected by the user in their settings.

Cookie Name: lidc
Storage Duration: 1 day
Description: To facilitate data center selection.

Cookie Name: sdsc
Storage Duration: Session
Description: Signed data service context cookie used for database routing to ensure consistency across all databases when a change is made. Used to ensure that user-inputted content is immediately available to the submitting user upon submission.

Cookie Name: li_gc
Storage Duration: 180 days
Description: Used to store consent of guests regarding the use of cookies for non-essential purposes.

Cookie Name: li_mc
Storage Duration: 180 days
Description: Used as a temporary cache to avoid database lookups for a member's consent for use of non-essential cookies and used for having consent information on the client side to enforce consent on the client side.

Cookie Name: UID
Storage Duration: 720 days
Description: Cookie used for market and user research.

Cookie Name: UserMatchHistory
Storage Duration: 30 days
Description: LinkedIn Ads ID syncing.

Cookie Name: AnalyticsSyncHistory
Storage Duration: 30 days
Description: Used to store information about the time a sync took place with the lms_analytics cookie.

Cookie Name: lms_ads
Storage Duration: 30 days
Description: Used to identify LinkedIn Members off LinkedIn for advertising.

Cookie Name: lms_analytics
Storage Duration: 30 days
Description: Used to identify LinkedIn Members off LinkedIn for analytics.

Cookie Name: li_fat_id
Storage Duration: 30 days
Description: Member indirect identifier for Members for conversion tracking, retargeting, and analytics.

Cookie Name: li_sugr
Storage Duration: 90 days
Description: Used to make a probabilistic match of a user's identity.

Cookie Name: _guid
Storage Duration: 90 days
Description: Used to identify a LinkedIn Member for advertising through Google Ads.

Cookie Name: BizographicsOptOut
Storage Duration: 10 years
Description: Used to determine opt-out status for non-members.

Cookie Name: li_giant
Storage Duration: 7 days
Description: Indirect identifier for groups of LinkedIn Members used for conversion tracking.

Cookie Name: oribi_cookie_test
Storage Duration: Session
Description: To determine if tracking can be enabled on the current domain.

Cookie Name: oribili_user_guid
Storage Duration: 365 days
Description: Used to count unique visitors to a website.

Cookie Name: ln_or
Storage Duration: 1 day
Description: Used to determine if Oribi analytics can be carried out on a specific domain.

Cookie Name: ar_debug
Storage Duration: Session
Description: Supports Google attribution reporting API integration to mitigate signal loss.

Lead Forensics

Cookie Name: __lfluuid
Storage Duration: 10 years
Description: The _lfuuid cookie allows a website to track visitor behavior on the sites on which the cookie is installed. Tracking is performed anonymously until a user identifies himself by submitting a form.

Changing privacy settings

Imprint

Data protection statement