<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=571159) </details> <!--IssueSummary end--> ## Problem Child pipelines (parent-child pipeline relationships) are not being migrated when using GitLab direct transfer to migrate projects. This results in the loss of pipeline relationship context after migration, breaking workflows that depend on parent-child pipeline structures. ## Impact - **Broken CI/CD workflows** that rely on parent-child pipeline relationships - **Loss of pipeline context** and traceability - **User confusion** when pipeline relationships disappear after migration ## Steps to reproduce 1. Create Test Project with Parent-Child Pipelines on the source 2. Verify parent-child relationships exist: 1. Go to CI/CD → Pipelines 1. Click on a pipeline to view the pipeline graph 1. Confirm child pipeline is visible and linked to parent 2. Perform Direct Transfer Migration 4. Verify that pipelines are migrated incomplete ### Screenshots: Source:  Destination:  ## Current Behavior 1. Parent pipelines are migrated successfully 2. Child pipelines are not migrated ## Expected Behavior 1. Parent pipelines are migrated 2. Child pipelines are migrated 3. Parent-child pipeline structure remains intact after migration ## Labels ~"Category:Importers" ~"Importer:Direct Transfer" ~"type::bug" ~"devops::foundations" ~"group::import" ~"backend"