Bidirectional migration
Move issues GitHub→GitLab or GitLab→GitHub. The direction is yours to choose.
Service
Issue Migration Service
Move issues between GitHub and GitLab, intact.
Online SaaS
Moving issues between GitHub and GitLab by hand loses exactly the things that matter: the comment history, the labels your automation depends on, the links between issues. Our migration service moves them intact.
It is a self-serve web app. Connect both sides, choose what to move, and migrate bidirectionally — as a one-time move when you switch platforms, or as an ongoing sync when you need both to stay in step.
What's included
What you get.
Metadata preserved
Issue content, labels, comments, and metadata come across — not just titles. What your workflows rely on keeps working.
One-time or ongoing
Run a single cut-over when you change platforms, or keep an ongoing sync so both sides stay consistent.
Self-serve
A web app you drive yourself — connect, select, migrate. No services engagement required.
FAQ
Issue Migration Service — questions, answered.
What gets migrated?
Issue content, labels, comments, and metadata — the context around an issue, not just its title — moved between GitHub and GitLab.
Is it one-time or continuous?
Either. Use it for a single platform cut-over, or as an ongoing sync to keep issues consistent across both platforms.
Which direction does it migrate?
Both. The service is bidirectional — GitHub to GitLab and GitLab to GitHub.
Contact
Tell us what you're trying to see.
Whether it is a product question or a consulting conversation, write to us directly — a real engineer reads every message.
support@xascade.com
A real engineer reads every message.