Showing results for 
Search instead for 
Did you mean: 

Moving CAL data

0 Kudos

Hi Experts,

Currently, we provide the CAL that the customer is using for validation on our Azure tenant and subscription. The customer has requested to move the CAL from our environment to their Azure environment, and we are considering the methods to do so. I am investigating the feasibility and recommended steps for each method as I believe there are multiple ways to move the CAL. Below are the methods and questions regarding them:

Method 1: Change the tenant associated with the subscription
Move the subscription with the deployed CAL that is currently associated with our tenant to the customer's tenant.
Question 1: Can this method be implemented?

Method 2: Deploy a new CAL to the customer's subscription and import the current data
Deploy a new CAL to the customer's Azure subscription and import the data from the current CAL by taking a backup.
Question 2: Can existing licenses be reused for the new CAL deployed to the customer's tenant?
Question 3: Please share the steps for exporting/importing data, logs, configuration files, etc.
Question 4: If there are any other methods besides 1 and 2, please kindly introduce them.

Thank you.

Accepted Solutions (1)

Accepted Solutions (1)

Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Mai,

A direct movement of appliances between accounts/subscriptions is not possible.

A backup/restore procedure should technically work on project base.
It will require HANA & Linux knowledge, some additional disk space in source/target for storing the backup (you can add disk space in the CAL console) and a way to transfer the backup files between the two subscriptions.

Rough procedure:
Create an S/4HANA Fully-Activated Appliance (same release) in the target subscription, and there do a restore of the back up taken from the source system.

Kind regards,
Joerg Wolf

0 Kudos

Hi Joerg,

Thank you for your response! It's very helpful.
I would like to proceed with the method you teach me, which is to create the same release in the target subscription and restore the backup obtained from the source system.

Best Regards,
Mai Tanaka

Answers (0)