GitLab Retirement Project

Engineering IT GitLab Service will be retired in May 2027.

If you are looking to start using version control, please check out the Campus GitHub Service

If you need to migrate from the Engineering IT GitLab Service, visit our GitLab Retirement Project page.

Go to Campus GitHub Service

Two Migration Paths to GitHub

There are two migration paths, basic and advanced. Basic migration will allow you to migrate just source code and commit history. The more advanced migration process will migrate additional data forms including: wiki, issues, merge requests, and more. 

If you can migrate before October 5, 2026 when GitLab will require on-campus network or VPN connections, you can use the easiest option to export/import process built in to GitHub.

Not sure what you have to migrate or which repositories you use, contact us for help.

 

Basic Migration Process - Just Source Code and Commit History 

If you just need to migration source code and commit history from GitLab to GitHub, check out these two options.

Migrating before October 5, 2026? Use the Easy Basic Migration Process.

Migrating after October 5, 2026? Use the Basic Migration Process (command-line).


Advanced Migration Process - More Data to Migrate

If you need to migrate more than just source code and commit history, you must use the Advanced Migration Process.

The advanced migration process will allow you to migrate more data like:

More data? Use this Advanced Migration Process.

Contact us if you have questions or need assistance.

GitLab Retirement Timeline

Date Change Communication and Links
May/June 2026 Announced Retirement of GitLab service <link to announcement email>
August 2026 No new repositories created <link to newsletter, comms>
October 1, 2026 Project page goes live <link>
October 5, 2026 VPN or on-campus network connection requirement < Targeted message link and date, audience>

Related Knowledge Articles