Text of docs.gitlab.com › user › import › mapping › post_migration_mapping as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Post-migration contribution and membership mapping | GitLab Docs

/ Post-migration contribution and membership mapping Tier : Free, Premium, Ultimate Offering : GitLab.com, GitLab Self-Managed, GitLab Dedicated Introduced in GitLab 17.4 for direct transfer with feature flags named importer_user_mapping and bulk_import_importer_user_mapping . Disabled by default. Introduced in GitLab 17.6 for Gitea with feature flags named importer_user_mapping and gitea_user_mapping , and for GitHub with flags named importer_user_mapping and github_user_mapping .

Disabled by default. Introduced in GitLab 17.7 for Bitbucket Server with feature flags named importer_user_mapping and bitbucket_server_user_mapping . Disabled by default. Enabled on GitLab.com and GitLab Self-Managed in GitLab 17.7 for direct transfer. Enabled on GitLab.com in GitLab 17.7 for Bitbucket Server , Gitea , and GitHub . Enabled on GitLab Self-Managed in GitLab 17.8 for Bitbucket Server , Gitea , and GitHub .

Reassigning contributions to a personal namespace owner when importing to a personal namespace introduced in GitLab 18.3 with a feature flag named user_mapping_to_personal_namespace_owner . Disabled by default. Generally available in GitLab 18.4 for direct transfer. Feature flag bulk_import_importer_user_mapping removed. Reassigning contributions to service accounts, project bots, and group bots introduced in GitLab 18.5 with a feature flag named user_mapping_service_account_and_bots .

Enabled by default. Generally available in GitLab 18.6 for Gitea. Feature flag gitea_user_mapping removed. Reassigning contributions to a personal namespace owner when importing to a personal namespace generally available in GitLab 18.6. Feature flag user_mapping_to_personal_namespace_owner removed. github_user_mapping feature flag removed in GitLab 18.8. user_mapping_service_account_and_bots feature flag removed in GitLab 18.10.

With post-migration mapping, user contributions and memberships from source instances are initially assigned to placeholder users rather than real users on the destination instance. Because you can defer assigning to real users, you have time to review the import and reassign contributions to the correct users. This process ensures accurate attribution while maintaining control over the mapping process. Post-migration user contribution and membership mapping is available by default for migrations from: GitLab when using direct transfer GitHub Bitbucket Server Gitea When you import projects to a personal namespace , user contribution mapping and membership mapping are not supported and all contributions are assigned to the personal namespace owner.

These contributions cannot be reassigned. Prerequisites Plan for the number of users, according to the user limits . If you import to GitLab.com, set up your paid namespace. If you import to GitLab.com and use SAML SSO for GitLab.com groups , ensure all users link their SAML identity to their GitLab.com account. Post-migration mapping workflow When using post-migration mapping, GitLab maps any memberships and contributions you import to placeholder users .

Placeholder users are created on the destination instance even if users with the same email addresses exist on the destination instance. Until you reassign contributions on the destination instance, all contributions are associated with placeholder users. After the import is complete and you’ve reviewed the results, you can update the mappings as follows: Reassign memberships and contributions to existing users on the destination instance.

You can map memberships and contributions for users with different email addresses on source and destination instances. Create new users on the destination instance and reassign memberships and contributions to them. You can also keep certain contributions assigned to placeholder users to preserve historical context. When you reassign contributions to a user on the destination instance, the user can either: Accept the reassignment.

The reassignment process might take a few minutes. In subsequent imports from the same source instance to the same top-level group or subgroup on the destination instance, contributions are mapped automatically to the user. Reject the reassignment. Enterprise users Introduced in GitLab 18.0. Added an opt-in for non-enterprise member reassignment in GitLab 19.5 with a feature flag named setting_allow_non_enterprise_placeholder_reassignment .

Disabled by default. The availability of this feature is controlled by a feature flag. For more information, see the history. This feature is available for testing, but not ready for production use. If your top-level group has at least one enterprise user , you can reassign contributions only to enterprise users in your organization. This means you cannot accidentally reassign to users outside your organization. A group Owner can also allow reassignment to non-enterprise users who are already members of the group.

To turn this on: In the top bar, select Search or go to and find your group. In the left sidebar, select Settings > General . Expand Permissions and group features . Select the Allow reassigning placeholder users to all group members checkbox. When you turn on this setting, you can reassign contributions to any active member of the top-level group, its subgroups, or its projects who has at least the Guest role. Members of groups invited to any of these groups or projects also qualify.

Pending invitations, access requests, and Minimal Access members do not qualify. Members of a group invited with Minimal Access do not qualify either. In the Reassign to dropdown list, enterprise users have an Enterprise badge. This setting does not expose GitLab.com users outside your group’s membership as reassignment targets. Deleted users Contributions on the source instance that were made by a now deleted user are mapped on the destination instance to a ghost user , except when: The contribution was never properly detached from the deleted user on the source instance.

Migrating from Bitbucket Server. Placeholder users With contribution and membership mapping, you don’t immediately assign contributions and memberships to users on the destination instance. Instead, a placeholder user is created for any active, inactive, or bot user with imported contributions or memberships. Both contributions and memberships are initially assigned to these placeholder users and can be reassigned after import to existing users on the destination instance.

Until they are reassigned, contributions are associated with the placeholder. Placeholder memberships do not display in member lists. Placeholder users do not count towards license limits. Exceptions A placeholder user is not created in these scenarios: You’re importing a project from Gitea with contributions from deleted users. Contributions from these users are mapped to the user who imported the project. You have exceeded your placeholder user limit .

Contributions from any new users are mapped to an import user. Placeholder user attributes Placeholder users are different from regular users and cannot: Sign in. Perform any actions. For example, running pipelines. Appear in suggestions as assignees or reviewers for issues and merge requests. Be members of projects and groups. To maintain a connection with a user on a source instance, placeholder users have: A unique identifier ( source_user_id ) used by the import process to determine if a new placeholder user is required.

A source hostname or domain ( source_hostname ). A source user’s name ( source_name ) to help with reassignment of contributions. A source user’s username ( source_username ) to facilitate group owners during the reassignment of the contribution. An import type ( import_type ) to distinguish which importer created the placeholder. A timestamp of when the source user was created ( created_at ) in local time for migration tracking ( introduced in GitLab 17.10).

To preserve historical context, the placeholder user name and username are derived fr

The rest of this page is on the live site.