I ran into the same issue as well. I setup the access token in my account at gitlab.com as well as the enabling the bulk_import_projects feature flag as their instructions state.
I also created the users that we have in our top level namespace on gitlab.com in the self hosted gitlab instance with the same usernames/email addresses. I was hoping that this would satisfy the member migration requirements:
Members (Introduced in 13.9) Group members are associated with the imported group if:
- The user already exists in the target GitLab instance and
- The user has a public email in the source GitLab instance that matches a confirmed email in the target GitLab instance
I experienced the same issue as you where the top level namespace group, subgroups, and projects were created but they failed to import anything from the gitlab.com projects and I see errors relating to the failure to import. The BulkImports::NetworkError was the error i saw in all of the failed migrations. In the gitlab issue referenced above, it looks like the cause of this is temporary server unavailability. When i tried to migrate the top level group, this included over 70 projects.
I’m going to create a test group with a project on gitlab.com and i’ll attempt to import that to my self hosted instance to see if it works. I’m wondering if the large number of projects in the migrated group are causing the failure.