Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Category Direction - Importers

Last Reviewed: 2020-02-27


Thanks for visiting the direction page for Importers in GitLab. If you'd like to provide feedback on this page or contribute to this vision, please feel free to open a merge request for this page or comment in the corresponding epic for this category.

Problems to solve

The mission of GitLab importers is to provide a great experience importing from self-managed GitLab to and from other source code management platforms such as GitHub and BitBucket.

A typical organization looking to adopt GitLab already has many other tools. Artifacts such as code, build pipelines, issues and roadmaps may already exist and are being used daily. Seamless transition of work in progress is critically important and a great experience during this migration creates a positive first impression of GitLab.

What's next & why

At the moment, the Import group is focused on enabling adoption through the introduction of group import/export. Additionally, our UX group is looking into the overall import user experience in order to create a more positive first impression when migrating to GitLab.

While this group focuses on building importers, it can often happen that importers are a higher priority for another group in gaining adoption of their features. When this happens other teams should not wait for their importer to become a priority of the Import group, but should just prioritize the work themselves since everyone can contribute.

Maturity plan

Our maturity plan is currently under construction. If you'd like to contribute feedback on areas you'd like to see prioritized, please add them as comments in the epic.