Steps to migrate a project to GitLab after is accepted in the pilot program

Take a look and be aware what upstream issues and limitations and our issues and limitations we have with GitLab.
Understand that moving to GitLab the project enters in production and it's not a test.
Understand that there are issues we are working with, and that we need your help dealing with them and communicating them to us.
Notify CarlosSoriano for doing a test migration for you. Once you agree it looks good, notify CarlosSoriano to move forward.
Change JHBuild to point to the new repo. Example: https://git.gnome.org/browse/jhbuild/commit/?id=401bccf388a11e6c396ded35b8f243b5b9d47e15
Notify EmmanueleBassi and change Continuous to point to the new repo. Example: https://git.gnome.org/browse/gnome-continuous/commit/?id=893e425851ed19271e36be1ce6500599817636bf
Change the Flatpak builder manifest to point to the new repo, if applicable.

Limitations and issues to consider before moving

Bugbot is not working yet. You can follow the progress subscribing to the bug report
Bugzilla although redirects to the new repo it doesn't show a clue for projects that already moved. Maybe we should put a banner?

These limitations and issues are not blockers for the pilot program, but they are blockers for the full migration and work is being done on them.