Timeline
Key dates, milestones, and responsibilities for the Bitbucket to GitHub migration.
Timeline
The migration must be completed before March 26, 2026 — this is when the Bitbucket plan expires.
Key Dates
| Date | Event |
|---|---|
| Now → March 12, 2026 | Continue pushing all code to Bitbucket upstream as usual |
| March 9, 2026 | Rohit Gaikwad begins migrating Fusion and Fusion Worker to GitHub, along with DevOps pipeline changes |
| March 12, 2026* | Bitbucket hard stop — merge access revoked, start mirroring changes to GitHub |
| March 26, 2026 | Bitbucket plan expiration — all repos must be on GitHub by this date |
| Post March 26, 2026 | All new development moves exclusively to GitHub |
* March 12 is the tentative date for the Bitbucket hard stop. This is still pending final confirmation.
Responsibilities
| Person | Responsibility |
|---|---|
| Rohit Gaikwad | All infrastructure changes — code mirroring, pipeline setup, DevOps workflows |
| Sai Tharun | GitHub migration execution — repo transfers, configuration, coordination |
Migration Order
| Priority | Service | Notes |
|---|---|---|
| 1 | Fusion | Starting week of March 9 — along with pipeline/DevOps changes |
| 2 | Fusion Worker | Starting week of March 9 — along with pipeline/DevOps changes |
| TBD | Other services | To be announced |
Important Notes
- Bitbucket repos will still be accessible after migration — there is no loss of backup. The repos won't disappear, but all new development must happen on GitHub.
- Fusion and Fusion Worker are first because they are low-hanging, service-based repos that are straightforward to migrate with pipeline changes.
Questions?
For any queries regarding the migration, reach out on Slack: #github-migration