Guide: Migrate from Azure DevOps to GitLab
Dec 3, 2025Evgeny Rudinsky

Summary
This post details the planning and execution phases for migrating from Azure DevOps to GitLab, focusing on repository migration (using Congregate or built-in import), pipeline migration (Azure Pipelines to GitLab CI/CD), and migration of other assets like work items, boards, artifacts, and container images. It highlights the importance of inventorying assets, understanding tool capabilities (Congregate vs. built-in import), planning organizational structure in GitLab, and managing authentication and permissions. The post also touches on the use of AI-based pipeline conversion and the differences in permissions models between the two platforms.
More from the GitLab Installation and Updates trail
- Consolidate your GitLab stack with Gitaly on Kubernetes
- Changes to packages.gitlab.com: What you need to know
- GPG key used to sign GitLab package repositories' metadata has been extended
- GitLab extends Omnibus package signing key expiration to 2028
- Deploying the world's largest GitLab instance 12 times daily