howto/git.md

@@ -290,12 +290,13 @@ See [issue 36][] for further discussion.
 
 ### How to migrate a Git repository from legacy to GitLab?
 
-Important: this policy is still being debated. It is not clear if any
-or all repositories should be migrated to GitLab, see [issue 36][]
-for the discussion on this topic.
+Moving a repository from Gitolite to GitLab proceeds in two parts. One
+part can be done by any user with access to GitLab. The second part
+needs to be done by TPA.
+
+#### User part: importing the repository into GitLab
 
-As an example of a repository migration, I have moved the wiki from
-gitolite to gitlab just now. I have followed the following procedure:
+This is the part you need to do as a user to move to GitLab:
 
  1. import the Gitolite repository in GitLab:
  
@@ -312,9 +313,16 @@ gitolite to gitlab just now. I have followed the following procedure:
  
     This will import the git repository into a new GitLab project.
 
- 3. if the repository is to be archived on GitLab, make it so in
+ 2. if the repository is to be archived on GitLab, make it so in
     `Settings` -> `General` -> `Advanced` -> `Archive project`
 
+ 3. [file a ticket with TPA](https://gitlab.torproject.org/tpo/tpa/team/-/issues/new) to request a redirection. make sure
+    you mention both the path to the gitolite and GitLab repositories
+
+That's it, you are done! The remaining steps will be executed by TPA.
+
+#### TPA part: lock down the repository and add redirections
+
  4. make an (executable) `pre-receive` hook in `git-rw` with an exit
     status of `1` warning about the new code location, example: