Pharma leader creates a unified developer environment after a strategic acquisition

Pharma leader creates a unified developer environment after a strategic acquisition

Following its multi-billion-dollar acquisition of a biotech firm, a global pharmaceutical company partnered with Modus Create to migrate nearly 900 repositories and 300 developers from the acquired firm’s GitHub Enterprise Cloud into its own enterprise environment. Navigating user overlaps, stringent security protocols, and complex regulatory requirements, the platform migration was completed ahead of schedule and within budget. As a result, the pharma giant has better control over its repos and has saved $10K per month in operating costs.

Our work involved

• Migration assessment
• GHEC migration
• Whiteglove support
• Licensing cost management
• Security and compliance

A global pharmaceutical company has partnered with Modus Create for over a decade to evolve into a technology-driven platform company. In 2023, it made a multi-billion dollar acquisition of a biotechnology company renowned for cancer research.

The sheer scale of acquisition meant new challenges in creating a unified developer environment as both the pharma and biotech firms had their own separate GitHub Enterprise Cloud (GHEC) environments. The existing setup wasn’t ideal for collaboration and needed a strategic and secure consolidation.

Challenge

High-stakes GitHub Enterprise Cloud migration with a tight deadline

Operating separate GHEC enterprises meant the pharmaceutical company was paying for two sets of licenses while managing code across fragmented systems. Platform migrations at this scale are always intricate, but several factors made this one particularly challenging:

• Different cloud infrastructures: The biotech firm operated on Google Cloud & Azure, whereas the pharma company relied on AWS, raising concerns about cross-platform migration.
• Identity overlaps: Many developers had separate biotech and pharma GitHub accounts, making it difficult to map commits, teams, and permissions.
• Security & compliance risks: GitHub Actions and Secrets were critical to the biotech’s workflows, but some of GitHub’s migration tools do not transfer encrypted secrets automatically, posing a potential operational security or compliance risk.
• Regulatory & timeline pressures: Some teams feared platform migration could disrupt key project deadlines or impact regulatory commitments.

Moreover, the biotech company’s GitHub license was set to expire in early 2025, creating a strict timeline to complete the migration before renewal. Therefore, the pharma company reached out to Modus Create to plan, implement, and execute the GitHub migration in less than six months.

Solution

A unified, cost-efficient GitHub environment

Phase 1: GitHub Platform Migration assessment

Goal: Establish a clear migration strategy and scope.

Modus Create’s architects and DevSecOps experts kicked off the project with an assessment to evaluate migration scope and feasibility. They evaluated existing development environments, internal processes, and frameworks and recommended narrowing the scope of the migration.

The Modus team suggested limiting the platform migration to GitHub repositories and postponing Terraform and cloud migrations to reduce complexity and risk. This approach would prove vital later as it would help minimize resistance to change and finish the migration on time.

Phase 2: Preparing the biotech team

Goal: Ensure a smooth onboarding process for all new developers.

Next, we invited all remaining team members from the acquired biotech company who did not yet have accounts in the pharma company’s GitHub enterprise. The Modus team worked closely to map permissions for the corresponding accounts to the pharma’s environment, ensuring consistent permissions and retaining the biotech’s role structures.

Modus also resolved duplicate accounts by consolidating contributor accounts with single sign-on and a parallel set of teams. This phase was crucial as it ensured that common challenges associated with user roles and access were resolved before the platform migration.

Phase 3: Proof of concept and initial migration

Goal: Demonstrate success with a small, low-risk batch.

The project involved moving over 900 repositories. Platform migrations of such scale always invite concerns from development teams. To mitigate risks and address potential objections, we conducted a pilot migration on a small set of low-risk repositories. This allowed teams to validate processes, test configurations, and ensure workflows would not be disrupted.

This phase provided critical insights that helped refine the bulk migration process, improving efficiency and addressing key concerns from dev teams that were initially resistant to change.

Phase 4: Bulk and critical repository migration

Goal: Migrate all repositories with minimal disruption.

Once confidence was established through the initial migration, Modus proceeded with the bulk migration of the remaining repositories. This phase involved:

• Leveraging automation: We adapted a previous project’s GitHub migration scripts to significantly reduce manual effort.
• Ensuring secrets transfer: Instead of copying repositories via the GitHub Enterprise Importer-which wouldn’t preserve secrets-we performed repository transfers wherever possible to maintain GitHub Actions and Secrets integrity.
• White-glove support: We provided real-time troubleshooting and dedicated war-room sessions for high-stakes teams, ensuring they had complete confidence in the process.
• Flexible scheduling: Critical teams were given control over migration timing to avoid major project disruptions.

Phase 5: Post-migration support

Goal: Optimize security, governance, and developer experience.

Following the migration, the Modus Create team focused on finalizing security measures, governance policies, and operational efficiencies. This included:

• Automated metadata standardization: We created a custom metadata YAML file for all migrated repositories to align them with enterprise security policies.
• Repository cleanup and archiving: Teams were encouraged to retire or archive obsolete repositories to reduce security risks and maintenance burdens.
• Security tool integration: We facilitated a transition from a mixture of legacy security tooling to the pharma company’s existing SonarQube and TruffleHog-based secret scanning, aligning all repositories with enterprise security standards.

Impact

A unified, cost-efficient GitHub environment

• $10,000 saved per month in redundant GitHub licensing costs.
• 900+ repositories migrated, ensuring a unified developer experience.
• 300 developers onboarded seamlessly with minimal disruption.
• Lowered security risks by enforcing standardized governance policies.
• Reinforced stronger collaboration across acquired teams, with a single GitHub environment improving efficiency and compliance.

With this platform migration, the pharma company has laid the foundation for faster innovation, reduced complexity, and enhanced security, ensuring that its developer ecosystem remains future-proof.