Provide migration guide from self-managed to SaaS
Problem to solve
Customers migrating from self-managed GitLab to GitLab SaaS are facing a number of challenges and pitfalls they need to be aware of. In order to enable customers making the switch to SaaS, we should provide a detailed migration guide.
We currently don't provide a guide in the docs that I was able to find. We are providing guides on migrating from other tools to a GitLab instance here, but only mention migrating from SaaS to self-managed, not the other way around. Further, that guide is very short and does not go into detail on group / rights / user mapping or importing and does not address the question of automation.
Further details
Currently, the only efficient way to migrate from self-managed to SaaS is leveraging a paid migration engagement via GitLab's Professional Services. Ideally, we could leverage some of their experience to enhance our documentation.
@munen has posted a guide on his company's blog that outlines the process brilliantly.
Proposal
Provide a comprehensive migration guide (not just manual migration of individual projects) on migrating from GitLab self-managed to SaaS in the docs.
Who can address the issue
@ngaskill as technical writer for Group Import possibly with input by Professional Services (@bryan-may).
If @munen is interested, basing the docs article on his blog post would be a brilliant start