Skip to content

GitLab implementation & migration

Move to GitLab without stopping delivery

We plan and execute migrations from GitHub, Bitbucket, Azure DevOps and Jenkins. Repositories, pipelines, permissions and integrations move in planned waves, with validation at every step.

Scope my migration GitLab CI/CD

Sources we migrate from

Common migration paths

01

GitHub → GitLab

Repositories, issues and pull requests via the GitHub importer; GitHub Actions workflows converted to GitLab CI/CD.

02

Bitbucket → GitLab

Bitbucket Cloud and Data Center imports, with Bamboo or Bitbucket Pipelines converted to GitLab CI/CD.

03

Azure DevOps → GitLab

Azure Repos imported over Git; Azure Pipelines YAML and classic pipelines re-implemented in GitLab CI/CD.

04

Jenkins → GitLab CI/CD

Jobs and shared libraries mapped to reusable CI/CD components, retiring Jenkins servers in stages.

05

Subversion → Git

History-preserving conversion with branch and tag mapping and developer onboarding.

06

GitLab → GitLab

Consolidating instances or moving between GitLab.com and Self-Managed with direct transfer.

How it works

Our migration method

  1. 1

    Inventory

    Repositories, pipelines, users, integrations and dependencies catalogued.

  2. 2

    Pilot

    A small wave proves the tooling and sets expectations on what transfers.

  3. 3

    Waves

    Teams move in planned waves with freeze windows and rollback plans.

  4. 4

    Validate

    Builds, permissions and integrations verified before the old system is retired.

  5. 5

    Enable

    Training, documentation and a support period for your developers.

FAQ

Migration questions

Can't see your question? Ask us directly. We reply within one business day.

Which platforms can we migrate from?
Commonly GitHub (cloud or Enterprise Server), Bitbucket (Cloud or Data Center), Azure DevOps, Jenkins, Subversion and older GitLab instances. GitLab provides importers for several of these; we add the planning, pipeline conversion and validation around them.
Will we lose history, issues or pull requests?
Repository history is preserved. How much metadata (issues, pull requests, comments, wikis) comes across depends on the source platform and importer. We confirm this per source in a pilot before the main migration.
How long does a migration take?
It depends on the number of repositories and pipelines. A pilot of a few projects typically takes days; full migrations run in waves over weeks so teams are never blocked.
Do we need to buy licences before migrating?
You need a subscription for the target instance, but you can often start the pilot on a trial. We align licence start dates with the migration plan so you do not pay for idle seats.

Quotation desk

Scope your GitLab migration

Tell us your current platform and roughly how many repositories and pipelines you have. We will come back with a scoped plan and licence recommendation.

  • Quotes in USD or ZAR, your choice, with VAT shown separately
  • Vendor-authorised supply, with renewal reminders
  • Edition and seat-count advice before you buy
  • Reseller enquiries handled confidentially

Prefer to talk?

Call 010 003 7197, WhatsApp +27 78 810 9342 or email hello@spreeze.co.za.

Monday to Friday, 08:00 to 17:00 SAST

1 · Who you are
2 · What you need

We reply within one business day (SAST). Quotes are subject to vendor pricing and availability; VAT is shown separately.

More on GitLab

GITLAB is a trademark of GitLab Inc. in the United States and other countries and regions. JFrog, Artifactory and Xray are trademarks of JFrog Ltd. All other product names are trademarks of their respective owners and are used for identification only.