Migrating pull requests

[jderose9]

How is one supposed to migrate pull requests?

I've import my git repos from on-premise TFS to Azure Devops Services via the Azure import tool, however the pull requests didn't come along with them.

I appreciate that this tool attempts to link my migrated work items to the original pull requests. However, those pull requests are missing.

Is there another tool or feature that others are using to migrate the pull requests as well?

[MichelZ]

There is no way currently to do this with the tool, and I'm not sure if there are API's for it. Will file it as a future enhancement for now, thanks.

[jjardina]

I too need this functionality.

[skensell201]

Hi all!
Is there any news on this topic? Or should other solutions be found?

[MrHinsh]

There is no way to migrate Pull Requests as they are linked to code branches.

Just to be clear:

• There is no API for this.
• it is not, nor will it ever be possible.

[hokkolo]

I see using github migration tool, its possible to migrate PRs from ADO to GH.

[MrHinsh]

The GitHub Migration tool migrates into Github which does provide API's. This tool migrates from ADO to ADO.

The Github Migration tool focuses on migrating repos, and migrates each commit at a time, replaying each commit so that it can create and close Pull Requets.

https://docs.github.com/en/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/about-migrations-from-azure-devops-to-github-enterprise-cloud

We do not migrate Git Repos.

[skensell201]

@MrHinsh Thanks for answer

[milanjaros]

Idea:

1. Get Pull Requests for all repositories.
2. Get Pull Request Commits.
3. Link commits to work items instead of Pull Requests (because it is impossible to create PRs as is since there is no API for it).

Optionally: As we migrate only a subset of repositories, we would skip the migration of work items that only relate to those not-migrated repositories.

[MrHinsh]

Commits are already linked to work items and we maintain that link.

[coversinplayus]

Migrating pull requests involves transferring open or closed PRs from one repository to another—commonly during project restructuring or moving to a new platform. It’s important to maintain commit history, comments, and review status where possible. While GitHub doesn’t natively support PR migration, you can replicate them manually or use third-party tools to preserve key data. Always document the original PR link and ensure your team is informed to maintain continuity in code reviews and discussions.