> For the complete documentation index, see [llms.txt](https://docs.opshub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opshub.com/v7.232/knowledge-resource-index/integration-combination-examples/azure-devops-server-and-azure-devops-services-delivery-plan-mapping.md).

# Delivery Plan Mapping Configuration \[Azure DevOps Server (TFS) - Azure DevOps Services (ADO)]

## Overview

Synchronizing Delivery Plans from Azure DevOps Server (TFS) to Azure DevOps Services (ADO) enables teams to maintain consistent roadmap visibility and portfolio planning across their migration journey. This integration ensures that Delivery Plan configurations, team mappings, backlog references and scheduling views are accurately transferred to the target ADO project—eliminating manual setup efforts, preserving planning continuity, and enabling stakeholders to seamlessly track progress and dependencies in the target environment.

<code class="expression">space.vars.OIM</code> provides bidirectional integration between Azure DevOps Server (TFS) and Azure DevOps Services (ADO).

This page covers the bidirectional integration of Delivery Plan and their references entities.

## System Prerequisites

* Configuring [system pre-requisites](/v7.232/integrate/integration-prerequisites.md) is mandatory for successful system configuration.
* Check out the pre-requisites for [Azure DevOps Server and Azure DevOps Service](/v7.232/connectors/azure-devops.md#prerequisites)
* To understand the pre-requisites for enabling Delivery Plan synchronization, refer to the section: [Delivery Plan Prerequisites](/v7.232/connectors/azure-devops.md#delivery-plan-prerequisites)

## Integration Configuration

* Log in into <code class="expression">space.vars.OIM</code>. The default credentials are:\
  **User Name:** admin, **Password:** password

<div align="center"><img src="/files/cLfwpRSyL37ns1Ky0GY2" alt="" width="700"></div>

> **Note**: **Proxy parameters:** Before you proceed with the configuration, check whether the system is behind a proxy server. If yes, then set up [proxy parameters](/v7.232/manage/administrator/proxy-setting.md) in <code class="expression">space.vars.OIM</code>.

* Since Delivery Plan references dependent entities such as **Team**, make sure that the Team entities integration has successfully completed before migrating the Delivery Plans .
* Click **Integrate** on the top right corner of the screen and then click the plus \[+] icon.

<div align="center"><img src="/files/dVzCxMcENzPTvQQhgxZH" alt="" width="1100"></div>

* The integration configuration page opens:
  * Integration Configuration for **Delivery Plan** Entity:
    * Enter a unique name for the integration. For example, this integration is named **Azure DevOps Server – Azure DevOps Service Delivery Plan**.
    * Click plus \[+] icon adjacent to the System 1 and System 2 fields one by one to configure Azure DevOps Server (TFS) and Azure DevOps Service (ADO).

      <div align="center"><img src="/files/8ZdPyOTCnTkjhC8yxK81" alt="" width="1100"></div>

### Configure System(s)

* Configure Azure DevOps Server (TFS) –Azure DevOps Service (ADO) by following the steps given on [Azure DevOps Server/Service System Configuration](/v7.232/connectors/azure-devops.md#system-configuration).

<div align="center"><img src="/files/zbtWrk7zVx3h9kgge3yr" alt="" width="1100"></div>

* When you save the respective system configuration pages after configuring the systems, the systems will automatically be added to the integration. Proceed to adding projects and entities in the integration.

<div align="center"><img src="/files/d0q0TKtcYiMqsKCdyYE1" alt="" width="1100"></div>

### Select Projects and Entities

* In the **Add Project(s) to Sync** section, select the projects you want to synchronize between Azure DevOps Server (TFS) and Azure DevOps Service (ADO) by clicking them.\
  Example: **DeliveryPlan1** from Azure DevOps Server (TFS) and **DeliveryPlan2** from Azure DevOps Service (ADO).
* Once the projects are selected, define the source project and target project:
  * **Forward (>)** → data flows from Azure DevOps Server (TFS) to Azure DevOps Service (ADO)
  * **Backward (<)** → data flows from Azure DevOps Service (ADO) to Azure DevOps Server (TFS)
  * **Bi-directional (<-->)** → data flows both ways
* Once the direction is selected, the arrows will turn grey. We have selected the bi-directional flow.

<div align="center"><img src="/files/Nldp47r0RVGSnjVME6CW" alt="" width="1100"></div>

* <code class="expression">space.vars.OIM</code> fetches entities available in both systems and shows them in entities list for both systems. From the **Select Entities to Sync** section, select the relevant entities for both systems.\
  Example: **Delivery Plan** from both Azure DevOps Server (TFS) and Azure DevOps Service (ADO).
* The next step is to define the fields that need to be integrated for every entity mapped. Once the entities are selected, click the plus icon \[+] adjacent to **Select fields to be Synced** to create the mapping between these two entities. You will now be navigated to Mapping Configuration screen.

<div align="center"><img src="/files/hBetDphRzXdUqEIAzIiw" alt="" width="1100"></div>

### Mapping Fields

#### Entity: Delivery Plan

* From the **Select Entities to Sync**, select the relevant entities for both systems.\
  In this case: **Delivery Plan** from Azure DevOps Server (TFS) and Azure DevOps Service (ADO) . Create a Mapping for this entity as well.
* Following details are automatically populated in the Mapping section: **Systems, Projects, Entities, and Mapping Name**. If you wish, change the name for the mapping in the **Name** field.
* Now, either click **Create from Scratch** to define the mapping from scratch or click **Auto Map** to automatically map all fields with the same name.
* Even if you select the **Auto Map**, <code class="expression">space.vars.OIM</code> will allow you to remove or add more fields before saving mapping.
* Since a Delivery Plan references dependent entities, ensure that the mandatory field **Team** and **Teams** are mapped.
* You can also import a mapping. Refer to Delivery Plan field mapping to import the default field mapping from Azure DevOps Services to Azure DevOps Server for the Delivery Plan entity.
  * You may further modify the imported mapping based on your use case.
* Delivery Plan has various fields which require advance mapping for proper sync and handling in <code class="expression">space.vars.OIM</code>.
  * The fields requiring advance mapping are: Teams, Field criteria, Fields, Markers, Tag colors. Refer to the attached mapping above for the advanced mapping for these fields.
* Once the mapping is created, click the **Create Mapping** to create & save this mapping as well.

<div align="center"><img src="/files/vSi7UArGpLMxO7DB85In" alt="" width="1100"></div>

### Save Integration

* To save the integration in active mode, slide the **Activate Integration** button to the right.
* As the final step, click **Save** to save the integration.

<div align="center"><img src="/files/K3Q9gnlkqz6dJV6AIZvg" alt="" width="1100"></div>

* The integration will be created. You will also get a confirmation pop-up at the bottom of the screen, and the integration will be listed in the integrations list.

<div align="center"><img src="/files/xtrNM1bAuejpvetSQHqX" alt="" width="1100"></div>

### Activate and Test the Integration

* After validating that the synchronization of dependent entities **Team** is successfully completed, activate the **Delivery Plan** integration and test it by synchronizing the Delivery Plan entity.
* Test the integration by synchronizing data between the specified Azure DevOps Server (TFS) and Azure DevOps Service (ADO) projects.

> **Note**: Do not use the **integration user credentials** to create entities in the systems, as the integration will not work in that case.

* Create/Update event in the source system and check whether the event synchronizes to the target system. Wait for one minute for the data to synchronize.
* If you face any issue, please refer to [possible reasons and their fix](/v7.232/help-center-index/faqs/general-faqs.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.opshub.com/v7.232/knowledge-resource-index/integration-combination-examples/azure-devops-server-and-azure-devops-services-delivery-plan-mapping.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.