Recommendations for Go Live

[former_member654580]

Hello Experts I hope you are well I am writing to request your support and recommendations for Go Live. What considerations should be taken into account for the Go Live?What data should be taken into account for transport to the PRD environment and what should be configured in that environment?

How and where is the transport or export to PRD?

Best regards

Elio C.

[SCHNEIDERT · Accepted solution]

Hi Elio,

big topic and quite complex to answer this one in short. But let me try in a few words. There are different things to consider concerning configuration:

1. You have to bring your Customizing/Configuration to the productive system. This is done via the „Manage Your Solution“ app in your Test Tenant. Here you go to „Configure Your Solution“, select all items and set the status to „Confirmed“. (After a first transport you have to create a change project in the Manage Your Solution App to do these steps again). After that you can click the „Proceed to Run Phase“ button. Remember: This is for your Configuration Settings.

2. For your Extensibility Items (like Custom Fields, Segmentation Configuration and so on) you have to go to the „Export Software Collection“ app. Create a Collection and add the items of your choice to the collection. Do a check so that there are no inconsistencies and export your collection.

3. In Production Tenant you go to the „Import Collection“ app. Here you can see your exported and transported Configuration and import it to your system.

So this is the main part for configuration transport.

4. In Addition to these main steps you should consider downloading the user roles (if they are customized) and upload them to P-System.

5. All the configuration concerning communication systems and arrangements have to be executed in the production tenant itself and cannot be transported of course.

In the Onboarding Guide here you can also find the chapter "Preparations For Productive Use" which could help you with step-by-step tutorial.

This is just for the transport of configuration and extensibility. Of course before Go-Live there are more things to consider like IP-WarmUp, Integration Tests, Key User Training and so on. So steps you have to do in every project regardless the product that is used.

Hope that helps to make it a little bit clearer. 🙂

BR Tobias

[anypre · Accepted solution]

when click on the onboarding guide here url, the page renders "Sorry, you are not authorized to see this page". Do you know how to get access to this content?

[SCHNEIDERT · Accepted solution]

Hi speakre,

think this is because of an outdated version that I linked above. Try that one: https://help.sap.com/docs/SAP_MARKETING_CLOUD/8982c0f28bca4839b563f10df1f8c259/395ed6da254342b78511b...

BR Tobias

[vervinckt_joyca]

Nice overview Tobias 🙂

One addition,

Check the timing of your go-live vs the Upgrade schedule.

Each quarter, a new release is pushed to the cloud systems, first to the Test tenant, then 2 weeks later to the Production tenant. But in this period, you cannot do any transports to production. So you can't do a go-live in that period, and you also don't want a go-live right before the "freeze" period as you cannot fix potential errors in production during that period.

Also know that you only transport configuration. Data (customers, accounts, email templates, landing pages, campaigns, ...) cannot be transported. Also communication arrangements are set up on production directly.

Kr,

Joyca

[former_member9501]

Besides the very good summary from Tobias and Joyca, I can also recommend to have a look at the following CX Works article we have published:

Validate the Go-Live Readiness of your SAP Marketing Cloud Project

Best Regards,
Frederik

[Former Member]

eliocentenob, regarding to your last questions:

1. There is, but they're a special team and you will need a separate contract with them.
2. It's always recommended to go live a couple of weeks after the upgrade.
3. Yes. Communication users, systems and arrangements. Also content, segmentation models, target group, campaigns, sender profiles and other artifacts.
4. Yes, you have to migrate the data in PROD too.

Let me know if you need more help. Regards,

[former_member654580]

Thank you all very much for your valuable contributions.

I am preparing and doing a check that everything that was configured is Okay.

Of course doubts continue to arise

1.-There is an SAP support before, during and after the live launch, which I asked why I had the experience with SAP Commerce Cloud and they had so much time.

2.- vervinckt.joyca I understand, according to the Upgrade calendar the ideal is to do the Go live after the PRD update

3.- schneidert All communication agreements must be configured again in PRD

4.- frederik_lipowsky, The project has been complicated but maybe it doesn't have several things listed, it's SMC with C4C. recently a migration of contacts and accounts was made from C4C to SMC, that migration must be done in PRD?, if I apply the logic of the ERP understanding if, to do everything again, those contacts and accounts in quality are not exported to PRD, or I'm wrong.

Best regards

Elio C.

[SCHNEIDERT]

eliocentenob yes exactly. You have to setup the communication agreements in P-tenant again. The URLs of the integrated systems like C4C and also the middleware like CPI are different from the ones in Q-system.