How to move projects between collections of an Azure DevOps server?

user_6136513 0
Viewed 3155

I have installed an Azure DevOps server on my local server and I've created DefaultCollection. After a few months, we add more collections. Now we want to move some projects from DefaultCollection to new collections.

I always choose 'Import' function from 'Repos' section to move all history, branches, commits, pushes of a repository. But when I put an Azure DevOps address, Import function does not work and throws an error:

Import request cannot be processed due to one of the following reasons:

  • Clone URL is incorrect.
  • Credentials are incorrect.
  • Clone URL points to an empty repository.

All reasons FIXed in my process and throws the same error again! When I change the address to another Git repository of other Git servers(Not DevOps server), it works fine. What's the problem with this?

devops azure-devops azure git
3 Answers

For this issue ,enabling the movement of projects between collections of an Azure DevOps server is a longstanding request from many customers.

From the uservoice we can know that: enabling team project move would be a huge amount of work due to architectural decisions made way back in the early days of Team Foundation Server. So I am afraid this feature will not be supported in the short term.

Here are some alternate approaches that you can use as a work around:

For Azure DevOps Server you could consider using Team Project Collection Split. This is a good alternative when you need to archive projects, split organizations, or reduce the number of team projects in a single collection, etc. However, this does not help you when you need to merge organizations, or consolidate team project collections.

  • WIMigrator supports migrating work items between projects. However, this tool does not copy Boards artifacts such as sprints, plans, dashboards, etc.
  • Migration Tools for Azure DevOps supports migrating work items, test suites, and test plans between projects. It also supports merging many team projects into a single team project along with several other capabilities.
  • VSTeam supports migrating pipelines between projects however some code or PowerShell scripting will be required.
user_115081920
user_127427730
user_82359710
Related