Transition requirements are the capabilities a solution must have, and the conditions it must meet, to move an organization from the current state to the future state; they stop being needed once the change is complete. Data conversion, user training and cutover are the textbook examples. In the BABOK Guide v3 they are one of four requirement types, and Certified Business Analysis Professional (CBAP) questions use them as an easy, often missed, point.
Last verified: October 2026 (exam facts from iiba.org).
Why transition requirements matter on the CBAP exam
Transition requirements matter because the exam tests classification, and the transition type is the one candidates forget exists. According to IIBA, the CBAP exam has 120 scenario-based multiple-choice questions in 210 minutes. Requirements Analysis and Design Definition carries 30% and Requirements Life Cycle Management 15%, and both lean on knowing which type a requirement is.
A typical question describes a need that vanishes after go-live. Candidates who think only in "functional versus non-functional" miss it.
How the BABOK classification schema works
The BABOK Guide v3 classification schema (section 2.3) sorts requirements into four types. The full section is behind IIBA's member login on the Knowledge Hub, so the table below paraphrases it, checked against secondary summaries by Modern Analyst and It Ain't Boring.
| Type | What it states | Lifespan |
|---|---|---|
| Business requirements | goals, objectives and outcomes that explain why the change exists | the whole change |
| Stakeholder requirements | needs of stakeholders that must be met to reach the business requirements; a bridge to solution requirements | the whole change |
| Solution requirements: functional | behaviour and information the solution must manage | steady state |
| Solution requirements: non-functional | quality conditions such as performance, security, usability | steady state |
| Transition requirements | capabilities and conditions needed only to get from current to future state | temporary |
Three features set transition requirements apart:
- They are temporary. Once the old system is retired and people work in the new way, they have no further use.
- They need both states defined. A Modern Analyst answer notes they can only be written once the current state and the future solution are both known, because they describe the gap between them.
- They cover people, process and data. Typical items are data conversion, training, parallel running, temporary interfaces and business continuity during the switch.
Worked example: replacing a bank's loan system
A bank is replacing its legacy loan system. The team identifies two needs: migrate ten years of account data, and train branch staff on the new system. Both needs disappear once the new system is live.
Here is how a business analyst would split the requirements:
| Requirement | Type | Why |
|---|---|---|
| Loan officers can approve loans up to a set limit | Functional | the system does this every day after go-live |
| Approval screen responds in under two seconds | Non-functional | a quality condition in steady state |
| Branch managers need to see approval backlog daily | Stakeholder | a need of one group, stated in their terms |
| Convert ten years of account data, with reconciled balances | Transition | needed only once, at cutover |
| Train all branch staff before the switch date | Transition | needed only during the move |
| Run old and new systems in parallel for one month | Transition | ends when the old system is switched off |
Why each wrong option fails
The LinkedIn version of this question offered four choices. Each wrong one has a reason it looks right.
- Functional requirements describe behaviour the solution supports in steady state. Data migration is behaviour, but one-off behaviour of the move, not of the solution.
- Non-functional requirements describe quality attributes like performance or security. Training is not a quality of the system.
- Stakeholder requirements state what a group needs in its own terms. Branch staff do need training, but the classifier is the temporary nature, not who benefits.
The trap is to classify by who asks or by what the item resembles. Classify by when the need ends.
What practitioners say
Practitioners agree that transition work is often neglected until late.
- Kupe Kupersmith argued in a 2011 BA Times article that teams spend too little time on how a solution moves into production. He lists data conversion, coordinating releases with integrated applications, training, organizational change and the cutover approach (hard switch, parallel run or pilot). His summary: "Projects are for people."
- The Dummies guide by Kupersmith, Paul Mulvey and Kate McGoey describes transition requirements as temporary capabilities across people, process and technology, including awareness and moving data to new structures (Dummies).
- Alex Shlega, reading BABOK in 2016, picked out business continuity as an example and noted that many analysts struggle to explain the other types too (It Ain't Boring).
Common misconceptions
- "Transition requirements are project tasks." They are requirements: they state capabilities and conditions. The plan to deliver them is separate.
- "Only IT migrations have them." Any change that moves people from one way of working to another has them, including process and policy changes.
- "Training is a stakeholder requirement." It is a need of a stakeholder group, but its temporary nature makes it transition in the schema.
Practice Questions
These are original questions written for this article.
Question 1
A bank is replacing its legacy loan system. The team must migrate ten years of account data and train branch staff. Both needs disappear once the new system is live. How does BABOK classify them?
A. Functional requirements B. Non-functional requirements C. Transition requirements D. Stakeholder requirements
Answer: C. Both are needed only to move from the current state to the future state. Functional and non-functional requirements describe the steady-state solution; stakeholder requirements describe a group's needs regardless of lifespan.
Question 2
A retailer moving to a new warehouse system needs a temporary interface that sends orders to both old and new systems for six weeks. What type of requirement is this interface?
A. Business requirement B. Transition requirement C. Non-functional requirement D. Functional requirement
Answer: B. The interface exists only during the parallel run and is removed afterwards.
Question 3
When can a business analyst fully define transition requirements?
A. Before eliciting business requirements B. Once the current state and the future solution are both defined C. Only after go-live D. At any time, since they are independent of the solution
Answer: B. Transition requirements describe how to cross the gap between two states, so both states must be understood first.
Related topics
Our older summary of functional requirements documents and the guide to non-functional requirements cover the steady-state types. Requirements architecture shows how all four types fit together, and Strategy Analysis explains the current and future state descriptions that transition requirements bridge. For the full technique set, see the map of all 50 BABOK techniques.
The CBAP simulator is not live yet. For scenario practice on another IIBA exam, try our CBDA practice exam.
FAQ
What are transition requirements in BABOK?
They are requirements that describe the capabilities and conditions needed to move from the current state to the future state. They are temporary and are no longer needed once the change is complete. Data conversion and training are the usual examples.
What is the difference between transition and functional requirements?
Functional requirements describe what the solution does in normal operation after go-live. Transition requirements describe what is needed only during the move, such as converting data or running old and new systems in parallel.
Are training requirements transition requirements?
Yes, when the training exists to help people move to the new solution. Once staff are working in the new way, the training need for the transition ends.
Sources
- IIBA: Certified Business Analysis Professional (CBAP)
- IIBA Knowledge Hub: BABOK Guide 2.3 Requirements Classification Schema
- Modern Analyst: Basic classification of requirements in the BABOK
- BA Times: The Business Analyst's Role in Transition
- Dummies: How to Define Transition and Technology Requirements
- It Ain't Boring: Business Analysis, Reading BABOK