Skip to Content
Author's profile photo Former Member

How to Migrate a Productive CRM System to the SAP HANA™ Platform

You might have picked up the news: SAP’s own CRM system now runs productively on the SAP HANA platform. In this blog, you will learn how SAP’s IT organization managed to migrate one of the world’s largest CRM systems to the SAP HANA platform in only 2.5 months. 

So how was this change managed? And what are the lessons learned? 

General Information

From a technical point of view, migration to the SAP HANA platform involves two steps: 

Both of these steps are well-known SAP practice and both have to be performed on one cutover weekend. However, some special preparations are required.

Prerequisites and Preparation

Before making any significant system change, it is important to do your housekeeping thoroughly, such as re-enforcing your archiving system and deleting unnecessary data (for example, change documents). This will keep your system lean and reduces the migration downtime.
Based on test upgrades and migration rehearsals, you can figure out how to deal with the largest tables during the migration. The largest tables can be split during the export, which will significantly reduce the migration runtime. Testing is always very important, namely functional tests of the upgraded system, backup/restore tests, and failover tests of the SAP HANA high availability solution (depending on the SAP HANA hardware vendor). For the SAP HANA migration, you need to focus on load and performance testing. This allows you to optimize the system for SAP HANA before going live. Some tables  perform better in column or row store, and some expensive statements need to be optimized.
Finally, you should consider performing at least two rehearsals of the entire procedure before production cutover.

Production Cutover

The ramp-down procedure is a standard process: unscheduled long running jobs, block-out the end users, clean up queues, isolate the system, and finally shut down the system. Cutting the high availability cluster at this stage has some significant advantage: One side is used for the actual upgrade and migration while the other side remains original. This original system can be used as a quick failback in case something goes wrong. After successful migration, this original system can be used as a reference system (for audits, for example).
The next step is the “upgrade” installation of the EHP2 for SAP CRM 7.0 on SAP HANA (technical CRM 7.12 based on SAP NetWeaver 7.40). Since this is only a minor EHP upgrade, the EHP2 installation only took 3 hours.
The actual migration consists of a DB export followed by a SAP HANA 1.0 SP5 import (in the meanwhile export and import can run in parallel). Large tables are split during the export and cluster tables are de-clustered since SAP HANA does not support cluster tables. The export of 3 TB took us 7 hours, and the import to SAP HANA 12 hours including the declustering. During the migration runtime, the application servers can be upgraded for SAP HANA.
After successfully migrating, it is essential to carry out some checks to verify that all tables and rows have been migrated properly and the dictionary is consistent (package checker, table checker). It also makes sense to perform additional content checks for the most important data (such as your sales pipeline).  
The ramp-up requires minimal effort as there is hardly any post-processing. Before opening the system, a spot check allows you to check whether everything in the migrated system is correct. End users should be ramped up with the assistance of a support team.

Lessons Learned

The original row-compressed database size of 3 TB converts to 1.1 TB on SAP HANA. About 15,500 business users are supported, of which 5000 are “active” users with more than 400 steps each week. The entire OS/DB-migration project took 2.5 months.
Performance is key. Start early with load testing to optimize the performance. During testing, we found that SAP HANA is on average significant faster (search improved up to a factor of 250). However, some transactions should be optimized for the SAP HANA platform. During the first week of production with SAP HANA, it is advisable to have a support team of SAP HANA and SAP CRM experts to help fine-tune the system.
To conclude, the entire SAP HANA migration can easily be performed on a weekend. If this is not sufficient time, you should consider the nearly zero downtime option using SLT replication

References and Further Information

Best regards, Peter Boegler, Enterprise Architect and
Cutover Manager, SAP CRM on HANA

Assigned Tags

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

      Good one! Thanks for your blog contribution, Peter.

      It is good to have such articles as we are focussing ourselves as a knowledge company now.



      Author's profile photo Former Member
      Former Member

      Thanks for this article.

      Could you give more insights on Java server capability in SAP CRM on HANA?



      Author's profile photo Former Member
      Former Member
      Blog Post Author

      Actually we migrated only the ABAP side to SAP Hana. The Java system remaines unchanged and is still working fine with the SAP CRM on SAP Hana.

      Best regards


      Author's profile photo Former Member
      Former Member

      Great Content! Shared it to all the networks i got !

      Author's profile photo Former Member
      Former Member
      Blog Post Author

      Update: The system is now also running HANA high availability and disaster tolerance by replication to a secondary system in a second  data center.