Skip to main content
Contact us
No more CodeCommit – make the move to GitLab
Share on socials

No more CodeCommit – make the move to GitLab

Jason Spriggs
Jason Spriggs
2 December 2024
6 min read
People on a ladder next to DevOps loop
Jason Spriggs
Jason Spriggs
2 December 2024
6 min read

AWS CodeCommit is ending, prompting users to find an alternative. Adaptavist offers a seamless transition to GitLab, preserving metadata, and enhancing workflows with their migration solution.

Earlier this year, AWS decided to close new customer access to CodeCommit – a core part of its developer tools offering since 2015. For many organisations, this means a lot of upheaval and a big choice to make: where should they migrate to?
Here, we explain what's happening with CodeCommit, make the case for moving to GitLab, and explain how Adaptavist's solution bridges the gaps in existing migration processes. We also give you a heads-up on our how-to guide to GitLab migration (coming soon!).
Clipboard with a list

AWS CodeCommit to GitLab migration guide

Sign up here to get your hands on it first when it's available.

What is CodeCommit and why is it being discontinued?

AWS CodeCommit is a managed source control service. It had the added benefit of being tightly integrated with other AWS services.
AWS has not given a reason for why the service is being discontinued; however, existing customers can continue to use it for the time being. CodeCommit is being EOLed in July 2025, so customers have until then to find a new hosting provider. AWS has said it "continues to invest in security, availability, and performance improvements for AWS CodeCommit" but has no plans to introduce any new features.

What’s next for CodeCommit users?

For many AWS customers who've relied on CodeCommit for their source-control needs for nearly 10 years, the announcement no doubt came as a shock with significant implications. It's also prompted development teams to think about migrating to alternative Git providers.
AWS hasn't left them floundering—it's provided step-by-step instructions about how to export repositories and move to alternative Git hosting platforms, including GitLab, GitHub, and BitBucket Cloud. Check out AWS's guidance here. Several migration methods are available, including cloning your repository, mirroring, and migrating specific branches.
It's vitally important that all these businesses find a reliable and efficient alternative to meet their source-control needs. So now it's just a case of deciding where to migrate to.

Our commitment to GitLab

Adaptavist partners with best-in-class technologies that help organisations deliver better software faster. We build DevOps toolchains based on business needs and can integrate tools that work across the entire software development lifecycle, including Git repositories.
That includes our relationship with GitLab – we're a GitLab Select Channel Partner and Professional Services Certified Partner. And we're committed to helping organisations like yours get the most out of this incredible tool, including providing seamless migration solutions.
As a cloud-based Git repository and DevOps platform, GitLab streamlines the developer experience, from testing and monitoring to deploying code, all from one platform.
In light of the AWS changes, we've been working with GitLab to develop a native solution for automating migrations from AWS CodeCommit to GitLab, both for SaaS and self-hosted environments. It's ideal for teams wanting to migrate to GitLab and integrate with other AWS services.

Bridging the gap with our open-source solution

At Adaptavist, we are always looking for opportunities to support and contribute to open-source software, making our ideas and innovations accessible to as many people as possible. The code base we’re contributing to at GitLab is a great example of our open-source efforts in action.
And our solution goes far beyond the Git repository migration outlined by AWS…
We know that many of our customers need more than just their code migrated to the destination system, in this case, GitLab. Unless the customer has the resources to implement custom scripting as part of their migration, Pull Requests (what GitLab refers to as Merge Requests), as well as other repository metadata, get left behind.

Why migrate with Adaptavist?

For organisations using GitLab Premium or Ultimate on SaaS or Self-Hosted, our solution means you can hold onto your valuable repository metadata without all the hassle. And it's available to anyone with data in CodeCommit, regardless of your organisation's size or vertical.
With bags of experience under our belts, our migration services ensure you can make a smooth transition from CodeCommit to GitLab with enhanced workflows for maximum efficiency.

Get your hands on our how-to migration guide

Making the move from CodeCommit to a new Git repository is a big project with lots to consider. That's why we’re releasing a free how-to guide to GitLab migration packed with useful information, including step-by-step instructions for a smooth process.
We're launching the guide after AWS re:Invent 2024 (2–6 December), so make sure you sign up to be the first to know when it's available.

Migrate with confidence and Adaptavist

That AWS July deadline will creep up fast. Don't leave your Git repository out in the cold – start planning your migration today. To get started, why not sign up for our how-to guide, and then we’ll let you know as soon as it’s available.
Written by
Jason Spriggs
Jason Spriggs
Consulting Team Lead
Jason, an award-winning DevOps consulting team lead, providing architectural vision and technical expertise. At Adaptavist, Jason and his team implement a wide range of industry-leading technologies and processes for clients.
DevOps
GitLab
AWS