Migrating from DevOps onpremise to GitHub enterprise and retaining DevOps code history

[matjasko-cmd]

Select Topic Area

Question

Body

Hello - Can anyone advise on how, in general, to migrate from DevOps on-premise to GitHub enterprise while maintaining/migrating the code version history in DevOps? Can this be accomplished 'without' first moving DevOps onprem to Azure DevOps cloud? Thank you!

[Balaji-Coder06]

Yes — you can migrate directly from Azure DevOps Server (on-prem) to GitHub Enterprise without first moving to Azure DevOps Services (cloud), while fully preserving Git commit history.

The key point is this: Git history lives in the repository itself, not in the DevOps platform. As long as your on-prem DevOps repos are Git (not TFVC), the full commit history, branches, and tags can be migrated intact.

General approach:
Clone the Azure DevOps on-prem Git repo
Use a mirror clone to preserve all refs:
git clone --mirror https://devops-onprem/org/project/_git/repo

Create a repository in GitHub Enterprise
On GitHub Enterprise (Cloud or Server), create an empty repo.

Push the mirror to GitHub Enterprise
git push --mirror https://github.company.com/org/repo.git

This preserves:
Full commit history
Branches and tags
Authors and timestamps

What does NOT migrate automatically:
Azure DevOps Boards (work items)
Pipelines / classic build definitions
Wiki (unless manually exported)
PR discussion history
Permissions and policies

These need separate migration (manual or via tools).

Tools that can help:
GitHub’s gh CLI (for repos and PRs if source is cloud)
Third-party tools like OpsHub or Git-TFS (if TFVC is involved)

When Azure DevOps Cloud is needed:
Only if you want automated migration of PRs, comments, and work items using GitHub’s official migration tooling. It’s not required for Git history.

Summary:
✅ Direct on-prem → GitHub Enterprise is supported
✅ Full Git history can be preserved
❌ DevOps metadata requires separate handling
❌ Azure DevOps Cloud is optional, not mandatory
This is a common enterprise migration path and works reliably when repositories are Git-based.

[matjasko-cmd]

Thank you. The challenge is that most of our DevOps repos are not Git (they are TFVC). Any path forward with this to move DevOps history into GitHub?

…

On Tue, Jan 20, 2026 at 11:44 AM Balaji S ***@***.***> wrote: Yes — you can migrate directly from Azure DevOps Server (on-prem) to GitHub Enterprise without first moving to Azure DevOps Services (cloud), while fully preserving Git commit history. The key point is this: Git history lives in the repository itself, not in the DevOps platform. As long as your on-prem DevOps repos are Git (not TFVC), the full commit history, branches, and tags can be migrated intact. General approach: Clone the Azure DevOps on-prem Git repo Use a mirror clone to preserve all refs: git clone --mirror https://devops-onprem/org/project/_git/repo <https://urldefense.com/v3/__https://devops-onprem/org/project/_git/repo__;!!HE3Wh9YiWbHP!yx7jvcVNjRdX42QTYY8to1C49e3lNycnaEx_RohV7tCxO3O_II6NeP7wBvLBo941ehhBJI7xw11ku6GHMS03qV-D$> Create a repository in GitHub Enterprise On GitHub Enterprise (Cloud or Server), create an empty repo. Push the mirror to GitHub Enterprise git push --mirror https://github.company.com/org/repo.git <https://urldefense.com/v3/__https://github.company.com/org/repo.git__;!!HE3Wh9YiWbHP!yx7jvcVNjRdX42QTYY8to1C49e3lNycnaEx_RohV7tCxO3O_II6NeP7wBvLBo941ehhBJI7xw11ku6GHMdIJyhLO$> This preserves: Full commit history Branches and tags Authors and timestamps What does NOT migrate automatically: Azure DevOps Boards (work items) Pipelines / classic build definitions Wiki (unless manually exported) PR discussion history Permissions and policies These need separate migration (manual or via tools). Tools that can help: GitHub’s gh CLI (for repos and PRs if source is cloud) Third-party tools like OpsHub or Git-TFS (if TFVC is involved) When Azure DevOps Cloud is needed: Only if you want automated migration of PRs, comments, and work items using GitHub’s official migration tooling. It’s not required for Git history. Summary: ✅ Direct on-prem → GitHub Enterprise is supported ✅ Full Git history can be preserved ❌ DevOps metadata requires separate handling ❌ Azure DevOps Cloud is optional, not mandatory This is a common enterprise migration path and works reliably when repositories are Git-based. — Reply to this email directly, view it on GitHub <https://urldefense.com/v3/__https://github.com/orgs/community/discussions/184756*discussioncomment-15551220__;Iw!!HE3Wh9YiWbHP!yx7jvcVNjRdX42QTYY8to1C49e3lNycnaEx_RohV7tCxO3O_II6NeP7wBvLBo941ehhBJI7xw11ku6GHMQ_6sk_V$>, or unsubscribe <https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/B3TG2DZH7NL75BZI53XZ4ST4HZLQHAVCNFSM6AAAAACSJOZYHCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNJVGEZDEMA__;!!HE3Wh9YiWbHP!yx7jvcVNjRdX42QTYY8to1C49e3lNycnaEx_RohV7tCxO3O_II6NeP7wBvLBo941ehhBJI7xw11ku6GHMb-hqdod$> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Kevin 412-397-6904

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬