Tutorial: Move your personal project to a group

Tier: Free, Premium, Ultimate Offering: GitLab.com

If you created a project under a personal namespace, you can perform common tasks, like managing issue and merge requests, and using source control and CI/CD.

However, at some point you might outgrow your personal project and want to move your project to a group namespace instead. With a group namespace, you can:

  • Give a group of users access to your project, rather than adding users one-by-one.
  • View all issues and merge requests for all projects in the group.
  • View all unique users in the group namespace, across all projects.
  • Manage usage quotas.
  • Start a trial or upgrade to a paid subscription tier. This option is important if you’re impacted by the changes to user limits, and need more users.

This tutorial shows you how to move your project from a personal namespace to a group namespace.


Here’s an overview of the steps:

  1. Create a group.
  2. Move your project to a group.
  3. Work with your group.

Create a group

To begin, make sure you have a suitable group to move your project to. The group must allow the creation of projects, and you must have at least the Maintainer role for the group.

If you don’t have a group, create one:

  1. On the left sidebar, at the top, select Create new () and New group.
  2. In Group name, enter a name for the group.
  3. In Group URL, enter a path for the group, which is used as the namespace.
  4. Choose the visibility level.
  5. Optional. Fill in information to personalize your experience.
  6. Select Create group.

Move your project to a group

Before you move your project to a group:

  • You must have the Owner role for the project.
  • Remove any container images
  • Remove any npm packages. If you transfer a project to a different root namespace, the project must not contain any npm packages. When you update the path of a user or group, or transfer a subgroup or project, you must remove any npm packages first. You cannot update the root namespace of a project with npm packages. Make sure you update your .npmrc files to follow the naming convention and run npm publish if necessary.

Now you’re ready to move your project:

  1. On the left sidebar, select Search or go to and find your project.
  2. Select Settings > General.
  3. Expand Advanced.
  4. Under Transfer project, choose the group to transfer the project to.
  5. Select Transfer project.
  6. Enter the project’s name and select Confirm.

You are redirected to the project’s new page. If you have more than one personal project, you can repeat these steps for each project.

For more information about these migration steps, see Transferring your project into another namespace. A migration might result in follow-up work to update the project path in your related resources and tools, such as websites and package managers.

Work with your group

You can now view your project in your group:

  1. On the left sidebar, select Search or go to and find your group.
  2. Look for your project under Subgroups and projects.

Start enjoying the benefits of a group! For example, as the group Owner, you can quickly view all unique users in your namespace:

  1. In your group, select Settings > Usage Quotas.
  2. The Seats tab displays all users across all projects in your group.