Migrating by direct transfer is generally available

Migrating GitLab groups and projects by direct transfer, now generally available from GitLab 18.3, simplifies the process of moving resources between GitLab instances using either a user-friendly UI or flexible API. This new method eliminates the need for manual file exports and imports, allowing users with the Owner role to directly migrate top-level groups, including sub-groups and projects, while offering enhancements such as post-import user contribution mapping and reliable handling of large projects through resource batching and concurrent execution. The feature, enabled by default on GitLab.com and requiring administrator activation on GitLab Self-Managed and Dedicated, provides better migration insights and is optimized for recent GitLab versions, though it still requires network connectivity between instances, limiting its use in air-gapped networks. Users are encouraged to familiarize themselves with the migration process, including user contribution mapping, and can review migration results via the group import history page or API endpoints. Feedback on further improvements is welcomed as GitLab continues to iterate on this feature.

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.