Professional Services using Direct transfer as default importer
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
While the long-term goal for the Import group is to provide all the GitLab importing capabilities needed by our customers in our application, we recognize that GitLab's current capabilities may not support specific migration scenarios. GitLab Professional Services team supports customers with more challenging set-ups.
Currently Professional Services team uses Congregate tool to orchestrate user, group, and project import API calls in order to help customers automate scaled migrations.
With completed Direct transfer we aim to substitute the part of Congregate which is about migrations of groups and projects between GL instances.
Note: As Congregate also supports migrating container registries and maven packages, fully retiring Congregate will require more effort than migrating groups and projects between GL instances.
This issues is to gather requirements, that have to be met to enable Professional Services team to use Direct transfer as their default tool. After we gather and understand all the problems, we will be better equipped to break them down and plan to solve them.
What needs to be done/addressed, so that PS can start using Direct transfer
- PS need to see E2E tests for migrating with Direct transfer passing. E2E tests still need to be set up by PS, this is planned by end of November 2022.
- Safe failures for the bulk import (More details needed)
- Some information is missing in the import response so our Professional Services diff reports don’t fully work (more details needed).