Duplicate Azure DevOps Service Organization

[JasonDWilson]

We have a client that is spinning off froma parent organization and would like duplicate their Azure DevOps Organization in their own tenancy.

What is most efficient way to make this happen?

Jason

[MrHinsh]

The most effective way would be to Change your organization connection to a different Microsoft Entra ID

[JasonDWilson]

We are only taking parts of the organization. I'd like to use your tools where possible.

When you say 'to migrate "Projects", "Process", "Repos", and "Artifacts"' -- I take it to mean that we need to create those manually. Is that correct?

As far of the order of the migration -- would this work?

1. Create the users
2. Create the process
3. Create the projects
4. Replicate Teams
5. Replication the Nodes
6. Replication the Work Items
7. Create the artificats

Do you have any advice about managing the users. Remember the users in the new instance are in a different Entra.

Thanks again for all your help.

Jason

[MrHinsh]

2. Create the process [use https://github.com/Microsoft/process-migrator]
3. Create the projects [manually or use powershell]
4. Create Repos [manually or use powershell]
5. Create the users [we have a processor to create mappings that you can use with the work item creation]
6. Replicate Teams [ we have a processor for that, but it does not add users ]
7. Replication the Work Items [Nodes are created automatically]
8. Create the artificats [manually or use powershell]

[MrHinsh]

We have a bunch of "processors" that might give additional help

[JasonDWilson]

This is exactly what I needed. Thanks again.

[MrHinsh]

If you need additional help, we can facilitate it. I just finished a migration of 80k work items for a customer... :)