How We Migrated Thousands of Repositories to SaaS With Developer Experience
summary
Booking.com migrates a 70,000-repository GitLab footprint by moving only 10,000 repos to hit 99.5% (finally 99.6%) of developer activity, starting with the 15 GB, 5‑million‑commit big rock that’s cloned 500 times/hour. Teams build a 49‑step runbook, automate it into a CLI then an API and a UI, add a webhook proxy, run migration waves and a self-service migration flow, and reduce on‑prem from 71 boxes to four while turning read‑only to cut the long tail.
AI-written summary · about
chapters (16)
- 0:00Migration challenge
- 2:13GitLab at Booking.com
- 5:24Migrate to GitHub SaaS
- 6:33Decoupling repositories
- 8:17Prioritize by activity
- 9:41Decoupling dependencies
- 10:21Upgrade failures and NFS
- 12:09Flip migration plan
- 13:34Biggest repository first
- 14:38Migration waves
- 15:43Automate migration
- 16:26Manual to automated
- 17:28Self-service tooling
- 18:13Self-migration tool
- 19:15Achieving 99.6% migration success
- 19:56Migration epilogue
related talks
24mA One Woman Show of Migrating an Entire R&D SCM From Bitbucket Cloud to a Self-Hosted GitLab
38mHow We Scaled GitLab For a 30k-employee Company
29mScaling Across the Enterprise
47mMigrating 1TB to GitHub: Lessons Learned from the Field
21mDriving Cultural Change to Improve Software Development and CI/CD
20mMigrating from BitBucket to
46mFrom 1,000 to 5,000 Users: Scaling GitLab Without (Too Much) Pain
21mFighting Git Workflows