Es
Eng

Peru's leading bank accelerates its technological transformation with GitHub Enterprise Cloud

Customer
Industry: Financial
Partner
GitHub
Products and services
GitHub
Sector
Country

An obsolete platform that limited innovation

Our client, one of the most important financial institutions in Latin America, faced a challenge that many organizations undergoing technological transformation are well aware of: a critical tool for their IT operation that had remained behind. Its source code management platform, based on Bitbucket on-premise, no longer met modern security, scalability and collaboration standards.

This complicated maintenance tasks, jeopardized code governance, and made coordination between teams difficult. In addition, the lack of updates prevented the use of conventional migration methods and generated internal resistance to changes. With more than 19,000 repositories in play and multiple development cells involved, the need for a technical, as well as a strategic, solution was urgent.

The path to GitHub Enterprise Cloud: A solution designed to scale

The decision to migrate to GitHub Enterprise Cloud (GHEC) responded, on the one hand, to a technological need, but also to a cultural need. It had become key to promote more agile and secure work environments, with advanced CI/CD, version control and code review. But a migration of this magnitude required more than a simple implementation.

This is where CleverIT comes into play, with a team specialized in GitHub solutions, capable of carrying out complex technological transformations, ensuring a fluid, personalized process aligned with our client's banking operation.

A tailor-made process for a massive challenge

The migration strategy was carefully designed: Eight progressive waves were defined to address the nearly 20,000 repositories in an orderly manner, without compromising operational continuity. A specific tool, AnsibleMig, was created, developed with infrastructure as code and designed to clone repositories from Bitbucket to GitHub under strict standards defined by our client.

This solution, integrated with GitHub Actions and based on customized workflows, made it possible to automate the migration process, reducing manual errors and accelerating execution. CleverIT's role was fundamental to accompany internal teams throughout the process, with training, joint planning and ongoing support during and after the migration.

The impact of the partnership between GitHub and CleverIt

Trust in the architecture of GitHub Enterprise Cloud, combined with CleverIt's in-depth knowledge of automation, change management and GitHub solutions, allowed us to overcome multiple and obtain key results:

  • Historical and productive repositories migrated to 100%.
  • A structured transition to a new repo governance, improving the management of roles and permissions.
  • Participation of development cells in the validation of the process, evidencing a change in internal culture in the face of modernization.
  • A safer environment with better code review practices, favoring the delivery of more robust products.

Results that drive innovation

Today our client not only has a modern, scalable and secure platform, but he is actively migrating his CI/CD flows to GitHub Actions, consolidating a technological ecosystem ready for the future.

This case demonstrates how a well-designed and executed migration, accompanied by a specialist team such as CleverIt, goes far beyond moving code from one repository to another. It's about creating optimal conditions for innovation, transforming development culture and building solid foundations for scaling digital products and services.

For organizations with high-level operations and a focus on security such as a bank, strategic alliances with GitHub and CleverIt are the engine that makes this technological evolution possible.

Improve your development and boost your productivity with CleverIt

Send your message and we'll help you!
attach icon
Attach file
maximum: 10MB
Thank you. We have received your shipment.
Oops! Something went wrong while submitting the form.