Forum Discussion

ShabinSGS's avatar
ShabinSGS
Brass Contributor
Nov 20, 2025

How to Move Azure DevOps Organization to New Organization

Dear Team,

We are using our existing Azure DevOps (abc.net), now we want to move to new org. (abc.com) without losing history, work items etc. Are there any options without 3rd party tools. Kindly advise.

Thanks & Regards,

Shabin

 

4 Replies

  • Azure DevOps doesn’t currently offer a built-in way to migrate an entire organisation. As Kidd_lp notes, you can mirror your Git repositories and export/import work items and YAML pipelines via REST or Excel, but boards and test plans have to be recreated. Some customers use the open-source Azure DevOps Migration Tools to copy boards and history between orgs, but that’s still a third-party solution and requires careful mapping and testing. Without such tooling you’ll need to rebuild boards/backlogs and reassign permissions manually. I recommend doing a trial migration in a test project to validate your process before committing.

  • ShabinSGS's avatar
    ShabinSGS
    Brass Contributor

    Hi Kidd_lp

    Thank you so much for the details.

    Let me check these.

    Thanks.

  • Azure DevOps does not support a direct, full organization-to-organization migration without third-party tools. However, you can manually migrate key components like repositories, work items, and pipelines using built-in features and APIs:

    1. Git Repositories
    •    Clone the repo from the old org: 

    git clone --mirror https://dev.azure.com/abc-net/project/_git/repo


    •    Push to the new org: 

    git push --mirror https://dev.azure.com/abc-com/project/_git/repo


    •    This preserves branches, tags, and commit history.
    2. Work Items
    •    Use Azure DevOps REST API or Excel integration: 
    o    Export work items to Excel using the Azure DevOps Office Integration tool.
    o    Re-import into the new org using Excel or REST API.
    o    You will need to manually map fields, states, and IDs.
    3. Build and Release Pipelines
    •    Export YAML pipelines directly from the old org and import into the new one.
    •    For classic pipelines: 
    o    Use the Export to JSON feature (via REST API).
    o    Recreate manually in the new org.
    4. Boards, Backlogs, and Test Plans
    •    No native export/import.
    •    Use Excel or REST API to extract and recreate.
    •    Consider manually recreating board configurations and test suites.

    • ShabinSGS's avatar
      ShabinSGS
      Brass Contributor

      We have changed the owner of the subscription to the new organization and updated the billing account. Could you please advise if this is sufficient, or if any issues might occur when we hand over the old Cloud DevOps? Do we need to assign permissions for each project individually to the users?

Resources