Import from point-solution platforms to GitLab
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
Today, the importers for GitLab do a good job moving over the core pieces from our direct competitors - for example, moving repositories, merge requests, issues, etc from GitHub. GitLab is a full DevSecOps platform though, so if customers are using other providers for pipelines, security scans, and so on, there is still a gap between migrating into GitLab and being able to fully use GitLab according to your business tooling.
Solution
We should consider importing from point-solution platforms that customers often adopt in order to be more efficient with their toolchain. A small example would be importing from TravisCI to GitLab CI/CD, which blogs are written about. In the future, there are even recommendation opportunities (remove CI code in place of GitLab tooling) or proactive measures (such as updating repository files automatically) to increase a customers time-to-value and adoption of GitLab.