audience

Migrating your test data from Team Foundation Server (TFS) to a new project or Azure DevOps Services can be a stressful task. Regular work items like user stories and tasks move easily. However, testing data requires extra care.

Using a specialized solution like the open-source Migration Tools for Azure DevOps by nkdAgility helps solve this problem. This tool ensures you keep your original settings and test setups completely intact. Why Test Migration is Hard

Basic export methods can move simple text. However, they often fail to keep important relationships between items. Testing data depends on complex links:

Test Configurations map your tests to specific hardware or software settings.

Test Suites group your test cases together in hierarchies or dynamic queries.

Shared Steps allow multiple tests to use the exact same actions.

If you try to move these manually, you will lose the connections. You would have to rebuild every single link from scratch. How the Migration Tool Protects Your Data

The Azure DevOps Migration Tools use specialized programs called “processors”. These processors handle each piece of your test data in a specific order.

Step 1: Move Variables & Configurations ➔ Step 2: Migrate Test Cases & Shared Steps ➔ Step 3: Rebuild Plans & Suites 1. Preserving Test Configurations

Before moving a single test case, the tool replicates your Test Variables and Test Configurations in the new destination. This step ensures that when test cases arrive, they immediately pair with the correct environment settings. 2. Rebuilding Complex Test Suites

The tool relies on the TfsTestPlansAndSuitesMigrationProcessor. This processor reads your old project tree and rebuilds your exact hierarchy. It wires your test cases back into their original locations. The tool successfully handles:

How-to: Migrating Plans and Suites | Azure DevOps Migration Tools