Skip to content

OpsHub Migrator for Microsoft Azure DevOps (OM4ADO)

Copy projects between Accounts or Collections

Schedule a free 30-minute live demo with our migration experts

Get it from Marketplaces

Microsoft Azure Marketplace

Trusted by forward-thinking teams across the globe

What they said

Success stories of those who tried, experienced, and scaled growth with OpsHub

Case Study

CSI Leasing Transforms DevOps Leveraging OpsHub

CSI Leasing, Inc., based in St. Louis, MO, is a leading financial leasing and IT Asset Disposition (ITAD) company with a global presence in the Americas, Europe, and Asia-Pacific. As one of the world’s largest equipment leasing companies, it offers leasing financing, asset management, end-of-life data security, and disposal services in over 50 countries. With a five-decade focus on technology solutions, CSI Leasing is a recognized industry leader.

Case Study

OpsHub and infiNetix Implement Azure DevOps Migration in Tight Timelines and Zero Downtime

infiNetix, our client, specializes in delivering high-end information technology services, and improving business processes. Based in Annapolis, MD, they provide IT & Consulting services to help their customers implement and scale their operations and technologies. One of their customers wanted to move/migrate their data from Commercial Cloud to Government Cloud, which required migration between Azure DevOps organizations. infiNetix chose OpsHub Azure DevOps Migrator (OADOM) to help its client ease their migration journey. 

Extensive Version and Entity Support

Purpose-Built Data Migration Tool for Azure DevOps Migrations

OM4ADO enables modern enterprises to de-risk their migration challenges and helps in comprehensive and cost-effective transfer of data with full context – exclusively between any of the supported versions of Azure DevOps Server (TFS) and Azure DevOps Services (VSTS).

Supports migration of all Work Items, Test Entities (Test Case, Test Suite, Test Plan, Test Result, Test Run) Area, and Iteration, etc.

Supports migration of TFVC information and history.

Supports migration of Dashboard, Query, Widget, Pipelines, User Permissions, Groups and Teams.

Supports 2010, 2012, 2013, 2015, 2018, 2019, 2020, and 2022 versions of Azure DevOps Server.

Supports all versions of Azure DevOps Services.

Comprehensive, Risk-free Azure DevOps Migrations

Comprehensive Azure DevOps Migration.

Comprehensive Migration

Zero Downtime Migration

Migrate without disrupting operations or team productivity.
OM4ADO supports Wide Range of Data Types including embedded images, TFVC, test results, work items etc.

Migrate Test Entities and Much More

Failure Management and Recovery

OM4ADO has a robust failure management and recovery system
OM4ADO Facilitates multiple re-runs to synchronize incremental changes.

Re-run the Sync Delta Changes

Traceability

Preserves versions, transitions, history for better traceability.

Experience scalable, non-disruptive migration with OM4ADO

Schedule a free 30-minute live demo with our migration experts

How OpsHub Migrator for Microsoft Azure DevOps Works

Achieve a seamless migration with full data context and zero downtime in 5 simple steps

The first step to create a migration is to select the Source endpoint and the Target endpoint.
  • Specify the kind of data to be migrated
  • Work Items
  • Test Entities (Test Case, Test Suite, Test Plan, Test Result, Test Run)
  • Area, Iteration and Dashboard
  • Query
  • Widget
  • Pipelines
  • User permissions, Groups and Teams
Ensure that the project you select is present in the target and that the process templates of the projects on both sides (Source and Target) are same.

All the users from the source endpoint are required to be mapped with target, Azure DevOps Server/ Azure DevOps users.

The users having the same email address in both the endpoints will be automatically mapped, followed by the same display name. (Although users can edit that if they want).

Users can map the remaining users manually.

Once the user mapping is completed, the utility validates the data provided for both endpoints. After the successful validation process, the migration configuration process will start.

For detailed information about how OM4ADO enables the 5-step migration, refer here.

OM4ADO vs. Others

Here’s why OM4ADO has an edge over other migration tools:

Feature OM4ADO Manual Lift & Shift Migration Script-based Migration
Ease of migration
Yes
No
Yes
No
Migrating large projects
Easy
Difficult
Easy
No
Template customization
Yes
Difficult
No
No
Zero – downtime migration & syncing delta changes
Yes
Difficult
No
No
Failure management & recovery
Yes
No
No
No
Migrating single or partial projects in a collection
Yes
Yes
No
No
Work item Type and Project change
Yes
No
Yes
No

Common Use Cases

More that’s possible with OpsHub Migrator for Microsoft Azure DevOps

Consolidate multiple instances

Merge Azure DevOps/TFS instances, consolidating projects from different sources. Ideal for streamlining operations after mergers or managing diverse project repositories.

Move selective projects

Effortlessly relocate specific projects to new Azure DevOps/TFS spaces, enabling the segregation of projects without disrupting the overall workflow.

Migrate data with a phased, agile approach

Migrate projects incrementally for a controlled transition, ensuring reduced impact on ongoing work.

Shift to Azure DevOps without TFS upgrades

Migrate directly to Azure DevOps without the need for intermediate TFS upgrades, enabling a quicker and hassle-free shift.

Swiftly adopt new templates

Seamlessly transition between different process templates within Azure DevOps/TFS, facilitating the adaptation to evolving industry standards.

Transfer data across versions and platforms of your choice

Maintain data integrity while migrating between different versions of Azure DevOps/TFS, ensuring a smooth data transfer.

Frequently Asked Questions

OM4ADO enables seamless migration from Azure DevOps Server (TFS) to Azure DevOps supporting all versions of Azure DevOps (VSTS) and 2010, 2012, 2013, 2015, 2019, and 2020 versions of Azure DevOps Server (TFS). For example, if you want to migrate from Azure DevOps Server 2019 to Azure DevOps Services, you can do so easily using OM4ADO. You need to click on New Migration and enter the Azure DevOps server parameter as the source endpoint while Azure DevOps service parameter as the target endpoint.

You can choose the data you wish to migrate from multiple options such as work items, TFVC with labels, area and iteration, query, dashboard and widgets available for you to sync, choose as per your requirement. You are allowed to select multiple projects or single projects as per your requirement. To map, you can select users from source and target endpoints to impersonate users at the relevant fields. OM4ADO also maps users automatically where the display name is the same between two systems. Additionally, you can carry out bulk-mapping of users by using the import/export feature. Once the tool will validate and configure the systems, you can migrate successfully.

It is important to note that you can migrate from Azure DevOps Server to Azure DevOps Server/Service or any combination of the two instances. You do not need to upgrade your existing Azure DevOps Server and can directly migrate from existing version whether it is 2010, 2012, 2013, 2015, 2017, 2018, 2019, and 2020 to Azure DevOps Services.

To successfully migrate between Azure DevOps Server and Azure DevOps, there are several project-level, entity-level and user-mapping prerequisites that need to be followed. For instance,
  • OpsHub Migrator for Microsoft Azure DevOps does not create projects in the target system (TFS /Azure DevOps). It simply migrates the data between two similar projects from source system to target system. User must create project(s) manually in the target system. Project(s) need to be created with the exact name as in the source system, including space, numerical, and special characters.
  • When migrating the project with Changeset, the endpoint user should have the Basic level access and not the stakeholder. If the endpoint user does not have the correct access, the user will receive the error, “<> is using Git Version Control’”.
  • If user needs to migrate the data associated with customization, then the user must create the same customization (Entity or Field or Value) manually in the target project before starting the migration process.
  • For detailed information on the prerequisites needed to migrate from Azure DevOps Server (TFS) to Azure DevOps (VSTS) using OM4ADO, refer here.

The Azure DevOps Services (VSTS) is not replacing Azure DevOps Server (TFS). However, the Cloud offering, Azure DevOps Services (VSTS) offers additional benefits as compared to its On–premise version, Azure DevOps Server (TFS). You can read this article for more information.

With OM4ADO, it is possible to consolidate multiple instances of Azure DevOps into one with zero downtime. It provides rich data migration, including history, attachments, inline images, user mentions, etc., for a wide variety of data sets, including source code, test assets, work items, area, iteration, etc. For further information and assistance, contact our migration experts.

The Commercial edition of OM4ADO tool can help you migrate Azure DevOps projects from one organization to another with no system downtime and zero data loss. Our team of migration experts will be happy to assist you in your migration journey.

Experience scalable, non-disruptive migration with OM4ADO

Schedule a free 30-minute live demo with our migration experts