Streamline migrations with user contribution and membership mapping

GitLab has introduced a new feature aimed at improving the group and project import process through enhanced user contribution and membership mapping, providing greater flexibility and control for users involved in migrations. This update is applicable across GitLab's migration by direct transfer, GitHub, Bitbucket Server, and Gitea importers, allowing post-import mapping of contributions and memberships to users on the destination instance without relying on email addresses. Users must accept or reject their assigned contribution mappings, which initially display as placeholders, to ensure a smooth transition. The feature includes security-focused reassignment processes, and upcoming improvements like CSV-based contribution reassignment for large-scale projects are planned. Available by default from GitLab version 17.7, this feature is supported on GitLab.com, GitLab Self-managed, and GitLab Dedicated instances, with feedback encouraged to enhance the feature further.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.