How does OpsHub Integration Manager help integrate your tools of choice?

Siloed tools severely hinder cross-team collaboration and create compliance challenges. Break free from data siloes and easily maintain cross-system traceability across tools. Provide full context to make informed decisions that drive innovation.

How does OpsHub Migration Manager migrate data across platforms?

Risky, disruptive tool modernization is not an option for the future-ready enterprise. Undertake tool transition painlessly, with zero downtime and high data fidelity. Scale effortlessly to meet evolving business needs. Modernize without compromising on productivity.

How does OpsHub Data Bridge extract insights from your data?

Most analytics are not actionable and not grounded in data. Unify multiple data sources with history and domain-aware analytics. Leverage data-backed decision making to consistently exceed expectations.

Discover our story, vision, and impact.

Get Started wIth 30 Days Free Trial

Blog

ADO to ADO Migration in 2026: A Guide to Cross-Tenant Moves, Mergers, and Splits

Moving between Azure DevOps organizations or tenants? This guide covers moves, merges, and splits, what migrates, your options, and the five stages to run it. OpsHub Migrator for Microsoft Azure DevOps (OM4ADO) supports it with history, user identity mapping across tenants, and delta migration, so teams keep working.

← Back to blog

OM4ADO Free and Pro Editions: What Each One Migrates

Azure DevOps migration needs range from TFS work items and history to repositories, tests, pipelines, and customized projects. OM4ADO offers Free and Pro editions to address these needs. This blog explains what each edition includes and when to use it.

Ankita Mehta

September 30, 2026

share this post:

What is OM4ADO, and is it free?

OpsHub Migrator for Microsoft Azure DevOps (OM4ADO) is a migration solution for Microsoft Azure DevOps and Team Foundation Server environments, co-developed with Microsoft. It runs through a graphical user interface and needs no scripting. Its free edition migrates projects from Team Foundation Server or Azure DevOps Server to Azure DevOps Services, with no licence key nor credit card required. The free edition is an edition of the product, not a trial. Within the path and volume, it covers; it runs a production migration.

What does OM4ADO do during migration?

The following six capabilities apply in both editions:

Migrates without halting operations: Data moves while teams keep working in the source TFS or ADO, so cutover is a scheduling decision, not an outage.
Keeps history and traceability intact: Revisions keep their original dates and authors. Comments, attachments, and inline images arrive with them, and links point at the migrated items, not back at the old TFS or ADO organization.
Keeps data current with delta runs: After the initial migration, OM4ADO moves only new or changed data, reducing what remains for cutover.
Supports phased migration: Incremental migration allows teams to migrate in phases with continuous TFS access—no cold downtime.
Recovers from failures without starting over: A failed item is logged with a reason instead of ending the run. Migrations resume from the last successful point, and failures can be retried from OM4ADO GUI.
Configure the migration via UI-based setup, not with code: Configure and manage migrations with a drag-and-drop GUI, suitable for both technical and non-technical users.

How do OM4ADO Free and Pro differ by migration need?

Both OM4ADO Free and OM4ADO Pro support Azure DevOps migration. The Free edition covers TFS to Azure DevOps migration, while the Pro edition covers additional, Azure DevOps entities, and different ADO use cases. The purpose of this table is to help organizations map their requirements to the documented edition capabilities. It does not position one edition as better than the other.

Capability	Free	Pro
Core migration capabilities
Standard and custom work items	Yes	Yes
Work item history	Yes	Yes
Comments and attachments	Yes	Yes
Relationships and linkages	Yes	Yes
Inline images and user mentions	Yes	Yes
TFVC changesets	Yes	Yes
TFVC changeset history	Yes	Yes
Projects having same customization	Yes	Yes
Delta migration	Yes	Yes
Migration management and usability
Migration setup and migration progress in the interface	Yes	Yes
Failure management and retry in the interface	Yes	Yes
Resume migration runs	Yes	Yes
Selective project migration	Yes	Yes
Additional entities and scenarios
Test plans, test suites, test runs, and test results	No	Yes
Changeset labels	No	Yes
Build and release pipelines	No	Yes
Queries, dashboards, and widgets	No	Yes
Area and iteration paths	No	Yes
Users, teams, and groups	No	Yes
Import and export of user mapping	No	Yes
Parallel migration of multiple projects	No	Yes
Projects having different customizations	No	Yes
Git repository migration	No	Yes
Migration paths
TFS (on-prem) to Azure DevOps (cloud)	Yes	Yes
Azure DevOps to Azure DevOps (cloud to cloud)	No	Yes
Azure DevOps (cloud) to TFS (on-prem)	No	Yes
TFS to TFS (on-prem version upgrade)	No	Yes
Merging or splitting instances	No	Yes
Support
Community support	Yes	Yes
Professional support	Add-on	Yes

The Free Edition can migrate a project of any size, but only up to 1000 work items and 1000 TFVC changesets, beyond that you need the Pro edition. Free edition users can merge multiple TFS projects into one Azure DevOps target by running separate installations, though it doesn’t reconcile IDs or relationships across sources the way Pro’s merging capability does. If your migration sits inside the Free column, there is nothing to buy. Download the free edition from here and run your first project.

How does an OM4ADO migration work?

Here are steps to configure and run the migration using OM4ADO:

Step 1: Create a new migration configuration

Start by clicking New Migration in OM4ADO. Select Azure DevOps Server (TFS) as the source endpoint and Azure DevOps Services as the target endpoint.

OM4ADO supports migrations between:

Azure DevOps Server (TFS) to Azure DevOps Services (VSTS)
Azure DevOps Server (TFS) to Azure DevOps Server (TFS)
Azure DevOps Services (VSTS) to Azure DevOps Services (VSTS)

You can migrate directly from TFS / Azure DevOps Server versions 2010, 2012, 2013, 2015, 2017, 2018, 2019, 2020, and 2022 without upgrading the source instance.

Step 2: Select the data to migrate

After clicking Next, select the data you wish to migrate. Choose the entity types you want to migrate. OM4ADO allows you to select from multiple options, including:

Work items
Version control (with labels)
Area paths and iteration paths
Queries, dashboards, widgets, etc.

Step 3: Select projects and validate templates

Select one or more projects to migrate. Ensure that the project name and process template are the same on both source and target. If a mismatch exists, OM4ADO will display a warning. In such cases, create the target project with the same name and template before proceeding.

Step 4: Map users between source and target

Map users to preserve fields such as Assigned To, Created By, and Changed By.

OM4ADO automatically maps users where display names match
Bulk user mapping can be done using an Excel import/export for large user bases

Step 5: Validate, run, and monitor the migration

OM4ADO validates differences between source and target process templates and highlights mismatches for review. Click on Finish and tool will automatically create the configuration. Once the configuration is complete, click on Yes to begin the migration. While the migration is happening:

Teams can continue working in the source system during migration
Incremental changes are automatically synchronized to the target
Migration progress can be monitored via View Migrations
OM4ADO also supports flexible cutover, allowing additional delta syncs even after the main migration completes.

Which OM4ADO edition does your migration use case need?

Four factors determine which OM4ADO edition you need: the migration path, the entities that must move, whether the customizations match, and project volume. Company size is not one of them. A three-person team moving between two Azure DevOps organizations needs Pro, because that path is a Pro path. A large team moving one in-scope TFS project uses the free edition.

Choose the Free edition when all of these are true:

Migration path: TFS/Azure DevOps Server to Azure DevOps Services
Entities: Work items and TFVC data
Customization: TFS and ADO use the same customization
Volume: Within the Free edition limits

Choose the Pro edition when any of these apply:

Different migration scenarios, including TFS to TFS, TFS to Azure DevOps, Azure DevOps Server to Azure DevOps Services, and Azure DevOps to Azure DevOps migrations.
Additional Azure DevOps entities, such as test plans, test suites, test cases, repositories, pipelines, dashboards, and queries.
Different customizations in TFS and ADO instances
Merge/split scenarios
Parallel migration
Volume exceeds Free limits

Conclusion

OM4ADO Free and Pro use the same migration engine but are suited to different migration requirements. Free is designed for straightforward Azure DevOps and TFS migrations within its supported limits, while Pro provides additional capabilities for larger and more involved migration scenarios.

Choosing between them comes down to your specific migration requirements, including the migration path, Azure DevOps entities involved, source and target organization customizations, merge or split scenarios, migration volume, and the level of history and traceability you need to preserve. Evaluating these factors upfront helps you select the right edition for your migration and move to Azure DevOps with the data, relationships, and history your teams need to continue working effectively from day one.

Count first. The OpsHub Data Discovery Utility reports work item, revision, test entity, and TFVC changeset counts for the projects you point it at, so you know which column you are in before installing anything.

Frequently Asked Questions (FAQs)

Is OM4ADO free?

Yes. OpsHub Migrator for Microsoft Azure DevOps (OM4ADO) has a free edition that migrates projects from Team Foundation Server (TFS) or Azure DevOps Server to Azure DevOps Services. It needs no licence key and no credit card. OM4ADO also has a paid Pro edition that covers more migration paths and more Azure DevOps entities.

How do I migrate from TFS to Azure DevOps?

A TFS to Azure DevOps migration follows five steps: connect the source Team Foundation Server; connect the target Azure DevOps organization; map the projects and fields; run the migration while teams keep working; then check the result and run a final delta before cutover. OpsHub Migrator for Microsoft Azure DevOps (OM4ADO) does all five through a graphical interface with no scripting, and its free edition covers this path.

Can OM4ADO migrate between two Azure DevOps organizations?

Yes, in the Pro edition. OpsHub Migrator for Microsoft Azure DevOps (OM4ADO) Pro supports Azure DevOps Services to Azure DevOps Services migration, including organization to organization and tenant to tenant, plus merging several instances into one and splitting one across several. The free edition covers Team Foundation Server or Azure DevOps Server to Azure DevOps Services only.

Is OM4ADO only for enterprise or large migrations?

No. OpsHub Migrator for Microsoft Azure DevOps (OM4ADO) handles Azure DevOps migrations of different sizes. A team moving one Team Foundation Server project with a few hundred work items uses the same product as an organization consolidating several Azure DevOps instances. Which edition applies depends on the migration path, the entities involved, whether customizations match, and project volume, not on the size of the organization.

Have more questions about your use case?

Evaluation Toolkit