Transition (Lifecycle Activity) Explained (ITIL® 5)

What Is the Transition Activity?

Transition is where a solution that's already been built and tested during Build actually gets deployed into the environment real customers and users depend on. That includes the deployment itself, along with the coordination needed to make sure the move doesn't disrupt existing services.

Because Transition sits at the boundary between "not live yet" and "live," it's often where risk gets concentrated — a solution can be perfectly built and still cause problems if the move into production isn't managed carefully.

Why Transition Is a Bridge Activity

Discover, Design, Acquire, and Build lean toward Product thinking — creating something. Deliver and Support lean toward Service thinking — running something for customers. Transition sits in the middle as a bridge: it's the activity that takes something built and hands it over into the world where it becomes an actual, live service.

Real-World Example

Once the shipment-notification feature has been built and tested in a development environment, Transition is where it actually gets deployed to production. The team schedules the deployment for a low-traffic window, confirms a rollback plan exists in case something goes wrong, and coordinates with the Service Desk so they're prepared for any related questions once it's live.

The deployment itself — flipping the switch — is a small part of Transition. Making sure it happens safely and predictably is the bigger part.

Why This Matters

Understanding Transition matters because:

• It's where risk is concentrated, since a well-built solution can still cause real problems if deployed carelessly
• It connects to existing practices like Change Enablement, which governs how risky that deployment is allowed to be
• It marks the practical line between "still in development" and "now a live service"

Common Exam Mistakes

The most common mistake is assuming Transition is just "deploying the code" — a purely technical step. In practice, it also includes the coordination, risk assessment, and rollback planning needed to move a solution into live use safely.

A second mistake is confusing Transition with Build. Build produces something tested and working in a development environment. Transition is the separate activity that moves that finished work into live use — the two are sequential, not the same step.

Memory Trick

Think:

Build proves it works.

Transition moves it into the real world.

Operate keeps it running once it's there.

If you're deploying, cutting over, or coordinating a go-live, you're in Transition.

Key Takeaways

• Transition is the lifecycle activity focused on moving a built and tested solution into live use.
• It's one of two "bridge" activities, alongside Operate, connecting Product-leaning work to Service-leaning work.
• Transition includes deployment coordination and risk management, not just the technical act of deploying.
• It connects closely to practices like Change Enablement, which governs how deployment risk is managed.
• This activity is part of the eight-activity ITIL® Product and Service Lifecycle, a frequently tested area of the ITIL® 5 Foundation syllabus.

One Practice Question