[{"data":1,"prerenderedAt":819},["ShallowReactive",2],{"/en-us/blog/github-to-gitlab-migration-made-easy":3,"navigation-en-us":42,"banner-en-us":452,"footer-en-us":462,"blog-post-authors-en-us-Fernando Diaz":700,"blog-related-posts-en-us-github-to-gitlab-migration-made-easy":714,"blog-promotions-en-us":757,"next-steps-en-us":809},{"id":4,"title":5,"authorSlugs":6,"authors":8,"body":10,"category":11,"categorySlug":11,"config":12,"content":16,"date":20,"description":17,"extension":26,"externalUrl":27,"featured":14,"heroImage":19,"isFeatured":14,"meta":28,"navigation":29,"path":30,"publishedDate":20,"rawbody":31,"seo":32,"slug":13,"stem":36,"tagSlugs":37,"tags":40,"template":15,"updatedDate":27,"__hash__":41},"blogPosts/en-us/blog/github-to-gitlab-migration-made-easy.yml","GitHub to GitLab migration the easy way",[7],"fernando-diaz",[9],"Fernando Diaz","If you are using different CI/CD tools and are considering migrating over to\nGitLab, you may be wondering about the difficulty of the migration process. Migration is usually a concern for [DevSecOps](https://about.gitlab.com/topics/devsecops/) teams when considering a new solution. This is due to the fact that migrating may involve heavy lifting. However, migrating to the GitLab AI-powered DevSecOps\nPlatform can be extremely simple and I will show you how step by step.\n\nIn this blog post, we will go over how to migrate from GitHub to GitLab using our [project import](https://docs.gitlab.com/user/project/import/)\nfunctionality. Manually migrating GitHub Actions to GitLab pipelines will be covered as well. I have also created a video going over the migration process for those who prefer that format:\n\n\u003C!-- blank line -->\n\n\u003Cfigure class=\"video_container\">\n  \u003Ciframe src=\"https://www.youtube.com/embed/0Id5oMl1Kqs\" frameborder=\"0\" allowfullscreen=\"true\"> \u003C/iframe>\n\u003C/figure>\n\n\u003C!-- blank line -->\n\n## What data can be migrated from GitHub to GitLab?\n\nGitLab's built-in importer allows for GitHub projects to be automatically migrated into GitLab. The built-in importer is accessed directly from GitLab's project creation UI. From the UI, you can select what data you wish to migrate to GitLab.\n\nThe data that can be migrated includes the following:\n\n* Repository description\n\n* Git repository data\n\n* Branch protection rules\n\n* Collaborators (members)\n\n* Issues\n\n* Pull requests\n\n* Wiki pages\n\n* Milestones\n\n* Labels\n\n* Release notes content\n\n* Release notes attachments\n\n* Comment attachments\n\n* Issue description attachments\n\n* Pull request description attachments\n\n* Pull request review comments\n\n* Regular issue and pull request comments\n\n* Git Large File Storage (LFS) objects\n\n* Pull request reviews\n\n* Pull request assigned reviewers\n\n* Pull request “merged by” information\n\n* Pull request comments replies in discussions\n\n* Pull request review comments suggestions\n\n* Issue events and pull requests events\n\nGitHub and GitLab have different naming conventions and concepts, so a mapping must be performed during the migration. For example, when collaborators/members are migrated, roles from GitHub are mapped to the appropriate GitLab roles as follows:\n\n| GitHub role | GitLab role |\n| ----------- | ----------- |\n| Read        | Guest       |\n| Triage      | Reporter    |\n| Write       | Developer   |\n| Maintain    | Maintainer  |\n| Admin       | Owner       |\n\n## Prerequisites\n\nNow that you have an understanding of what can be imported, let's review the prerequisites for performing the migration.\n\nWith the GitLab importer, you can either import your projects from\n**GitHub.com** or **GitHub Enterprise** to either **GitLab.com** or\n**Self-managed GitLab** as long as you meet the following requirements:\n\n* You must be a Maintainer on the GitLab destination group you are importing\nto from GitHub\n\n* Each GitHub author and assignee in the repository must have a\npublic-facing email address on GitHub that matches their GitLab email address\n\n* GitHub accounts must have a public-facing email address that is populated\n\n* [GitHub import\nsource](https://docs.gitlab.com/administration/settings/visibility_and_access_controls/#configure-allowed-import-sources)\nmust be enabled (Self-managed GitLab only)\n\nWhen migrating a user, GitLab uses the public-facing email address in GitHub to verify the user with the same email on GitLab. Because email ownership is unique, you'll know you have set a valid user with valid permissions.\n\n## Performing the import\n\nNow let's go over how to perform the migration. I will be migrating my project, the [Reddit sentiment analyzer](https://github.com/fishtoadsoft/reddit-sentiment-analyzer), from\nGitHub to GitLab. The Reddit sentiment analyzer contains a pull request (called a merge request in GitLab), issues, and comments.\n\n**Note:** While you may not have permissions to my project, the step-by-step process applies to any project you own. I am using my project so you can see how I migrate GitHub Actions in the next section. Now, let's get started!\n\n1) Create a new project in GitLab using the [Project Creation\nInterface](https://gitlab.com/projects/new).\n\n2) Select the **Import Project** box. This allows you to migrate data from external sources.\n\n![Import project box](https://about.gitlab.com/images/blogimages/2023-july-github-to-gitlab-migration/import_project.png)\n\n3) Under **Import project from**, press the **GitHub** button. This will take you to the **Authenticate with GitHub** page.\n\n4) Press the **Authenticate with GitHub** button. You can also use a [personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens)\nfrom GitHub with the **repo scope** if you prefer. This will take you to the\nGitHub authorization app.\n\n5) From here, you can grant access to [GitHub organization(s)](https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/about-organizations)\nwhere the projects you wish to migrate are located.\n\n![GitHub authorization app](https://about.gitlab.com/images/blogimages/2023-july-github-to-gitlab-migration/github_authorize_app.png)\n\n6) Press the **Grant** button for the organization where the project you wish to migrate is stored.\n\n7) Press the **Authorize gitlabhq** button to grant GitLab access to the organization(s) selected. You will then be taken to the import selection page.\n\n8) From here, you can select the items you wish to import.\n\n![Import selection](https://about.gitlab.com/images/blogimages/2023-july-github-to-gitlab-migration/import_selection.png)\n\n**Note:** The more items you choose to migrate, the longer the import will take.\n\n9) Then you must set the GitLab location you want to migrate the GitHub project to.\n\n![Set the GitLab location to migrate to](https://about.gitlab.com/images/blogimages/2023-july-github-to-gitlab-migration/import_to.png)\n\n10) Press the **Import** button and the import will begin. You can see the progress in the UI. Once the import is complete the status will be changed to \"complete.\" [Import progress status](https://about.gitlab.com/images/blogimages/2023-july-github-to-gitlab-migration/import_progress.png)\n\nNow you should have the imported project in your workspace. Mine is called [https://gitlab.com/awkwardferny/reddit-sentiment-analyzer](https://gitlab.com/awkwardferny/reddit-sentiment-analyzer).\nWhen examining the imported project, you can see the following:\n\n**Repository has been migrated**\n\n![Repository has been migrated](https://about.gitlab.com/images/blogimages/2023-july-github-to-gitlab-migration/migrated_data.png)\n\n**Issue has been migrated**\n\n![Issue has been migrated](https://about.gitlab.com/images/blogimages/2023-july-github-to-gitlab-migration/migrated_issue.png)\n\n**Merge request has been migrated**\n\n![Merge request has been migrated](https://about.gitlab.com/images/blogimages/2023-july-github-to-gitlab-migration/migrated_merge_request.png)\n\n## Migrating GitHub Actions over to GitLab CI/CD\n\nNow that you have migrated the project over from GitHub, notice that none of the GitHub Actions are running. Don't worry, they are very easy to migrate manually. So let's start the migration process for Actions.\n\n1) Examine the GitHub Actions within the **.github/workflows** folder. In the [project you just imported](https://gitlab.com/awkwardferny/reddit-sentiment-analyzer/-/tree/master/.github/workflows), you should see three different Action files:\n\n#### lint.yml\n\nThis file contains the Action, which performs linting on the source code using flake8. It uses the python:3.10 Docker image and installs the application requirements before performing the lint.\n\n```yaml\nname: \"Lint\"\n\non:\n  push:\n    branches: [ master ]\n  pull_request:\n    branches: [ master ]\n\njobs:\n  lint:\n    runs-on: ubuntu-latest\n    steps:\n    - uses: actions/checkout@v3\n    - name: Set up Python 3.10\n      uses: actions/setup-python@v4\n      with:\n        python-version: \"3.10\"\n    - name: Install dependencies\n      run: |\n        python -m pip install --upgrade pip\n        pip install flake8 pytest\n        if [ -f requirements.txt ]; then pip install -r requirements.txt; fi\n    - name: Lint with flake8\n      run: |\n        # stop the build if there are Python syntax errors or undefined names\n        flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics\n        # exit-zero treats all errors as warnings. The GitHub editor is 127 chars wide\n        flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics\n```\n\n#### smoke.yml\n\nThis file contains the action which performs a smoke test by just running the CLI help menu. It uses the python:3.10 Docker image and installs the application requirements before performing the smoke test.\n\n```yaml\nname: \"Smoke Tests\"\n\non:\n  push:\n    branches: [ master ]\n  pull_request:\n    branches: [ master ]\n\njobs:\n  smoke-tests:\n    runs-on: ubuntu-latest\n    steps:\n    - uses: actions/checkout@v3\n    - name: Set up Python 3.10\n      uses: actions/setup-python@v4\n      with:\n        python-version: \"3.10\"\n    - name: Install dependencies\n      run: |\n        python -m pip install --upgrade pip\n        pip install setuptools\n        if [ -f requirements.txt ]; then pip install -r requirements.txt; fi\n    - name: Install Sentiment Analysis Application\n      run: |\n        python setup.py install\n    - name: Run smoke tests\n      run: |\n        reddit-sentiment --help\n```\n\n#### unit.yml\n\nThis file contains the Action, which performs unit tests using pytest. It uses the python:3.10 Docker image and installs the application requirements running the unit tests.\n\n```yaml\nname: \"Unit Tests\"\n\non:\n  push:\n    branches: [ master ]\n  pull_request:\n    branches: [ master ]\n\njobs:\n  unit-tests:\n    runs-on: ubuntu-latest\n    steps:\n    - uses: actions/checkout@v3\n    - name: Set up Python 3.10\n      uses: actions/setup-python@v4\n      with:\n        python-version: \"3.10\"\n    - name: Install dependencies\n      run: |\n        python -m pip install --upgrade pip\n        pip install pytest\n        if [ -f requirements.txt ]; then pip install -r requirements.txt; fi\n    - name: Test with pytest\n      run: |\n        python -m pip install --upgrade pip\n        if [ -f test-requirements.txt ]; then pip install -r test-requirements.txt; fi\n        pytest tests/\n```\n\nNow let's go ahead and migrate these Actions over to GitLab.\n\n2) Go to the recently imported project on GitLab and open up the [WebIDE](https://docs.gitlab.com/user/project/web_ide/).\n\n3) Create a file at the root called [**.gitlab-ci.yml**](https://docs.gitlab.com/ci/yaml/gitlab_ci_yaml/).\n\nThis file defines the GitLab pipeline.\n\n4) Add the following configuration, which will add the GitHub Actions as\nJobs in the GitLab pipeline. Notice the comments I added describing each section.\n\n```yaml\n# This creates the stages in which the jobs will run. By default all\n# jobs will run in parallel in the stage. Once the jobs are completed\n# successfully then you move on to the next stage. The way jobs run\n# is completely configurable.\nstages:\n  - test\n\n# With the include statement, you can quickly add jobs which have\n# been pre-defined in external YAMLs. The SAST job I included below\n# is provided and maintained by GitLab and adds Static Application\n# Security Testing (SAST) to your pipeline.\ninclude:\n  - template: Jobs/SAST.gitlab-ci.yml\n\n# This is the unit test job which does exactly what is defined in\n# the GitHub Action in unit.yml. You can see it uses the python:3.10\n# Docker image, installs the application dependencies, and then runs\n# the unit tests with pytest. It was added with a simple copy and\n# paste and minor syntax changes.\nunit:\n  image: python:3.10\n  stage: test\n  before_script:\n    - python -m pip install --upgrade pip\n    - pip install pytest\n    - if [ -f requirements.txt ]; then pip install -r requirements.txt; fi\n  script:\n    - pytest tests/\n\n# This is the lint job which does exactly what is defined in the\n# GitHub Action in lint.yml. You can see it uses the python:3.10\n# Docker image, installs the application dependencies, and then\n# performs the linting with flake8. It was added with a simple copy\n# and paste and minor syntax changes.\nlint:\n  image: python:3.10\n  stage: test\n  before_script:\n    - python -m pip install --upgrade pip\n    - pip install flake8\n    - if [ -f requirements.txt ]; then pip install -r requirements.txt; fi\n  script:\n    - flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics\n    - flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics\n\n# This is the smoke test job which does exactly what is defined in\n# the GitHub Action in smoke.yml. You can see it uses the python:3.10\n# Docker image, installs the application dependencies, and then runs\n# the smoke tests with the Reddit sentiment analysis CLI. It was\n# added with a simple copy and paste and minor syntax changes.\nsmoke:\n  image: python:3.10\n  stage: test\n  before_script:\n    - python -m pip install --upgrade pip\n    - pip install setuptools\n    - if [ -f requirements.txt ]; then pip install -r requirements.txt; fi\n    - python setup.py install\n  script:\n    - reddit-sentiment --help\n```\n\nYou can see that scripts being executed in GitLab match those scripts within the GitHub Actions. The only thing that has really changed is the syntax setting up the jobs and stages. To learn more on how to create and configure pipelines, check out the [GitLab CI/CD documentation](https://docs.gitlab.com/ci/).\n\n5) Let's check in the code. From the WebIDE click on the Source Control Tab in the side panel of the WebIDE. It is the [third icon from the top](https://code.visualstudio.com/docs/sourcecontrol/overview#_commit).\nThen press the **Commit to 'main'** button, select **Continue**, and voila, you should now have a running pipeline.\n\n6) Examine the pipeline and make sure the jobs are running properly. Go back to your project and click on the [pipeline](https://docs.gitlab.com/ci/pipelines/) icon. You can see the the four jobs we created have run.\n\n![Four jobs have run](https://about.gitlab.com/images/blogimages/2023-july-github-to-gitlab-migration/gitlab_jobs.png)\n\n7) Click on the **Unit** job and you can see that the unit tests were run successfully.\n\n```bash\n$ pytest tests/\n============================= test session starts\n==============================\nplatform linux -- Python 3.10.11, pytest-7.3.1, pluggy-1.0.0\nrootdir: /builds/awkwardferny/reddit-sentiment-analyzer\ncollected 2 items\ntests/test_scraper.py ..\n[100%]\n============================== 2 passed in 0.09s\n===============================\nCleaning up project directory and file based variables\n00:00\nJob succeeded\n```\n\nAnd that's how simple it is to migrate a project over from GitHub to GitLab!\n\n## What other platforms can GitLab import from?\n\nThe GitLab importer allows one-click migration from several other platforms.\nThese platforms include:\n\n* [Bitbucket\nCloud](https://docs.gitlab.com/user/project/import/bitbucket/)\n\n* [Bitbucket Server\n(Stash)](https://docs.gitlab.com/user/project/import/bitbucket_server/)\n\n* [FogBugz](https://docs.gitlab.com/user/project/import/fogbugz/)\n\n* [Gitea](https://docs.gitlab.com/user/project/import/gitea/)\n\n* [Repository by\nURL](https://docs.gitlab.com/user/project/import/repo_by_url/)\n\n* [Uploading a manifest file\n(AOSP)](https://docs.gitlab.com/user/project/import/manifest/)\n\n* [Jira (issues\nonly)](https://docs.gitlab.com/user/project/import/jira/)\n\nWe also have documentation covering how to migrate from these platforms:\n\n* [SVN](https://docs.gitlab.com/user/project/import/#import-from-subversion)\n\n* [ClearCase](https://docs.gitlab.com/user/project/import/clearcase/)\n\n* [CVS](https://docs.gitlab.com/user/project/import/cvs/)\n\n* [Perforce](https://docs.gitlab.com/user/project/import/perforce/)\n\n* [TFVC](https://docs.gitlab.com/user/project/import/tfvc/)\n\n---\n\nThanks for reading! Now you know how easy it is to migrate from GitHub over to GitLab. For more information on GitLab and migrating from GitHub, follow the links below:\n\n* [GitHub-to-GitLab project migration\ndocumentation](https://docs.gitlab.com/user/project/import/github/)\n\n* [Available project\nimporters](https://docs.gitlab.com/user/project/import/#available-project-importers)\n\n* [GitHub-to-GitLab migration video](https://youtu.be/0Id5oMl1Kqs)\n\nAlso, read how GitLab has been named a leader in the DevOps platforms space by [Gartner](https://about.gitlab.com/blog/gitlab-leader-gartner-magic-quadrant-devops-platforms/)\nand the integrated software delivery platforms space by [Forrester](https://about.gitlab.com/blog/gitlab-leader-forrester-wave-integrated-software-delivery-platforms/).\n\n_Cover image by [Julia\nCraice](https://unsplash.com/@jcraice?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)\non [Unsplash](https://unsplash.com/s/photos/migration?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)_","devsecops",{"slug":13,"featured":14,"template":15},"github-to-gitlab-migration-made-easy",false,"BlogPost",{"title":5,"description":17,"authors":18,"heroImage":19,"date":20,"body":10,"category":11,"tags":21},"Learn how easy it is to migrate from GitHub to GitLab using GitLab's project import functionality.",[9],"https://res.cloudinary.com/about-gitlab-com/image/upload/v1749668776/Blog/Hero%20Images/julia-craice-faCwTallTC0-unsplash.jpg","2023-07-11",[22,23,24,25],"CI/CD","tutorial","DevSecOps","DevSecOps platform","yml",null,{},true,"/en-us/blog/github-to-gitlab-migration-made-easy","seo:\n  ogTitle: GitHub to GitLab migration the easy way\n  ogImage: https://res.cloudinary.com/about-gitlab-com/image/upload/v1749668776/Blog/Hero%20Images/julia-craice-faCwTallTC0-unsplash.jpg\n  ogDescription: Learn how easy it is to migrate from GitHub to GitLab using\n    GitLab's project import functionality.\n  ogSiteName: https://about.gitlab.com\n  noIndex: false\n  ogType: article\n  ogUrl: https://about.gitlab.com/blog/github-to-gitlab-migration-made-easy\n  title: GitHub to GitLab migration the easy way\n  canonicalUrls: https://about.gitlab.com/blog/github-to-gitlab-migration-made-easy\n  description: Learn how easy it is to migrate from GitHub to GitLab using\n    GitLab's project import functionality.\ncontent:\n  title: GitHub to GitLab migration the easy way\n  description: Learn how easy it is to migrate from GitHub to GitLab using\n    GitLab's project import functionality.\n  authors:\n    - Fernando Diaz\n  heroImage: https://res.cloudinary.com/about-gitlab-com/image/upload/v1749668776/Blog/Hero%20Images/julia-craice-faCwTallTC0-unsplash.jpg\n  date: 2023-07-11\n  body: >-\n    If you are using different CI/CD tools and are considering migrating over to\n\n    GitLab, you may be wondering about the difficulty of the migration process.\n    Migration is usually a concern for\n    [DevSecOps](https://about.gitlab.com/topics/devsecops/) teams when\n    considering a new solution. This is due to the fact that migrating may\n    involve heavy lifting. However, migrating to the GitLab AI-powered DevSecOps\n\n    Platform can be extremely simple and I will show you how step by step.\n\n\n    In this blog post, we will go over how to migrate from GitHub to GitLab\n    using our [project import](https://docs.gitlab.com/user/project/import/)\n\n    functionality. Manually migrating GitHub Actions to GitLab pipelines will be\n    covered as well. I have also created a video going over the migration\n    process for those who prefer that format:\n\n\n    \u003C!-- blank line -->\n\n\n    \u003Cfigure class=\"video_container\">\n      \u003Ciframe src=\"https://www.youtube.com/embed/0Id5oMl1Kqs\" frameborder=\"0\" allowfullscreen=\"true\"> \u003C/iframe>\n    \u003C/figure>\n\n\n    \u003C!-- blank line -->\n\n\n    ## What data can be migrated from GitHub to GitLab?\n\n\n    GitLab's built-in importer allows for GitHub projects to be automatically\n    migrated into GitLab. The built-in importer is accessed directly from\n    GitLab's project creation UI. From the UI, you can select what data you wish\n    to migrate to GitLab.\n\n\n    The data that can be migrated includes the following:\n\n\n    * Repository description\n\n\n    * Git repository data\n\n\n    * Branch protection rules\n\n\n    * Collaborators (members)\n\n\n    * Issues\n\n\n    * Pull requests\n\n\n    * Wiki pages\n\n\n    * Milestones\n\n\n    * Labels\n\n\n    * Release notes content\n\n\n    * Release notes attachments\n\n\n    * Comment attachments\n\n\n    * Issue description attachments\n\n\n    * Pull request description attachments\n\n\n    * Pull request review comments\n\n\n    * Regular issue and pull request comments\n\n\n    * Git Large File Storage (LFS) objects\n\n\n    * Pull request reviews\n\n\n    * Pull request assigned reviewers\n\n\n    * Pull request “merged by” information\n\n\n    * Pull request comments replies in discussions\n\n\n    * Pull request review comments suggestions\n\n\n    * Issue events and pull requests events\n\n\n    GitHub and GitLab have different naming conventions and concepts, so a\n    mapping must be performed during the migration. For example, when\n    collaborators/members are migrated, roles from GitHub are mapped to the\n    appropriate GitLab roles as follows:\n\n\n    | GitHub role | GitLab role |\n\n    | ----------- | ----------- |\n\n    | Read        | Guest       |\n\n    | Triage      | Reporter    |\n\n    | Write       | Developer   |\n\n    | Maintain    | Maintainer  |\n\n    | Admin       | Owner       |\n\n\n    ## Prerequisites\n\n\n    Now that you have an understanding of what can be imported, let's review the\n    prerequisites for performing the migration.\n\n\n    With the GitLab importer, you can either import your projects from\n\n    **GitHub.com** or **GitHub Enterprise** to either **GitLab.com** or\n\n    **Self-managed GitLab** as long as you meet the following requirements:\n\n\n    * You must be a Maintainer on the GitLab destination group you are importing\n\n    to from GitHub\n\n\n    * Each GitHub author and assignee in the repository must have a\n\n    public-facing email address on GitHub that matches their GitLab email\n    address\n\n\n    * GitHub accounts must have a public-facing email address that is populated\n\n\n    * [GitHub import\n\n    source](https://docs.gitlab.com/administration/settings/visibility_and_access_controls/#configure-allowed-import-sources)\n\n    must be enabled (Self-managed GitLab only)\n\n\n    When migrating a user, GitLab uses the public-facing email address in GitHub\n    to verify the user with the same email on GitLab. Because email ownership is\n    unique, you'll know you have set a valid user with valid permissions.\n\n\n    ## Performing the import\n\n\n    Now let's go over how to perform the migration. I will be migrating my\n    project, the [Reddit sentiment\n    analyzer](https://github.com/fishtoadsoft/reddit-sentiment-analyzer), from\n\n    GitHub to GitLab. The Reddit sentiment analyzer contains a pull request\n    (called a merge request in GitLab), issues, and comments.\n\n\n    **Note:** While you may not have permissions to my project, the step-by-step\n    process applies to any project you own. I am using my project so you can see\n    how I migrate GitHub Actions in the next section. Now, let's get started!\n\n\n    1) Create a new project in GitLab using the [Project Creation\n\n    Interface](https://gitlab.com/projects/new).\n\n\n    2) Select the **Import Project** box. This allows you to migrate data from\n    external sources.\n\n\n    ![Import project\n    box](https://about.gitlab.com/images/blogimages/2023-july-github-to-gitlab-migration/import_project.png)\n\n\n    3) Under **Import project from**, press the **GitHub** button. This will\n    take you to the **Authenticate with GitHub** page.\n\n\n    4) Press the **Authenticate with GitHub** button. You can also use a\n    [personal access\n    token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens)\n\n    from GitHub with the **repo scope** if you prefer. This will take you to the\n\n    GitHub authorization app.\n\n\n    5) From here, you can grant access to [GitHub\n    organization(s)](https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/about-organizations)\n\n    where the projects you wish to migrate are located.\n\n\n    ![GitHub authorization\n    app](https://about.gitlab.com/images/blogimages/2023-july-github-to-gitlab-migration/github_authorize_app.png)\n\n\n    6) Press the **Grant** button for the organization where the project you\n    wish to migrate is stored.\n\n\n    7) Press the **Authorize gitlabhq** button to grant GitLab access to the\n    organization(s) selected. You will then be taken to the import selection\n    page.\n\n\n    8) From here, you can select the items you wish to import.\n\n\n    ![Import\n    selection](https://about.gitlab.com/images/blogimages/2023-july-github-to-gitlab-migration/import_selection.png)\n\n\n    **Note:** The more items you choose to migrate, the longer the import will\n    take.\n\n\n    9) Then you must set the GitLab location you want to migrate the GitHub\n    project to.\n\n\n    ![Set the GitLab location to migrate\n    to](https://about.gitlab.com/images/blogimages/2023-july-github-to-gitlab-migration/import_to.png)\n\n\n    10) Press the **Import** button and the import will begin. You can see the\n    progress in the UI. Once the import is complete the status will be changed\n    to \"complete.\" [Import progress\n    status](https://about.gitlab.com/images/blogimages/2023-july-github-to-gitlab-migration/import_progress.png)\n\n\n    Now you should have the imported project in your workspace. Mine is called\n    [https://gitlab.com/awkwardferny/reddit-sentiment-analyzer](https://gitlab.com/awkwardferny/reddit-sentiment-analyzer).\n\n    When examining the imported project, you can see the following:\n\n\n    **Repository has been migrated**\n\n\n    ![Repository has been\n    migrated](https://about.gitlab.com/images/blogimages/2023-july-github-to-gitlab-migration/migrated_data.png)\n\n\n    **Issue has been migrated**\n\n\n    ![Issue has been\n    migrated](https://about.gitlab.com/images/blogimages/2023-july-github-to-gitlab-migration/migrated_issue.png)\n\n\n    **Merge request has been migrated**\n\n\n    ![Merge request has been\n    migrated](https://about.gitlab.com/images/blogimages/2023-july-github-to-gitlab-migration/migrated_merge_request.png)\n\n\n    ## Migrating GitHub Actions over to GitLab CI/CD\n\n\n    Now that you have migrated the project over from GitHub, notice that none of\n    the GitHub Actions are running. Don't worry, they are very easy to migrate\n    manually. So let's start the migration process for Actions.\n\n\n    1) Examine the GitHub Actions within the **.github/workflows** folder. In\n    the [project you just\n    imported](https://gitlab.com/awkwardferny/reddit-sentiment-analyzer/-/tree/master/.github/workflows),\n    you should see three different Action files:\n\n\n    #### lint.yml\n\n\n    This file contains the Action, which performs linting on the source code\n    using flake8. It uses the python:3.10 Docker image and installs the\n    application requirements before performing the lint.\n\n\n    ```yaml\n\n    name: \"Lint\"\n\n\n    on:\n      push:\n        branches: [ master ]\n      pull_request:\n        branches: [ master ]\n\n    jobs:\n      lint:\n        runs-on: ubuntu-latest\n        steps:\n        - uses: actions/checkout@v3\n        - name: Set up Python 3.10\n          uses: actions/setup-python@v4\n          with:\n            python-version: \"3.10\"\n        - name: Install dependencies\n          run: |\n            python -m pip install --upgrade pip\n            pip install flake8 pytest\n            if [ -f requirements.txt ]; then pip install -r requirements.txt; fi\n        - name: Lint with flake8\n          run: |\n            # stop the build if there are Python syntax errors or undefined names\n            flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics\n            # exit-zero treats all errors as warnings. The GitHub editor is 127 chars wide\n            flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics\n    ```\n\n\n    #### smoke.yml\n\n\n    This file contains the action which performs a smoke test by just running\n    the CLI help menu. It uses the python:3.10 Docker image and installs the\n    application requirements before performing the smoke test.\n\n\n    ```yaml\n\n    name: \"Smoke Tests\"\n\n\n    on:\n      push:\n        branches: [ master ]\n      pull_request:\n        branches: [ master ]\n\n    jobs:\n      smoke-tests:\n        runs-on: ubuntu-latest\n        steps:\n        - uses: actions/checkout@v3\n        - name: Set up Python 3.10\n          uses: actions/setup-python@v4\n          with:\n            python-version: \"3.10\"\n        - name: Install dependencies\n          run: |\n            python -m pip install --upgrade pip\n            pip install setuptools\n            if [ -f requirements.txt ]; then pip install -r requirements.txt; fi\n        - name: Install Sentiment Analysis Application\n          run: |\n            python setup.py install\n        - name: Run smoke tests\n          run: |\n            reddit-sentiment --help\n    ```\n\n\n    #### unit.yml\n\n\n    This file contains the Action, which performs unit tests using pytest. It\n    uses the python:3.10 Docker image and installs the application requirements\n    running the unit tests.\n\n\n    ```yaml\n\n    name: \"Unit Tests\"\n\n\n    on:\n      push:\n        branches: [ master ]\n      pull_request:\n        branches: [ master ]\n\n    jobs:\n      unit-tests:\n        runs-on: ubuntu-latest\n        steps:\n        - uses: actions/checkout@v3\n        - name: Set up Python 3.10\n          uses: actions/setup-python@v4\n          with:\n            python-version: \"3.10\"\n        - name: Install dependencies\n          run: |\n            python -m pip install --upgrade pip\n            pip install pytest\n            if [ -f requirements.txt ]; then pip install -r requirements.txt; fi\n        - name: Test with pytest\n          run: |\n            python -m pip install --upgrade pip\n            if [ -f test-requirements.txt ]; then pip install -r test-requirements.txt; fi\n            pytest tests/\n    ```\n\n\n    Now let's go ahead and migrate these Actions over to GitLab.\n\n\n    2) Go to the recently imported project on GitLab and open up the\n    [WebIDE](https://docs.gitlab.com/user/project/web_ide/).\n\n\n    3) Create a file at the root called\n    [**.gitlab-ci.yml**](https://docs.gitlab.com/ci/yaml/gitlab_ci_yaml/).\n\n\n    This file defines the GitLab pipeline.\n\n\n    4) Add the following configuration, which will add the GitHub Actions as\n\n    Jobs in the GitLab pipeline. Notice the comments I added describing each\n    section.\n\n\n    ```yaml\n\n    # This creates the stages in which the jobs will run. By default all\n\n    # jobs will run in parallel in the stage. Once the jobs are completed\n\n    # successfully then you move on to the next stage. The way jobs run\n\n    # is completely configurable.\n\n    stages:\n      - test\n\n    # With the include statement, you can quickly add jobs which have\n\n    # been pre-defined in external YAMLs. The SAST job I included below\n\n    # is provided and maintained by GitLab and adds Static Application\n\n    # Security Testing (SAST) to your pipeline.\n\n    include:\n      - template: Jobs/SAST.gitlab-ci.yml\n\n    # This is the unit test job which does exactly what is defined in\n\n    # the GitHub Action in unit.yml. You can see it uses the python:3.10\n\n    # Docker image, installs the application dependencies, and then runs\n\n    # the unit tests with pytest. It was added with a simple copy and\n\n    # paste and minor syntax changes.\n\n    unit:\n      image: python:3.10\n      stage: test\n      before_script:\n        - python -m pip install --upgrade pip\n        - pip install pytest\n        - if [ -f requirements.txt ]; then pip install -r requirements.txt; fi\n      script:\n        - pytest tests/\n\n    # This is the lint job which does exactly what is defined in the\n\n    # GitHub Action in lint.yml. You can see it uses the python:3.10\n\n    # Docker image, installs the application dependencies, and then\n\n    # performs the linting with flake8. It was added with a simple copy\n\n    # and paste and minor syntax changes.\n\n    lint:\n      image: python:3.10\n      stage: test\n      before_script:\n        - python -m pip install --upgrade pip\n        - pip install flake8\n        - if [ -f requirements.txt ]; then pip install -r requirements.txt; fi\n      script:\n        - flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics\n        - flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics\n\n    # This is the smoke test job which does exactly what is defined in\n\n    # the GitHub Action in smoke.yml. You can see it uses the python:3.10\n\n    # Docker image, installs the application dependencies, and then runs\n\n    # the smoke tests with the Reddit sentiment analysis CLI. It was\n\n    # added with a simple copy and paste and minor syntax changes.\n\n    smoke:\n      image: python:3.10\n      stage: test\n      before_script:\n        - python -m pip install --upgrade pip\n        - pip install setuptools\n        - if [ -f requirements.txt ]; then pip install -r requirements.txt; fi\n        - python setup.py install\n      script:\n        - reddit-sentiment --help\n    ```\n\n\n    You can see that scripts being executed in GitLab match those scripts within\n    the GitHub Actions. The only thing that has really changed is the syntax\n    setting up the jobs and stages. To learn more on how to create and configure\n    pipelines, check out the [GitLab CI/CD\n    documentation](https://docs.gitlab.com/ci/).\n\n\n    5) Let's check in the code. From the WebIDE click on the Source Control Tab\n    in the side panel of the WebIDE. It is the [third icon from the\n    top](https://code.visualstudio.com/docs/sourcecontrol/overview#_commit).\n\n    Then press the **Commit to 'main'** button, select **Continue**, and voila,\n    you should now have a running pipeline.\n\n\n    6) Examine the pipeline and make sure the jobs are running properly. Go back\n    to your project and click on the\n    [pipeline](https://docs.gitlab.com/ci/pipelines/) icon. You can see the\n    the four jobs we created have run.\n\n\n    ![Four jobs have\n    run](https://about.gitlab.com/images/blogimages/2023-july-github-to-gitlab-migration/gitlab_jobs.png)\n\n\n    7) Click on the **Unit** job and you can see that the unit tests were run\n    successfully.\n\n\n    ```bash\n\n    $ pytest tests/\n\n    ============================= test session starts\n\n    ==============================\n\n    platform linux -- Python 3.10.11, pytest-7.3.1, pluggy-1.0.0\n\n    rootdir: /builds/awkwardferny/reddit-sentiment-analyzer\n\n    collected 2 items\n\n    tests/test_scraper.py ..\n\n    [100%]\n\n    ============================== 2 passed in 0.09s\n\n    ===============================\n\n    Cleaning up project directory and file based variables\n\n    00:00\n\n    Job succeeded\n\n    ```\n\n\n    And that's how simple it is to migrate a project over from GitHub to GitLab!\n\n\n    ## What other platforms can GitLab import from?\n\n\n    The GitLab importer allows one-click migration from several other platforms.\n\n    These platforms include:\n\n\n    * [Bitbucket\n\n    Cloud](https://docs.gitlab.com/user/project/import/bitbucket/)\n\n\n    * [Bitbucket Server\n\n    (Stash)](https://docs.gitlab.com/user/project/import/bitbucket_server/)\n\n\n    * [FogBugz](https://docs.gitlab.com/user/project/import/fogbugz/)\n\n\n    * [Gitea](https://docs.gitlab.com/user/project/import/gitea/)\n\n\n    * [Repository by\n\n    URL](https://docs.gitlab.com/user/project/import/repo_by_url/)\n\n\n    * [Uploading a manifest file\n\n    (AOSP)](https://docs.gitlab.com/user/project/import/manifest/)\n\n\n    * [Jira (issues\n\n    only)](https://docs.gitlab.com/user/project/import/jira/)\n\n\n    We also have documentation covering how to migrate from these platforms:\n\n\n    *\n    [SVN](https://docs.gitlab.com/user/project/import/#import-from-subversion)\n\n\n    * [ClearCase](https://docs.gitlab.com/user/project/import/clearcase/)\n\n\n    * [CVS](https://docs.gitlab.com/user/project/import/cvs/)\n\n\n    * [Perforce](https://docs.gitlab.com/user/project/import/perforce/)\n\n\n    * [TFVC](https://docs.gitlab.com/user/project/import/tfvc/)\n\n\n    ---\n\n\n    Thanks for reading! Now you know how easy it is to migrate from GitHub over\n    to GitLab. For more information on GitLab and migrating from GitHub, follow\n    the links below:\n\n\n    * [GitHub-to-GitLab project migration\n\n    documentation](https://docs.gitlab.com/user/project/import/github/)\n\n\n    * [Available project\n\n    importers](https://docs.gitlab.com/user/project/import/#available-project-importers)\n\n\n    * [GitHub-to-GitLab migration video](https://youtu.be/0Id5oMl1Kqs)\n\n\n    Also, read how GitLab has been named a leader in the DevOps platforms space\n    by\n    [Gartner](https://about.gitlab.com/blog/gitlab-leader-gartner-magic-quadrant-devops-platforms/)\n\n    and the integrated software delivery platforms space by\n    [Forrester](https://about.gitlab.com/blog/gitlab-leader-forrester-wave-integrated-software-delivery-platforms/).\n\n\n    _Cover image by [Julia\n\n    Craice](https://unsplash.com/@jcraice?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)\n\n    on\n    [Unsplash](https://unsplash.com/s/photos/migration?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)_\n  category: devsecops\n  tags:\n    - CI/CD\n    - tutorial\n    - DevSecOps\n    - DevSecOps platform\nconfig:\n  slug: github-to-gitlab-migration-made-easy\n  featured: false\n  template: BlogPost\n",{"ogTitle":5,"ogImage":19,"ogDescription":17,"ogSiteName":33,"noIndex":14,"ogType":34,"ogUrl":35,"title":5,"canonicalUrls":35,"description":17},"https://about.gitlab.com","article","https://about.gitlab.com/blog/github-to-gitlab-migration-made-easy","en-us/blog/github-to-gitlab-migration-made-easy",[38,23,11,39],"cicd","devsecops-platform",[22,23,24,25],"DHtPzZRNclikPXzSTQSBjHMBd7vGcIvxn02oIy2Zs3A",{"data":43},{"logo":44,"freeTrial":49,"sales":54,"login":59,"items":64,"search":372,"minimal":403,"duo":422,"switchNav":431,"pricingDeployment":442},{"config":45},{"href":46,"dataGaName":47,"dataGaLocation":48},"/","gitlab logo","header",{"text":50,"config":51},"Get free trial",{"href":52,"dataGaName":53,"dataGaLocation":48},"https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com&glm_content=default-saas-trial/","free trial",{"text":55,"config":56},"Talk to sales",{"href":57,"dataGaName":58,"dataGaLocation":48},"/sales/","sales",{"text":60,"config":61},"Sign in",{"href":62,"dataGaName":63,"dataGaLocation":48},"https://gitlab.com/users/sign_in/","sign in",[65,92,186,191,293,353],{"text":66,"config":67,"cards":69},"Platform",{"dataNavLevelOne":68},"platform",[70,76,84],{"title":66,"description":71,"link":72},"The intelligent orchestration platform for DevSecOps",{"text":73,"config":74},"Explore our Platform",{"href":75,"dataGaName":68,"dataGaLocation":48},"/platform/",{"title":77,"description":78,"link":79},"GitLab Duo Agent Platform","Agentic AI for the entire software lifecycle",{"text":80,"config":81},"Meet GitLab Duo",{"href":82,"dataGaName":83,"dataGaLocation":48},"/gitlab-duo-agent-platform/","gitlab duo agent platform",{"title":85,"description":86,"link":87},"Why GitLab","See the top reasons enterprises choose GitLab",{"text":88,"config":89},"Learn more",{"href":90,"dataGaName":91,"dataGaLocation":48},"/why-gitlab/","why gitlab",{"text":93,"left":29,"config":94,"link":96,"lists":100,"footer":168},"Product",{"dataNavLevelOne":95},"solutions",{"text":97,"config":98},"View all Solutions",{"href":99,"dataGaName":95,"dataGaLocation":48},"/solutions/",[101,124,147],{"title":102,"description":103,"link":104,"items":109},"Automation","CI/CD and automation to accelerate deployment",{"config":105},{"icon":106,"href":107,"dataGaName":108,"dataGaLocation":48},"AutomatedCodeAlt","/solutions/delivery-automation/","automated software delivery",[110,113,116,120],{"text":22,"config":111},{"href":112,"dataGaLocation":48,"dataGaName":22},"/solutions/continuous-integration/",{"text":77,"config":114},{"href":82,"dataGaLocation":48,"dataGaName":115},"gitlab duo agent platform - product menu",{"text":117,"config":118},"Source Code Management",{"href":119,"dataGaLocation":48,"dataGaName":117},"/solutions/source-code-management/",{"text":121,"config":122},"Automated Software Delivery",{"href":107,"dataGaLocation":48,"dataGaName":123},"Automated software delivery",{"title":125,"description":126,"link":127,"items":132},"Security","Deliver code faster without compromising security",{"config":128},{"href":129,"dataGaName":130,"dataGaLocation":48,"icon":131},"/solutions/application-security-testing/","security and compliance","ShieldCheckLight",[133,137,142],{"text":134,"config":135},"Application Security Testing",{"href":129,"dataGaName":136,"dataGaLocation":48},"Application security testing",{"text":138,"config":139},"Software Supply Chain Security",{"href":140,"dataGaLocation":48,"dataGaName":141},"/solutions/supply-chain/","Software supply chain security",{"text":143,"config":144},"Software Compliance",{"href":145,"dataGaName":146,"dataGaLocation":48},"/solutions/software-compliance/","software compliance",{"title":148,"link":149,"items":154},"Measurement",{"config":150},{"icon":151,"href":152,"dataGaName":153,"dataGaLocation":48},"DigitalTransformation","/solutions/visibility-measurement/","visibility and measurement",[155,159,163],{"text":156,"config":157},"Visibility & Measurement",{"href":152,"dataGaLocation":48,"dataGaName":158},"Visibility and Measurement",{"text":160,"config":161},"Value Stream Management",{"href":162,"dataGaLocation":48,"dataGaName":160},"/solutions/value-stream-management/",{"text":164,"config":165},"Analytics & Insights",{"href":166,"dataGaLocation":48,"dataGaName":167},"/solutions/analytics-and-insights/","Analytics and insights",{"title":169,"items":170},"GitLab for",[171,176,181],{"text":172,"config":173},"Enterprise",{"href":174,"dataGaLocation":48,"dataGaName":175},"/enterprise/","enterprise",{"text":177,"config":178},"Small Business",{"href":179,"dataGaLocation":48,"dataGaName":180},"/small-business/","small business",{"text":182,"config":183},"Public Sector",{"href":184,"dataGaLocation":48,"dataGaName":185},"/solutions/public-sector/","public sector",{"text":187,"config":188},"Pricing",{"href":189,"dataGaName":190,"dataGaLocation":48,"dataNavLevelOne":190},"/pricing/","pricing",{"text":192,"config":193,"link":195,"lists":199,"feature":284},"Resources",{"dataNavLevelOne":194},"resources",{"text":196,"config":197},"View all resources",{"href":198,"dataGaName":194,"dataGaLocation":48},"/resources/",[200,233,256],{"title":201,"items":202},"Getting started",[203,208,213,218,223,228],{"text":204,"config":205},"Install",{"href":206,"dataGaName":207,"dataGaLocation":48},"/install/","install",{"text":209,"config":210},"Quick start guides",{"href":211,"dataGaName":212,"dataGaLocation":48},"/get-started/","quick setup checklists",{"text":214,"config":215},"Learn",{"href":216,"dataGaLocation":48,"dataGaName":217},"https://university.gitlab.com/","learn",{"text":219,"config":220},"Product documentation",{"href":221,"dataGaName":222,"dataGaLocation":48},"https://docs.gitlab.com/","product documentation",{"text":224,"config":225},"Best practice videos",{"href":226,"dataGaName":227,"dataGaLocation":48},"/getting-started-videos/","best practice videos",{"text":229,"config":230},"Integrations",{"href":231,"dataGaName":232,"dataGaLocation":48},"/integrations/","integrations",{"title":234,"items":235},"Discover",[236,241,246,251],{"text":237,"config":238},"Customer success stories",{"href":239,"dataGaName":240,"dataGaLocation":48},"/customers/","customer success stories",{"text":242,"config":243},"Blog",{"href":244,"dataGaName":245,"dataGaLocation":48},"/blog/","blog",{"text":247,"config":248},"The Source",{"href":249,"dataGaName":250,"dataGaLocation":48},"/the-source/","the source",{"text":252,"config":253},"Remote",{"href":254,"dataGaName":255,"dataGaLocation":48},"https://handbook.gitlab.com/handbook/company/culture/all-remote/","remote",{"title":257,"items":258},"Connect",[259,264,269,274,279],{"text":260,"config":261},"GitLab Services",{"href":262,"dataGaName":263,"dataGaLocation":48},"/services/","services",{"text":265,"config":266},"Community",{"href":267,"dataGaName":268,"dataGaLocation":48},"/community/","community",{"text":270,"config":271},"Forum",{"href":272,"dataGaName":273,"dataGaLocation":48},"https://forum.gitlab.com/","forum",{"text":275,"config":276},"Events",{"href":277,"dataGaName":278,"dataGaLocation":48},"/events/","events",{"text":280,"config":281},"Partners",{"href":282,"dataGaName":283,"dataGaLocation":48},"/partners/","partners",{"textColor":285,"title":286,"text":287,"link":288},"#000","What’s new in GitLab","Stay updated with our latest features and improvements.",{"text":289,"config":290},"Read the latest",{"href":291,"dataGaName":292,"dataGaLocation":48},"/releases/whats-new/","whats new",{"text":294,"config":295,"lists":297},"Company",{"dataNavLevelOne":296},"company",[298],{"items":299},[300,305,311,313,318,323,328,333,338,343,348],{"text":301,"config":302},"About",{"href":303,"dataGaName":304,"dataGaLocation":48},"/company/","about",{"text":306,"config":307,"footerGa":310},"Jobs",{"href":308,"dataGaName":309,"dataGaLocation":48},"/jobs/","jobs",{"dataGaName":309},{"text":275,"config":312},{"href":277,"dataGaName":278,"dataGaLocation":48},{"text":314,"config":315},"Leadership",{"href":316,"dataGaName":317,"dataGaLocation":48},"/company/team/e-group/","leadership",{"text":319,"config":320},"Team",{"href":321,"dataGaName":322,"dataGaLocation":48},"/company/team/","team",{"text":324,"config":325},"Handbook",{"href":326,"dataGaName":327,"dataGaLocation":48},"https://handbook.gitlab.com/","handbook",{"text":329,"config":330},"Investor relations",{"href":331,"dataGaName":332,"dataGaLocation":48},"https://ir.gitlab.com/","investor relations",{"text":334,"config":335},"Trust Center",{"href":336,"dataGaName":337,"dataGaLocation":48},"/security/","trust center",{"text":339,"config":340},"AI Transparency Center",{"href":341,"dataGaName":342,"dataGaLocation":48},"/ai-transparency-center/","ai transparency center",{"text":344,"config":345},"Newsletter",{"href":346,"dataGaName":347,"dataGaLocation":48},"/company/contact/#contact-forms","newsletter",{"text":349,"config":350},"Press",{"href":351,"dataGaName":352,"dataGaLocation":48},"/press/","press",{"text":354,"config":355,"lists":356},"Contact us",{"dataNavLevelOne":296},[357],{"items":358},[359,362,367],{"text":55,"config":360},{"href":57,"dataGaName":361,"dataGaLocation":48},"talk to sales",{"text":363,"config":364},"Support portal",{"href":365,"dataGaName":366,"dataGaLocation":48},"https://support.gitlab.com","support portal",{"text":368,"config":369},"Customer portal",{"href":370,"dataGaName":371,"dataGaLocation":48},"https://customers.gitlab.com/customers/sign_in/","customer portal",{"close":373,"login":374,"suggestions":381},"Close",{"text":375,"link":376},"To search repositories and projects, login to",{"text":377,"config":378},"gitlab.com",{"href":62,"dataGaName":379,"dataGaLocation":380},"search login","search",{"text":382,"default":383},"Suggestions",[384,386,390,392,396,400],{"text":77,"config":385},{"href":82,"dataGaName":77,"dataGaLocation":380},{"text":387,"config":388},"Code Suggestions (AI)",{"href":389,"dataGaName":387,"dataGaLocation":380},"/solutions/code-suggestions/",{"text":22,"config":391},{"href":112,"dataGaName":22,"dataGaLocation":380},{"text":393,"config":394},"GitLab on AWS",{"href":395,"dataGaName":393,"dataGaLocation":380},"/partners/technology-partners/aws/",{"text":397,"config":398},"GitLab on Google Cloud",{"href":399,"dataGaName":397,"dataGaLocation":380},"/partners/technology-partners/google-cloud-platform/",{"text":401,"config":402},"Why GitLab?",{"href":90,"dataGaName":401,"dataGaLocation":380},{"freeTrial":404,"mobileIcon":409,"desktopIcon":414,"secondaryButton":417},{"text":405,"config":406},"Start free trial",{"href":407,"dataGaName":53,"dataGaLocation":408},"https://gitlab.com/-/trials/new/","nav",{"altText":410,"config":411},"Gitlab Icon",{"src":412,"dataGaName":413,"dataGaLocation":408},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203874/jypbw1jx72aexsoohd7x.svg","gitlab icon",{"altText":410,"config":415},{"src":416,"dataGaName":413,"dataGaLocation":408},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203875/gs4c8p8opsgvflgkswz9.svg",{"text":418,"config":419},"Get Started",{"href":420,"dataGaName":421,"dataGaLocation":408},"https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com/get-started/","get started",{"freeTrial":423,"mobileIcon":427,"desktopIcon":429},{"text":424,"config":425},"Learn more about GitLab Duo",{"href":82,"dataGaName":426,"dataGaLocation":408},"gitlab duo",{"altText":410,"config":428},{"src":412,"dataGaName":413,"dataGaLocation":408},{"altText":410,"config":430},{"src":416,"dataGaName":413,"dataGaLocation":408},{"button":432,"mobileIcon":437,"desktopIcon":439},{"text":433,"config":434},"/switch",{"href":435,"dataGaName":436,"dataGaLocation":408},"#contact","switch",{"altText":410,"config":438},{"src":412,"dataGaName":413,"dataGaLocation":408},{"altText":410,"config":440},{"src":441,"dataGaName":413,"dataGaLocation":408},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1773335277/ohhpiuoxoldryzrnhfrh.png",{"freeTrial":443,"mobileIcon":448,"desktopIcon":450},{"text":444,"config":445},"Back to pricing",{"href":189,"dataGaName":446,"dataGaLocation":408,"icon":447},"back to pricing","GoBack",{"altText":410,"config":449},{"src":412,"dataGaName":413,"dataGaLocation":408},{"altText":410,"config":451},{"src":416,"dataGaName":413,"dataGaLocation":408},{"title":453,"button":454,"config":459},"See how agentic AI transforms software delivery",{"text":455,"config":456},"Watch GitLab Transcend now",{"href":457,"dataGaName":458,"dataGaLocation":48},"/events/transcend/virtual/","transcend event",{"layout":460,"icon":461,"disabled":29},"release","AiStar",{"data":463},{"text":464,"source":465,"edit":471,"contribute":476,"config":481,"items":486,"minimal":689},"Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license",{"text":466,"config":467},"View page source",{"href":468,"dataGaName":469,"dataGaLocation":470},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/","page source","footer",{"text":472,"config":473},"Edit this page",{"href":474,"dataGaName":475,"dataGaLocation":470},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/content/","web ide",{"text":477,"config":478},"Please contribute",{"href":479,"dataGaName":480,"dataGaLocation":470},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/CONTRIBUTING.md/","please contribute",{"twitter":482,"facebook":483,"youtube":484,"linkedin":485},"https://twitter.com/gitlab","https://www.facebook.com/gitlab","https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg","https://www.linkedin.com/company/gitlab-com",[487,534,584,628,655],{"title":187,"links":488,"subMenu":503},[489,493,498],{"text":490,"config":491},"View plans",{"href":189,"dataGaName":492,"dataGaLocation":470},"view plans",{"text":494,"config":495},"Why Premium?",{"href":496,"dataGaName":497,"dataGaLocation":470},"/pricing/premium/","why premium",{"text":499,"config":500},"Why Ultimate?",{"href":501,"dataGaName":502,"dataGaLocation":470},"/pricing/ultimate/","why ultimate",[504],{"title":505,"links":506},"Contact Us",[507,510,512,514,519,524,529],{"text":508,"config":509},"Contact sales",{"href":57,"dataGaName":58,"dataGaLocation":470},{"text":363,"config":511},{"href":365,"dataGaName":366,"dataGaLocation":470},{"text":368,"config":513},{"href":370,"dataGaName":371,"dataGaLocation":470},{"text":515,"config":516},"Status",{"href":517,"dataGaName":518,"dataGaLocation":470},"https://status.gitlab.com/","status",{"text":520,"config":521},"Terms of use",{"href":522,"dataGaName":523,"dataGaLocation":470},"/terms/","terms of use",{"text":525,"config":526},"Privacy statement",{"href":527,"dataGaName":528,"dataGaLocation":470},"/privacy/","privacy statement",{"text":530,"config":531},"Cookie preferences",{"dataGaName":532,"dataGaLocation":470,"id":533,"isOneTrustButton":29},"cookie preferences","ot-sdk-btn",{"title":93,"links":535,"subMenu":543},[536,539],{"text":25,"config":537},{"href":75,"dataGaName":538,"dataGaLocation":470},"devsecops platform",{"text":540,"config":541},"AI-Assisted Development",{"href":82,"dataGaName":542,"dataGaLocation":470},"ai-assisted development",[544],{"title":545,"links":546},"Topics",[547,551,556,561,566,569,574,579],{"text":548,"config":549},"CICD",{"href":550,"dataGaName":38,"dataGaLocation":470},"/topics/ci-cd/",{"text":552,"config":553},"GitOps",{"href":554,"dataGaName":555,"dataGaLocation":470},"/topics/gitops/","gitops",{"text":557,"config":558},"DevOps",{"href":559,"dataGaName":560,"dataGaLocation":470},"/topics/devops/","devops",{"text":562,"config":563},"Version Control",{"href":564,"dataGaName":565,"dataGaLocation":470},"/topics/version-control/","version control",{"text":24,"config":567},{"href":568,"dataGaName":11,"dataGaLocation":470},"/topics/devsecops/",{"text":570,"config":571},"Cloud Native",{"href":572,"dataGaName":573,"dataGaLocation":470},"/topics/cloud-native/","cloud native",{"text":575,"config":576},"AI for Coding",{"href":577,"dataGaName":578,"dataGaLocation":470},"/topics/devops/ai-for-coding/","ai for coding",{"text":580,"config":581},"Agentic AI",{"href":582,"dataGaName":583,"dataGaLocation":470},"/topics/agentic-ai/","agentic ai",{"title":585,"links":586},"Solutions",[587,589,591,596,600,603,607,610,612,615,618,623],{"text":134,"config":588},{"href":129,"dataGaName":134,"dataGaLocation":470},{"text":123,"config":590},{"href":107,"dataGaName":108,"dataGaLocation":470},{"text":592,"config":593},"Agile development",{"href":594,"dataGaName":595,"dataGaLocation":470},"/solutions/agile-delivery/","agile delivery",{"text":597,"config":598},"SCM",{"href":119,"dataGaName":599,"dataGaLocation":470},"source code management",{"text":548,"config":601},{"href":112,"dataGaName":602,"dataGaLocation":470},"continuous integration & delivery",{"text":604,"config":605},"Value stream management",{"href":162,"dataGaName":606,"dataGaLocation":470},"value stream management",{"text":552,"config":608},{"href":609,"dataGaName":555,"dataGaLocation":470},"/solutions/gitops/",{"text":172,"config":611},{"href":174,"dataGaName":175,"dataGaLocation":470},{"text":613,"config":614},"Small business",{"href":179,"dataGaName":180,"dataGaLocation":470},{"text":616,"config":617},"Public sector",{"href":184,"dataGaName":185,"dataGaLocation":470},{"text":619,"config":620},"Education",{"href":621,"dataGaName":622,"dataGaLocation":470},"/solutions/education/","education",{"text":624,"config":625},"Financial services",{"href":626,"dataGaName":627,"dataGaLocation":470},"/solutions/finance/","financial services",{"title":192,"links":629},[630,632,634,636,639,641,643,645,647,649,651,653],{"text":204,"config":631},{"href":206,"dataGaName":207,"dataGaLocation":470},{"text":209,"config":633},{"href":211,"dataGaName":212,"dataGaLocation":470},{"text":214,"config":635},{"href":216,"dataGaName":217,"dataGaLocation":470},{"text":219,"config":637},{"href":221,"dataGaName":638,"dataGaLocation":470},"docs",{"text":242,"config":640},{"href":244,"dataGaName":245,"dataGaLocation":470},{"text":237,"config":642},{"href":239,"dataGaName":240,"dataGaLocation":470},{"text":252,"config":644},{"href":254,"dataGaName":255,"dataGaLocation":470},{"text":260,"config":646},{"href":262,"dataGaName":263,"dataGaLocation":470},{"text":265,"config":648},{"href":267,"dataGaName":268,"dataGaLocation":470},{"text":270,"config":650},{"href":272,"dataGaName":273,"dataGaLocation":470},{"text":275,"config":652},{"href":277,"dataGaName":278,"dataGaLocation":470},{"text":280,"config":654},{"href":282,"dataGaName":283,"dataGaLocation":470},{"title":294,"links":656},[657,659,661,663,665,667,669,673,678,680,682,684],{"text":301,"config":658},{"href":303,"dataGaName":296,"dataGaLocation":470},{"text":306,"config":660},{"href":308,"dataGaName":309,"dataGaLocation":470},{"text":314,"config":662},{"href":316,"dataGaName":317,"dataGaLocation":470},{"text":319,"config":664},{"href":321,"dataGaName":322,"dataGaLocation":470},{"text":324,"config":666},{"href":326,"dataGaName":327,"dataGaLocation":470},{"text":329,"config":668},{"href":331,"dataGaName":332,"dataGaLocation":470},{"text":670,"config":671},"Sustainability",{"href":672,"dataGaName":670,"dataGaLocation":470},"/sustainability/",{"text":674,"config":675},"Diversity, inclusion and belonging (DIB)",{"href":676,"dataGaName":677,"dataGaLocation":470},"/diversity-inclusion-belonging/","Diversity, inclusion and belonging",{"text":334,"config":679},{"href":336,"dataGaName":337,"dataGaLocation":470},{"text":344,"config":681},{"href":346,"dataGaName":347,"dataGaLocation":470},{"text":349,"config":683},{"href":351,"dataGaName":352,"dataGaLocation":470},{"text":685,"config":686},"Modern Slavery Transparency Statement",{"href":687,"dataGaName":688,"dataGaLocation":470},"https://handbook.gitlab.com/handbook/legal/modern-slavery-act-transparency-statement/","modern slavery transparency statement",{"items":690},[691,694,697],{"text":692,"config":693},"Terms",{"href":522,"dataGaName":523,"dataGaLocation":470},{"text":695,"config":696},"Cookies",{"dataGaName":532,"dataGaLocation":470,"id":533,"isOneTrustButton":29},{"text":698,"config":699},"Privacy",{"href":527,"dataGaName":528,"dataGaLocation":470},[701],{"id":702,"title":9,"body":27,"config":703,"content":705,"description":27,"extension":26,"meta":709,"navigation":29,"path":710,"seo":711,"stem":712,"__hash__":713},"blogAuthors/en-us/blog/authors/fernando-diaz.yml",{"template":704},"BlogAuthor",{"name":9,"config":706},{"headshot":707,"ctfId":708},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1749659556/Blog/Author%20Headshots/fern_diaz.png","fjdiaz",{},"/en-us/blog/authors/fernando-diaz",{},"en-us/blog/authors/fernando-diaz","lxRJIOydP4_yzYZvsPcuQevP9AYAKREF7i8QmmdnOWc",[715,728,743],{"content":716,"config":726},{"title":717,"description":718,"authors":719,"heroImage":721,"date":722,"body":723,"category":11,"tags":724},"Teaching software development the easy way using GitLab","Learn how University of Washington lecturer Stephen G. Dame uses GitLab for Education to manage student assignments, distribute course materials, and provide inline code feedback at scale.\n",[720],"Rod Burns","https://res.cloudinary.com/about-gitlab-com/image/upload/v1749659537/Blog/Hero%20Images/display-article-image-0679-1800x945-fy26.png","2026-04-29","For instructors teaching software development, one of the biggest logistical challenges is assignment distribution and feedback at scale. How do you give large groups of students access to course materials, keep solution code private, and still deliver meaningful, contextual feedback without lots of administrative overhead?\n\nThe **[GitLab for Education program](https://about.gitlab.com/solutions/education/)** provides qualifying institutions with free access to **GitLab Ultimate**, enabling instructors to build professional-grade workflows that mirror real-world software development environments. In this article, you'll learn how Stephen G. Dame, a lecturer in the Computing and Software Systems department at the University of Washington, Bothell, uses simple workflows in GitLab to manage everything from course materials to student feedback across multiple classes.\n\n## From aerospace to academia: Bringing GitLab to the classroom\n\nDame came to academia with years of experience as a chief software engineer at Boeing Commercial Airplanes, where GitLab was used for aerospace projects. As an adjunct professor, he became an early advocate for GitLab within the university, joining the GitLab for Education program to access the full feature set needed to run structured, scalable course workflows.\n\n> **\"GitLab provides the greatest way to organize multiple classes, student assignments, lectures, and code samples through the use of Groups and Subgroups, which I found to be unique to GitLab compared to other repository platforms.\"**\n>\n> - Stephen G. Dame, University of Washington, Bothell\n\n## Set up groups: Build the right structure before writing a line of code\n\nThe foundation of an effective GitLab-based course is a well-planned group hierarchy. GitLab's **[Groups and Subgroups](https://docs.gitlab.com/tutorials/manage_user/#create-the-organization-parent-group-and-subgroups)** allow instructors to model the natural structure of a university department institution, course, and role with precise, inheritable permissions at every level.\n\nDame's structure places the university at the root (`UWTeaching`), with each course occupying its own subgroup (e.g. `css430`). Within each course sit repositories for `lecture-materials` and `code`, alongside dedicated Subgroups for `students` and `graders`. Instructor materials remain private, while student and grader subgroups are configured with controlled permissions so that assignment briefs and solutions are visible only to the right people.\n\n![Screenshot of GitLab group hierarchy — institution, course subgroup, and per-student subgroups](https://res.cloudinary.com/about-gitlab-com/image/upload/v1777463673/dpxfnitv76pdmvcqtgag.png)\n\nPermissions cascade downward through the hierarchy via **Manage > Members**, allowing Dame to add students to a course's `students` subgroup with `Reporter` access and an expiration date tied to the end of the academic quarter. Students can clone and pull from assignment repositories but cannot push — keeping solution code firmly under instructor control.\n\nStudents are guided to set up SSH keys across all their working environments (local machines, cloud shells, virtual machines) so they can clone repositories and receive weekly updates via `git pull`. They copy relevant code into their own private repositories to manage their own version history.\n\n**Tip for large classes:** For larger cohorts, adding students by hand is impractical. GitLab's REST API lets you automate subgroup creation and membership from a list of usernames. Below is a sample Python script that handles this:\n\n```python\n    import gitlab\n    from datetime import datetime\n\n    # Connect to your GitLab instance\n    gl = gitlab.Gitlab('https://gitlab.com', private_token='YOUR_PRIVATE_TOKEN')\n\n    # Target parent group ID (e.g., the ID for \"css430 > students\")\n    parent_group_id = 12345678\n\n    # Set expiration: typically the beginning of the next month after quarter end\n    expiry_date = '2025-01-01'\n\n    # List of collected student usernames\n    student_list = ['alice_css430', 'bob_css430', 'carol_css430', 'dave_css430', 'eve_css430']\n\n    for username in student_list:\n        try:\n            # 1. Create a personal subgroup for the student\n            subgroup = gl.groups.create({\n                'name': username,\n                'path': username,\n                'parent_id': parent_group_id,\n                'visibility': 'private'\n            })\n\n            # 2. Add student to the new subgroup with Expiration\n            user = gl.users.list(username=username)[0]\n            subgroup.members.create({\n                'user_id': user.id,\n                'access_level': gitlab.const.REPORTER_ACCESS,\n                'expires_at': expiry_date\n            })\n            print(f\"Success: Subgroup created and student added for {username}\")\n        except Exception as e:\n            print(f\"Error processing {username}: {e}\")\n```\nThere is also an [open source project that automates class management](https://gitlab.com/edu-docs/class-management-automation) published by GitLab that provides additional tooling for this workflow.\n## Give feedback where the work actually lives\n\nOnce the structure is in place, the feedback workflow is where GitLab's value becomes most apparent to students. Dame asks students to submit assignments by opening a **[merge request](https://docs.gitlab.com/user/project/merge_requests/)** in their repository. This gives instructors an immediate, clean diff of everything the student has written.\n![A GitLab merge request showing inline code comment function for an instructor](https://res.cloudinary.com/about-gitlab-com/image/upload/v1777467468/icclzyglbkwlvfysggbi.png)\nInstructors can click any line of code and leave an **inline comment** — not just flagging what is wrong, but explaining why, and pointing to what to look at next. Students receive this feedback in direct context with their code, which is far more actionable than a comment at the bottom of a submitted document.\n\n## Join GitLab for Education\n\nSetting up your first GitLab assignment takes some initial effort, but once the structure is in place it largely runs itself. The real payoff goes beyond organization: Students graduate having worked daily in an environment that mirrors professional software development, building habits around [version control](https://about.gitlab.com/topics/version-control/) and [code review](https://docs.gitlab.com/development/code_review/) rather than learning them as abstract concepts.\n\nIf you are just getting started, keep it simple. Begin with a single course group, one assignment template, and a basic pipeline. The structure will grow naturally alongside your confidence with the platform.\n\nMake sure to **[sign up for GitLab for Education](https://about.gitlab.com/solutions/education/join/)** so that you and your students can access all top-tier features, including unlimited reviewers on merge requests, additional compute minutes, and expanded storage.\n\n> [Apply to the GitLab for Education program today](https://about.gitlab.com/solutions/education/join/).",[622,725],"open source",{"featured":14,"template":15,"slug":727},"teaching-software-development-the-easy-way-using-gitlab",{"content":729,"config":741},{"description":730,"authors":731,"heroImage":733,"date":734,"title":735,"body":736,"category":11,"tags":737},"AI-generated code is 34% of development work. Discover how to balance productivity gains with quality, reliability, and security.",[732],"Manav Khurana","https://res.cloudinary.com/about-gitlab-com/image/upload/v1767982271/e9ogyosmuummq7j65zqg.png","2026-01-08","AI is reshaping DevSecOps: Attend GitLab Transcend to see what’s next","AI promises a step change in innovation velocity, but most software teams are hitting a wall. According to our latest [Global DevSecOps Report](https://about.gitlab.com/developer-survey/), AI-generated code now accounts for 34% of all development work. Yet 70% of DevSecOps professionals report that AI is making compliance management more difficult, and 76% say agentic AI will create unprecedented security challenges.\n\nThis is the AI paradox: AI accelerates coding, but software delivery slows down as teams struggle to test, secure, and deploy all that code.\n\n## Productivity gains meet workflow bottlenecks\nThe problem isn't AI itself. It's how software gets built today. The traditional DevSecOps lifecycle contains hundreds of small tasks that developers must navigate manually: updating tickets, running tests, requesting reviews, waiting for approvals, fixing merge conflicts, addressing security findings. These tasks drain an average of seven hours per week from every team member, according to our research.\n\nDevelopment teams are producing code faster than ever, but that code still crawls through fragmented toolchains, manual handoffs, and disconnected processes. In fact, 60% of DevSecOps teams use more than five tools for software development overall, and 49% use more than five AI tools. This fragmentation creates collaboration barriers, with 94% of DevSecOps professionals experiencing factors that limit collaboration in the software development lifecycle.\n\nThe answer isn't more tools. It's intelligent orchestration that brings software teams and their AI agents together across projects and release cycles, with enterprise-grade security, governance, and compliance built in.\n\n## Seeking deeper human-AI partnerships\nDevSecOps professionals don't want AI to take over — they want reliable partnerships. The vast majority (82%) say using agentic AI would increase their job satisfaction, and 43% envision an ideal future with a 50/50 split between human and AI contributions. They're ready to trust AI with 37% of their daily tasks without human review, particularly for documentation, test writing, and code reviews.\n\nWhat we heard resoundingly from DevSecOps professionals is that AI won't replace them; rather, it will fundamentally reshape their roles. 83% of DevSecOps professionals believe AI will significantly change their work within five years, and notably, 76% think this will create more engineering jobs, not fewer. As coding becomes easier with AI, engineers who can architect systems, ensure quality, and apply business context will be in high demand.\n\nCritically, 88% agree there are essential human qualities that AI will never fully replace, including creativity, innovation, collaboration, and strategic vision.\n\nSo how can organizations bridge the gap between AI’s promise and the reality of fragmented workflows?\n\n## Join us at GitLab Transcend: Explore how to drive real value with agentic AI\nOn February 10, 2026, GitLab will be hosting Transcend, where we'll reveal how intelligent orchestration transforms AI-powered software development. You'll get a first look at GitLab's upcoming product roadmap and learn how teams are solving real-world challenges by modernizing development workflows with AI.\n\nOrganizations winning in this new era balance AI adoption with security, compliance, and platform consolidation. AI offers genuine productivity gains when implemented thoughtfully — not by replacing human developers, but by freeing DevSecOps professionals to focus on strategic thinking and creative innovation.\n\n[Register for Transcend today](https://about.gitlab.com/events/transcend/virtual/) to secure your spot and discover how intelligent orchestration can help your software teams stay in flow.",[738,739,740],"AI/ML","DevOps platform","security",{"featured":29,"template":15,"slug":742},"ai-is-reshaping-devsecops-attend-gitlab-transcend-to-see-whats-next",{"content":744,"config":755},{"title":745,"description":746,"authors":747,"heroImage":749,"date":750,"body":751,"category":11,"tags":752},"Atlassian ending Data Center as GitLab maintains deployment choice","As Atlassian transitions Data Center customers to cloud-only, GitLab presents a menu of deployment choices that map to business needs.",[748],"Emilio Salvador","https://res.cloudinary.com/about-gitlab-com/image/upload/v1750098354/Blog/Hero%20Images/Blog/Hero%20Images/blog-image-template-1800x945%20%281%29_5XrohmuWBNuqL89BxVUzWm_1750098354056.png","2025-10-07","Change is never easy, especially when it's not your choice. Atlassian's announcement that [all Data Center products will reach end-of-life by March 28, 2029](https://www.atlassian.com/blog/announcements/atlassian-ascend), means thousands of organizations must now reconsider their DevSecOps deployment and infrastructure. But you don't have to settle for deployment options that don't fit your needs. GitLab maintains your freedom to choose — whether you need self-managed for compliance, cloud for convenience, or hybrid for flexibility — all within a single AI-powered DevSecOps platform that respects your requirements.\n\nWhile other vendors force migrations to cloud-only architectures, GitLab remains committed to supporting the deployment choices that match your business needs. Whether you're managing sensitive government data, operating in air-gapped environments, or simply prefer the control of self-managed deployments, we understand that one size doesn't fit all.\n\n## The cloud isn't the answer for everyone\n\nFor the many companies that invested millions of dollars in Data Center deployments, including those that migrated to Data Center [after its Server products were discontinued](https://about.gitlab.com/blog/atlassian-server-ending-move-to-a-single-devsecops-platform/), this announcement represents more than a product sunset. It signals a fundamental shift away from customer-centric architecture choices, forcing enterprises into difficult positions: accept a deployment model that doesn't fit their needs, or find a vendor that respects their requirements.\n\nMany of the organizations requiring self-managed deployments represent some of the world's most important organizations: healthcare systems protecting patient data, financial institutions managing trillions in assets, government agencies safeguarding national security, and defense contractors operating in air-gapped environments.\n\nThese organizations don't choose self-managed deployments for convenience; they choose them for compliance, security, and sovereignty requirements that cloud-only architectures simply cannot meet. Organizations operating in closed environments with restricted or no internet access aren't exceptions — they represent a significant portion of enterprise customers across various industries.\n\n![GitLab vs. Atlassian comparison table](https://res.cloudinary.com/about-gitlab-com/image/upload/v1759928476/ynl7wwmkh5xyqhszv46m.jpg)\n\n## The real cost of forced cloud migration goes beyond dollars\n\nWhile cloud-only vendors frame mandatory migrations as \"upgrades,\" organizations face substantial challenges beyond simple financial costs:\n\n* **Lost integration capabilities:** Years of custom integrations with legacy systems, carefully crafted workflows, and enterprise-specific automations become obsolete. Organizations with deep integrations to legacy systems often find cloud migration technically infeasible.\n\n* **Regulatory constraints:** For organizations in regulated industries, cloud migration isn't just complex — it's often not permitted. Data residency requirements, air-gapped environments, and strict regulatory frameworks don't bend to vendor preferences. The absence of single-tenant solutions in many cloud-only approaches creates insurmountable compliance barriers.\n\n* **Productivity impacts:** Cloud-only architectures often require juggling multiple products: separate tools for planning, code management, CI/CD, and documentation. Each tool means another context switch, another integration to maintain, another potential point of failure. GitLab research shows [30% of developers spend at least 50% of their job maintaining and/or integrating their DevSecOps toolchain](https://about.gitlab.com/developer-survey/). Fragmented architectures exacerbate this challenge rather than solving it.\n\n## GitLab offers choice, commitment, and consolidation\n\nEnterprise customers deserve a trustworthy technology partner. That's why we've committed to supporting a range of deployment options — whether you need on-premises for compliance, hybrid for flexibility, or cloud for convenience, the choice remains yours. That commitment continues with [GitLab Duo](https://about.gitlab.com/gitlab-duo-agent-platform/), our AI solution that supports developers at every stage of their workflow.\n\nBut we offer more than just deployment flexibility. While other vendors might force you to cobble together their products into a fragmented toolchain, GitLab provides everything in a **comprehensive AI-native DevSecOps platform**. Source code management, CI/CD, security scanning, Agile planning, and documentation are all managed within a single application and a single vendor relationship.\n\nThis isn't theoretical. When Airbus and [Iron Mountain](https://about.gitlab.com/customers/iron-mountain/) evaluated their existing fragmented toolchains, they consistently identified challenges: poor user experience, missing functionalities like built-in security scanning and review apps, and management complexity from plugin troubleshooting. **These aren't minor challenges; they're major blockers for modern software delivery.**\n\n## Your migration path: Simpler than you think\n\nWe've helped thousands of organizations migrate from other vendors, and we've built the tools and expertise to make your transition smooth:\n\n* **Automated migration tools:** Our [Bitbucket Server importer](https://docs.gitlab.com/user/import/bitbucket_server/) brings over repositories, pull requests, comments, and even Large File Storage (LFS) objects. For Jira, our [built-in importer](https://docs.gitlab.com/user/project/import/jira/) handles issues, descriptions, and labels, with professional services available for complex migrations.\n\n* **Proven at scale:** A 500 GiB repository with 13,000 pull requests, 10,000 branches, and 7,000 tags is likely to [take just 8 hours to migrate](https://docs.gitlab.com/user/import/bitbucket_server/) from Bitbucket to GitLab using parallel processing.\n\n* **Immediate ROI:** A [Forrester Consulting Total Economic Impact™ study commissioned by GitLab](https://about.gitlab.com/resources/study-forrester-tei-gitlab-ultimate/) found that investing in GitLab Ultimate confirms these benefits translate to real bottom-line impact, with a three-year 483% ROI, 5x time saved in security related activities, and 25% savings in software toolchain costs.\n\n## Start your journey to a unified DevSecOps platform\n\nForward-thinking organizations aren't waiting for vendor-mandated deadlines. They're evaluating alternatives now, while they have time to migrate thoughtfully to platforms that protect their investments and deliver on promises.\n\nOrganizations invest in self-managed deployments because they need control, compliance, and customization. When vendors deprecate these capabilities, they remove not just features but the fundamental ability to choose environments matching business requirements.\n\nModern DevSecOps platforms should offer complete functionality that respects deployment needs, consolidates toolchains, and accelerates software delivery, without forcing compromises on security or data sovereignty.\n\n[Talk to our sales team](https://about.gitlab.com/sales/) today about your migration options, or explore our [comprehensive migration resources](https://about.gitlab.com/move-to-gitlab-from-atlassian/) to see how thousands of organizations have already made the switch.\n\nYou also can [try GitLab Ultimate with GitLab Duo Enterprise](https://about.gitlab.com/free-trial/devsecops/) for free for 30 days to see what a unified DevSecOps platform can do for your organization.",[573,24,753,754],"product","features",{"featured":29,"template":15,"slug":756},"atlassian-ending-data-center-as-gitlab-maintains-deployment-choice",{"promotions":758},[759,773,784,795],{"id":760,"categories":761,"header":763,"text":764,"button":765,"image":770},"ai-modernization",[762],"ai-ml","Is AI achieving its promise at scale?","Quiz will take 5 minutes or less",{"text":766,"config":767},"Get your AI maturity score",{"href":768,"dataGaName":769,"dataGaLocation":245},"/assessments/ai-modernization-assessment/","modernization assessment",{"config":771},{"src":772},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138786/qix0m7kwnd8x2fh1zq49.png",{"id":774,"categories":775,"header":776,"text":764,"button":777,"image":781},"devops-modernization",[753,11],"Are you just managing tools or shipping innovation?",{"text":778,"config":779},"Get your DevOps maturity score",{"href":780,"dataGaName":769,"dataGaLocation":245},"/assessments/devops-modernization-assessment/",{"config":782},{"src":783},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138785/eg818fmakweyuznttgid.png",{"id":785,"categories":786,"header":787,"text":764,"button":788,"image":792},"security-modernization",[740],"Are you trading speed for security?",{"text":789,"config":790},"Get your security maturity score",{"href":791,"dataGaName":769,"dataGaLocation":245},"/assessments/security-modernization-assessment/",{"config":793},{"src":794},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138786/p4pbqd9nnjejg5ds6mdk.png",{"id":796,"paths":797,"header":800,"text":801,"button":802,"image":807},"github-azure-migration",[798,799],"migration-from-azure-devops-to-gitlab","integrating-azure-devops-scm-and-gitlab","Is your team ready for GitHub's Azure move?","GitHub is already rebuilding around Azure. Find out what it means for you.",{"text":803,"config":804},"See how GitLab compares to GitHub",{"href":805,"dataGaName":806,"dataGaLocation":245},"/compare/gitlab-vs-github/github-azure-migration/","github azure migration",{"config":808},{"src":783},{"header":810,"blurb":811,"button":812,"secondaryButton":817},"Start building faster today","See what your team can do with the intelligent orchestration platform for DevSecOps.\n",{"text":813,"config":814},"Get your free trial",{"href":815,"dataGaName":53,"dataGaLocation":816},"https://gitlab.com/-/trial_registrations/new?glm_content=default-saas-trial&glm_source=about.gitlab.com/","feature",{"text":508,"config":818},{"href":57,"dataGaName":58,"dataGaLocation":816},1777493598228]