Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Submitted
Workspace Targetprocess
Categories Other
Created by Guest
Created on Aug 26, 2025

Team Migration Between ARTs or Portfolios

Background: Currently, migrating teams between Agile Release Trains (ARTs) or Portfolios—or any combination thereof—is a highly manual and error-prone process. It demands deep integration knowledge and strict adherence to procedural guidelines to prevent data loss or synchronization issues. This complexity is exacerbated by the dual-platform environment of TargetProcess and Azure DevOps (AzDo), where misalignment can result in the loss of Program Increment (PI), Team Iteration (TI), or team assignments.

Problem Statement: Manual migration introduces significant operational risk and overhead. Specific challenges include:

  • Loss of PI/TI metadata in TargetProcess during reassignment.
  • Disruption of team assignments and iteration context in AzDo.
  • Increased technical debt due to bi-directional sync complexity. 

Request: We propose the development of a streamlined, semi-automated (or fully automated) migration framework that enables safe and configurable movement of teams and their associated work items across ARTs and Portfolios. This solution should:

  • Provide a user-friendly interface for initiating and managing migrations.
  • Offer control over what data is migrated (e.g., team assignments, PI/TI, historical data).
  • Include validation checks to prevent data loss or sync conflicts.
  • Support rollback or audit capabilities for traceability (nice to have).

Scenarios to Support:

  1. Move a team from one Portfolio to another.
  2. Move a team between ARTs within the same Portfolio.
  3. Move a team between ARTs across different Portfolios.

Ideal Outcome: The ideal solution would also include the ability to select the volume of data to migrate with the team.

Idea priority High