GitLab Migrations

Move to GitLab.
Keep the context.

Move repositories, pipelines and teams into GitLab. Agree what must survive, what needs adapting and how your team will accept the result.

Read the case study
Illustrative engineering planning session with a laptop and a hand-drawn repository map.
Illustrative migration planning

A customer story

Three platforms.
One auditable foundation.

Defence organisation operating under NIST requirements

A leading defence organisation was running repositories across GitLab, GitHub and Bitbucket, with different CI/CD pipelines on each platform. Build jobs ran on employee home computers and personal devices, creating an untenable situation for an organisation operating under NIST compliance requirements.

OTTRA consolidated the repositories into a single self-managed GitLab Ultimate instance on Azure. We rebuilt CI/CD infrastructure on a centralised Kubernetes cluster and embedded security scanning and compliance controls into every pipeline.

Every repository migrated, with full commit history preserved. Build execution moved from personal devices to auditable, containerised infrastructure, giving the organisation a secure platform ready to scale in a regulated defence environment.

Know what moves.
Verify what arrives.

When work spans platforms, start with the history, permissions and delivery paths the move must preserve.

A mapped migration

Inventory repositories, users, metadata, pipelines and integrations. Record the supported transfer method, limitations, exceptions and acceptance checks.

Working delivery paths

Adapt the pipelines and integrations in scope. Check runners, capacity, secrets, access and security controls against your environment.

An accepted handover

Validate the agreed data and representative builds and workflows. Document exceptions, team guidance, follow-up owners and conditions for retiring the source.

Sources, rehearsal and cutover

The route from GitHub, Bitbucket, Azure DevOps, SVN or another GitLab environment depends on what you need to preserve. Check GitLab’s import guidance for supported data and methods.

Agree the destination, access model, sequence, responsibilities, maintenance window, recovery approach and decision-maker. Rehearse a representative sample and resolve exceptions before cutover. Your team accepts the result before the old platform is retired.

Paysafe
“Working with OTTRA was straightforward from start to finish. They know GitLab inside out, and that confidence came through in everything they delivered.”
Krasimir Bozukov, Enterprise Architect, Paysafe

What must move
with your code?

Bring the source and target platforms, approximate repository and team counts, key integrations and cutover constraints.

Discuss your migration

We agree scope, timing and cost before work starts.