Skip to Content
Author's profile photo Majid Ahmed

Moving Your C4C Solution From Test to Production – The Copying Process

Moving Your Solution From Test to Production – The Copying Process and Duplicate Work Required

When the test solution profile is copied over, only certain configurations are copied to a new (fresh) production tenant.

Many customisations have to be either imported or manually redone in the production tenant.

I have highlighted below the copying processes and additional work that is required in the production tenant.

The lists below are in no way exhaustive but will serve to provide a guide as to the work required during the move from the test C4C solution to the new production system.

Initial test system copying by SAP to the new production system will only include:

The scope

All the fine tuning entries

KUT adaptations, extension fields,    (as long as non previously exist in Production)

Page layouts & code list restrictions  (as long as non previously exist in Production)

Level 0 master data objects:

These will be copied over to the staging area of the migration workbench but will need to be manually committed to the new production tenant:

BANK_DIRECTORY (bank directories)

ORG_CENTER (organizational structure)

JOB (jobs)

PRODUCT_CATEGORY (product categories)

L0_TRANSPORT_LANE (transport lanes)

L0_TRANSPORT_ZONE (transport zones)

Level O master data is automatically transferred to migration templates which then sit in the staging area as prepopulated templates awaiting import by the user into the production tenant.

Customisations Requiring Export from Test and Import into Production System

Many configurations that have been created in the test tenant will require exporting out of the test system, saving on to your desktop and then importing into the new production system via the import function in each of the respective business objects or workcentres.

The non exhaustive list below gives you an idea of the type of customisations requiring export from Test then import into Production:

Code list mapping

ID mapping

Customised and New Reports

KPIs & Dashboards


Custom objects

Language Adaptations

OData service

Organisation chart (if not accepted via Level 0 data transfer)

Lead routing

Realignment runs

Customisations which have to be manually redone in the Production tenant.

There are some customisations which cannot be copied or imported into the Production tenant.

Below are some of the customisations which have to be manually redone in the production system.

Business roles

Workflow rules

Work Distribution

Email and fax settings

Service Level Agreements

Mashup authoring

Report assignment to workcenters

The extent and nature of the replication work required will of course depend on the scope of the solution being implemented.

I hope this helps to guide fellow SCN users during their project implementations.



Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Sam Kovatovich
      Sam Kovatovich

      Hello Majid,

      Thank you so much for this post, it is very helpful.  I was also hoping you might be able to point me towards the correct reading material so that I can learn how to perform some of these copying tasks.  For example, I have some reports in my test tenant that I would like to copy to my production tenant.  Can you point me towards the reading material that shows how I can perform this task?


      thank you very much in advance.


      Author's profile photo Majid Ahmed
      Majid Ahmed
      Blog Post Author

      Hi Sam


      As a point of reference and learning please refer to the content here SAP Hybris Cloud for Customer Business Analytics Guide


      For downloading a custom built report go into Silverlight of the test tenant, then to Business Analytics -> Upload/ Download. Select the download tab, from the new window that opens, search and select the report you wish to download and hit "download". You can download Dashboards, Data Sources, Key Figures, KPIs and Reports. If you decide to download a report, the download will also include the underlying datasources, keyfigures and KPIs.


      The download will be created as an XML file which needs to be saved to your desktop. In your production tenant, go to Silverlight > Business Analytics > Upload/Download and select the upload tab. Simply select the XML file downloaded from the test tenant and and press upload. Your report will now appear in you reports list.


      Hope this helps.




      Author's profile photo Rahul Shah
      Rahul Shah

      Hi Majid,

      Thank you for this post, and especially for the link to the Analytics guide.  I think there needs to be a lot more literature on this.  My question is about subsequent objects.  In the guide, it doesn't mention that key figures are brought in when you download/upload a dashboard, but in my experience, they do come.  Also, when I brought in my dashboard, it didn't come cleanly.  I still had to go into design mode, hit next next next, and then it displayed properly.  In this case, I uploaded the report first, then the dashboard.  In your experience, is there a sequence that works better than others?  For example, should I have uploaded the dashboard first, then the report?  Is it just a necessary evil that I still have to go in and tweak my dashboard after upload?  Even though it says my key figures come in with the dashboard, should I still import them separately anyway?


      Thank you

      Author's profile photo Former Member
      Former Member

      Hello Majid,

      Thank you so much for this post, exactly the info i was looking for! There is one more question i have. Is there any possibility to move/export customized/adapted homepage from one tenant to another? I mean that i have customezed homepage with tiles for reports and now i want to save this adaptation and use it at production. how can i do it?

      Author's profile photo Apoorva Mahale
      Apoorva Mahale

      Thank you for the checklist!