A Gradual Strategy for Migrating Classic Pipelines to YAML
Your organization uses Azure DevOps Server (on-premises) and plans to migrate to Azure DevOps Services. You have hundreds of classic build and release pipelines. You need to design a migration strategy that minimizes downtime and allows for a gradual transition. The team wants to use the new YAML-based pipelines after migration. What should you do?
Quick Answer
Exporting classic pipeline definitions as JSON and manually recreating each one as YAML is the approach that actually supports a gradual, low-downtime migration — pipelines convert incrementally, each one gets validated before the next, and existing classic pipelines keep running untouched in the meantime. There's no automated classic-to-YAML converter in the Azure DevOps Migration Tools, so this manual, phased path is the realistic one.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Export the classic pipeline definitions as JSON, and manually recreate them as YAML pipelines in Azure DevOps Services.
Exporting classic pipeline definitions as JSON and manually recreating them as YAML pipelines in Azure DevOps Services allows for a gradual migration, minimizing downtime. The team can convert pipelines incrementally, ensuring familiarity with YAML syntax and validating each pipeline before moving the next. Option B is wrong because recreating all pipelines from scratch is inefficient, error-prone, and does not leverage the existing pipeline logic. Option C is wrong because the Azure DevOps Migration Tools are designed for data migration (work items, repos, etc.) and do not automatically convert classic pipelines to YAML. Option D is wrong because migrating pipelines as classic first and then planning a separate conversion project delays the adoption of YAML and introduces additional rework.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Export the classic pipeline definitions as JSON, and manually recreate them as YAML pipelines in Azure DevOps Services.
Why this is correct
This allows gradual migration while maintaining existing pipelines.
- ✗
Recreate all pipelines from scratch using YAML in the new organization.
Why it's wrong here
Recreating from scratch is time-consuming and error-prone.
- ✗
Use the Azure DevOps Migration Tools to automatically convert classic pipelines to YAML.
Why it's wrong here
The migration tools do not support automatic conversion to YAML.
- ✗
Migrate all pipelines as-is (classic) and then plan a separate project to convert them to YAML.
Why it's wrong here
This does not minimize downtime and requires extra effort later.
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
JSON
JSON is a lightweight, text-based format for storing and exchanging data that is easy for humans to read and write and easy for machines to parse and generate.
Key term
Pipeline
A pipeline is an automated series of steps that takes code from development to production, ensuring quality and speed.
About these practice questions
Courseiva writes every AZ-400 question from scratch — 823 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on AZ-400
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Your organization uses Azure DevOps Server (on-premises) and is planning to migrate to Azure DevOps Services. You have hundreds of build and release pipelines. The migration must be done with minimal downtime and with validation that each pipeline works after migration. You have a test collection of 20 critical pipelines that must be validated first. What is the best approach?
medium- A.Export all pipelines as JSON from the server and import them into Azure DevOps Services. Skip validation to save time.
- B.Manually recreate the 20 critical pipelines in Azure DevOps Services and test them. Then recreate the rest manually.
- ✓ C.Use the Azure DevOps Migration Tools to replicate the test pipelines to a new Azure DevOps Services organization. Validate, fix issues, then migrate the remaining pipelines in batches.
- D.Perform an in-place upgrade of Azure DevOps Server to the latest version, then migrate to Azure DevOps Services using the Data Migration Tool.
Why C: Using the Azure DevOps Migration Tools to perform a trial migration to a test organization allows you to validate and fix issues before migrating the full collection. Direct upgrade is not supported. Manual recreation is error-prone and not minimal downtime. Skipping validation risks breaking pipelines.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-400 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-400 exam.