Skip to the content.

Reference Overview

This documentation is for a preview version of the Azure DevOps Migration Tools. If you are not using the preview version then please head over to the main documentation.

Overview > Reference

The system works by setting one or more Processors in the json configuration file. This processor can have many ProcessorEnrichers that enable aditional features, and must have at least two Endpoints; a Source Endpoint and a Target Endpoint. Each Endpoint may have additional EndpointEnrichers that add additional Client specific functionality.

What types of things do we have

We currently have a WorkItemTrackingProcessor with Endpoints for InMemory (for testing), FileSystem, and Tfs. You can mix-and-match Endpoints so that you would be able to migrate your WorkItem data from Tfs to FileSystem as needed.

The model should also work for other data Teams, SharedQueries, PlansAndSuits.

How the Configuration file flows

{
  "Version": "0.0",
  "LogLevel": "Verbose",
  "MappingTools": [
    {
      "$type": "MappingToolA",
      "Enabled": true
    },
    {
      "$type": "MappingToolA",
      "Enabled": true
    }
  ],
  "Processors": [
    {
      "$type": "ProcessorA",
      "Enabled": true,
      "Enrichers": [
        {
          "$type": "EnricherA",
          "Enabled": true
        },
        {
          "$type": "EnricherB",
          "Enabled": true
        }
      ],
      "Endpoints": [
        {
          "$type": "EndPointA",
          "Direction": "Source",
          "Enrichers": [
            {
              "$type": "EnricherA",
              "Enabled": true,
            },
            {
              "$type": "EnricherB",
              "Enabled": true,
            }
          ]
        },
        {
          "$type": "EndPointB",
          "Direction": "Target",
          "Enrichers": [
            {
              "$type": "EnricherA",
              "Enabled": true,
              "AttachmentWorkingPath": "c:\\temp\\WorkItemAttachmentWorkingFolder\\",
              "AttachmentMaxSize": 480000000
            }
          ]
        }
      ]
    }
  ]
}

What was added here

While we still have a long way to go this is a strong move towards v2. It will add object confusion while we build within the context of the existing tool. However, I have marked many of the objects as [Obsolite("This is v1 *", false) so that we can distinguish in the confusing areas.

Legacy Folders