Migrating from GitLab to Managed Service for GitLab

You can migrate your projects to Managed Service for GitLab using the following methods:

• Self-migration: You export each project individually from the source GitLab and import them into Managed Service for GitLab without involving support. This migrates the main entities: repositories, issues with comments, merge requests, labels, milestones, wiki, and CI/CD pipelines as archives. CI/CD variables, webhooks, pipeline triggers, artifacts, and job logs are not migrated.
• Support-assisted migration: Support restores the Managed Service for GitLab instance from a backup of your custom installation. This migrates all data and settings, including projects, users, groups, access permissions, and pipelines.

Self-migrationSelf-migration

This method works well for migration of projects from any GitLab, including GitLab.com, a dedicated GitLab.com instance, and self-managed installations.

1. Export your project from the source GitLab instance:
   1. Open the project in the source GitLab.
   2. In the left-hand menu, select Settings → General.
   3. Expand the Advanced section.
   4. Click Export project.
   5. Wait for an email containing the export archive link or refresh the settings page and click Download export under Export project.
2. Create a Managed Service for GitLab instance.
3. By default, Managed Service for GitLab instances restrict import from external sources. To enable it:
   1. Open the GitLab admin panel.
   2. Go to Admin Area → Settings → General.
   3. Expand Import and export settings.
   4. Make sure the GitLab export source is enabled under Allowed import sources. If this source is not there, add it manually.
   5. Click Save changes.
4. Import a project to the Managed Service for GitLab instance:
   1. In the top-right corner, click  Create new... and select New project/repository.
   2. Select Import project.
   3. Under Import project from, select GitLab export.
   4. Enter project name and URL, then select the export file you go in the previous step.
   5. Click Import project.
5. Migrate GitLab projects one at a time.

For more information, see these GitLab guides:

• Import and export settings
• Migrate GitLab data by using file exports

Support-assisted migrationSupport-assisted migration

Before you begin, see how to run migration from a custom GitLab installation to Managed Service for GitLab.

To migrate data to a Managed Service for GitLab instance:

1. Create a Managed Service for GitLab instance.

2. Apply the same configuration to your Managed Service for GitLab instance as in your custom installation, such as OmniAuth or group access restrictions. Entities such as users, groups, and pipelines are migrated later when using your custom installation backup.

3. Find out the GitLab version of your custom installation. For correct migration, the custom installation version must match the Managed Service for GitLab version.

   1. Open your custom GitLab installation.

   2. In the left-hand menu, click Help.

      A pop-up window will display the GitLab version.

4. Test the migration:

   1. Back up your custom installation and configuration files.

   2. Provide the support team with the backup and GitLab version of your custom installation. The support team will restore the instance from your backup in Managed Service for GitLab.

   3. Once support confirms the instance restoration in Managed Service for GitLab, open it and make sure:

      • It contains all settings, data, and projects you need.
      • You can push commits and update branches.

5. Perform the production migration:

   1. Notify support of your planned migration date.
   2. On the day before the migration, switch your custom GitLab installation to Read only mode.
   3. Back up your custom installation and configuration files.
   4. Provide this backup to the support team.
   5. On the specified migration date, the support team will restore your instance from the provided backup in Managed Service for GitLab.

6. Optionally, configure the instance domain name:

   1. If you used a custom domain name for your custom installation and want to keep it, provide that domain name to the support team. They will configure it for your Managed Service for GitLab instance.
   2. In your custom installation, configure a CNAME DNS record to forward users from the Managed Service for GitLab instance domain to your custom domain.

See alsoSee also

• Running migration from GitLab to Managed Service for GitLab
• Resource relationships in Managed Service for GitLab
• Creating and activating a Yandex Managed Service for GitLab instance
• Getting Yandex Managed Service for GitLab instance info

GitLab guidesGitLab guides

• Import and export settings
• Migrate GitLab data by using file exports
• Groups
• OmniAuth
• Group access and permissions
• Back up GitLab
• Place GitLab into a read-only state
• GitLab Dedicated network access and security
• DNS settings