Skip to main content

How to Migrate to the Cloud Without Losing Your Mind? Case Study of Cloud Migration at RBI Group

Migrating banking applications to the cloud is a crucial step in the digital transformation of financial institutions. While complex, this process can yield significant benefits such as increased flexibility, scalability, and cost reduction. But how can this operation be effectively carried out without losing your mind? Here's a guide based on the experiences of the CMAP project implemented within Raiffeisen Tech.


  • By Marek Olszewski

CMAP project

In 2021, Raiffeisen Bank International (RBI) launched the Cloud Migration Acceleration Program (CMAP) to accelerate the migration of its banking systems to the cloud. Given the scale of the project (currently operational in 11 countries), RBI opted to collaborate with an external service provider.

The organizational structure of the CMAP project comprises three main departments ensuring its effective management and implementation.

The first is the project management office, serving as the central body responsible for communication and overall project management. They ensure all activities are coordinated and executed according to the established schedule and budget.

The second department is the pool of experts, consisting of specialists from various fields. These experts possess technical, business, and regulatory knowledge crucial for supporting the project at every stage. Their role includes providing necessary expertise and substantive support, critical to the success of the CMAP project.

The third department consists of migration teams ("migration factors"), dedicated groups working for specific banks within the network. These teams collaborate directly with local engineers to ensure smooth implementation of technological solutions in individual institutions. Their involvement allows for adapting global strategies to local needs and requirements.

The CMAP project distinguishes five migration strategies:

  1. Rehost: Moving applications without changing the architecture.
  2. Replatform: Leveraging cloud-native services without altering the database engine.
  3. Refactor: Rebuilding applications for the cloud, which may require code changes.
  4. Retain: Keeping applications in local data centers.
  5. Retire: Phasing out applications from operation.

Based on the migration of over 200 systems and applications, the most popular strategy proved to be replatforming (47%), followed by rehosting (20%) and refactoring (20%). The retain strategy accounted for 13%, reflecting earlier application selection by banks as potential candidates for migration.

Migration phases

The migration process is divided into two main phases. The first phase is the Assessment Phase, involving assessment of applications in the client's environment, data analysis, and creation of the target cloud infrastructure design. This phase meticulously examines current systems and client data to design optimal cloud infrastructure.

The second phase is the Migration Phase, which includes the actual migration of applications, project verification, testing, and post-migration support known as the hypercare period. During this phase, applications are physically migrated to the new cloud environment, followed by verification and testing to ensure everything operates as planned. Post-migration support is also provided to swiftly address any issues and ensure the stability of the new environment.

Key insights from migration

The CMAP project has yielded valuable insights that significantly influenced its development and execution. One key achievement was establishing solution standards across the RBI Group. These standards facilitate cost management, improve security, and streamline process monitoring, enhancing the overall efficiency of the network.

Another crucial aspect was technological flexibility. The CMAP project enabled collaboration with various technologies such as Terraform, CloudFormation, and CDK. This allowed migration teams to expand their skills and adapt to diverse technological challenges.

Building teams was also essential within the CMAP project. The shift from relying on external service providers to establishing internal expert teams enhanced internal competencies and autonomy in project execution.

Managing customer expectations was equally critical, especially in application refactoring. Balancing these expectations with project goals was key to achieving satisfactory outcomes for all parties involved.

Lastly, ensuring resource availability was vital. The CMAP project ensured the availability of local teams and application providers, crucial for the migration's success. This facilitated smooth and effective execution across all project stages.

These valuable experiences not only contributed to the success of the CMAP project but also laid a solid foundation for future technological initiatives.

Summary

Raiffeisen Tech's CMAP project successfully migrated hundreds of applications to the cloud, establishing internal expert teams and setting standards for the entire RBI Group. Despite challenges such as managing customer expectations and resource availability, the project delivered significant benefits and experiences that will be valuable in further digital transformation efforts for banks.

Prefer to watch a video?

Raiffeisen Tech's approach to cloud application migration was the topic of my presentation at the Cloud Computing conference. I discussed the approach to cloud migration within the RBI Group, outlining the project's organizational structure and migration phases. I covered migration strategies and selection criteria, benefits derived from the chosen migration approach, as well as potential challenges encountered during implementation. If you missed the conference, you can view the recording here: