How to migrate GitLab groups and projects more efficiently

Migrating GitLab resources between instances through direct transfer has seen significant improvements, particularly for handling large projects, by introducing batching in the export and import of project relations such as CI/CD pipelines. This method splits data into smaller, manageable files and utilizes parallel processing to enhance performance, although it may increase the overall migration duration. Key factors influencing migration duration include the hardware resources of the source and destination instances and the complexity and size of the data being migrated. The process allows up to five concurrent entities to be imported, with Sidekiq workers playing a crucial role in speeding up the migration by processing multiple batches. Future plans include making direct transfer limits configurable and removing the 90-minute export timeout to accommodate larger projects, with ongoing improvements aimed at transitioning the feature from beta to general availability.

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.