Helix streams are an innovative way to manage concurrent development, dependencies, and other common branching and release activities. Streams provide projects with a workflow framework based on best practices observed over many years. Streams are flexible enough to accommodate many branching and development models, including the mainline branching model and a promotion model suitable for website development.

Moving an existing project into streams requires some planning. Although the mechanical aspects of moving the data into a stream depot are straightforward, other areas must be addressed, including the impact on users and other tools.

This document highlights preparatory steps to consider before moving an existing project to streams. Although some planning is required, moving to streams presents an opportunity to take advantage of its built-in productive workflow process and address legacy bottlenecks.