<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=395621) </details> <!--IssueSummary end--> <!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ### 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](https://blog.clairvoyantsoft.com/migration-from-travis-ci-to-gitlab-ci-7c08397a2c3). 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.