Make your Atlassian to GitLab Migration Simple

What’s In the Guide?

This is our honest take on running discovery and planning for a migration from Jira, Confluence, and Bitbucket to GitLab. We’re transparent about what migrates easily, what takes some tweaking, and what needs to be redesigned completely. This migration is not one-to-one, you’re consolidating from multiple tools down to a unified platform. That comes with some challenges, but also a lot of opportunity to streamline your processes and build new efficiency into your SDLC.

We want this to be genuinely helpful to your organization. We include overviews of each of the topics, detailed tables comparing features and limits, and recommendations from our experiences doing these migrations. We’ve even included a check list at the end so you can make sure you haven’t missed anything.

Some of the topics covered are: building a reliable inventory of your Atlassian setup, deciding what GitLab isn’t going to replace, a rundown of GitLab’s Jira importer tools, rebuilding workflows and automation rules, analyzing seat count to size your license correctly, and more.