Planning your migration to SAP HANA Cloud
You have decided to migrate to SAP HANA Cloud, that is great! Before you can start, it is really important to plan your migration in detail. Fortunately, the self-service migration tool can help you do that.
Let’s start with the pre-requisites to migrate. We highly recommend that you start by becoming familiar with some important documentation:
- SAP Note 2868742 – Differences between SAP HANA Cloud and SAP HANA Platform for SQL, SQLScript and SAP HDI (SAP HANA Deployment Infrastructure)
- SAP Note 2946614 – End-of-Maintenance of SAP HANA 1.0 on SAP Cloud Platform
- SAP Note 2937069 – SAP HANA Cloud Migration FAQ
- Feature compatibility documentation
Next, we recommend you consider the connectivity and replication technologies available for SAP HANA Cloud.
If you are looking to send data to SAP HANA Cloud, you will soon be able to use the SAP Cloud Connector. You can also use SDI with RTR for HANA 2 SPS04 or later, or SDI with a DP Agent for HANA 2 SPS03 or lower.
If you want to connect and replicate data from SAP HANA Cloud, you can use one of two options:
- Using a DP Agent with JDBC to HANA on-premise
- Using ODBC and a DP Agent for several cloud data sources
We recommend as well that you assess your current applications and determine which, if not all, should be migrated. If you do not need to migrate all of them, this might make the process less complex. It is important, however, to know which applications are relevant and then be able to compare this to any warnings or errors you get during the pre-migration check.
The next pre-requisite is to purchase and set up your SAP HANA Cloud instance, which will be the target for the migration. You can learn how to do this in detail by checking our Onboarding Guide to see how to provision your first instance.
The final pre-requisite is to create a user called DMUser. This user will be the one used for the migration and it needs to be created by the SYSTEM user and have specific privileges. You can find all the details and SQL statement to create this user in our technical documentation.
Artifacts that cannot be migrated with the self-service tool
The self-service tool can easily migrate all of your data and catalog items, but it does have some limitations. Mainly the tool cannot migrate HDI containers and application bindings.
If you are using HDI containers, please see this tutorial on how to manually migrate these containers.
If you are using custom applications, please see here how to recreate the bindings.
Read more about manual migrations here: Migrating Independent Databases to SAP HANA Cloud
An important recommendation is that, if you don’t have it already, you create a non-productive source database that can be used for the checks and necessary adjustments. This will allow you to safely make changes recommended by the pre-migration check, run it again, until you are ready to migrate.
Be aware that the self-service migration tool does not make any changes on any source database you use – even a non-productive one. But there are benefits to having a non-productive source system, allowing you to do incremental changes as needed to get to a successful migration.
Running the pre-migration check
The pre-migration check is an important part of the self-service migration for SAP HANA Cloud tool. It examines your source database to find any incompatibilities and issues with a migration. You can run the pre-migration check as many times as needed to complete your planning and preparation.
- To get started, simply go to the SAP Cloud Platform cockpit.
- Enter the subaccount where your SAP HANA Service is.
- Enter your space.
- On the left hand-side of the screen, click on SAP HANA Cloud Migrations.
- Click on New Migration.
- Fill out the Name and Source Type fields.
- Click on Create.
- You will be taken to the Migration Dashboard. Here, select your source instance.
- Enter your database instance username and password for the source instance.
- Click on Check Compatibility with SAP HANA Cloud.
- Once the compatibility check is completed, you will see the results divided into two lists: Database Compatibility and Applications Compatibility.
- You can switch between these two categories by clicking on the buttons under Incompatibilities. You will also see a number of results for each category next to the name of the category button.
As you scroll down to see any errors or warnings, you will get the following information about each of them: Severity, Incompatible Feature, Feature Description, and Incompatible Objects.
To understand more about the results and how to handle them, continue to the article on Preparing your migration.