To convert an existing project to an SCLM-controlled project, bring the project groups under control one at a time beginning with the top layer of the hierarchy, which is the production (frozen) group, and work downward. Most projects to be converted already exist in some kind of logical hierarchy. If all production source code is stored in one logical place and code under development is stored elsewhere, you have at least a two-layer hierarchy. Before migration can begin, you must place the source code to be converted into partitioned data sets.

There are many advantages to using the preceding method. First, you can bring a project under SCLM control in discrete steps, over a period of time. Second, SCLM can locate integrity problems in the existing hierarchy and fix them systematically during the conversion process. Third, SCLM performs the conversion using the same tools that developers use in the normal development process. Thus, you ensure consistency within the hierarchy, and you become familiar with SCLM. Finally, from the conversion process, you receive an indication of the performance that you can expect of SCLM during the development process.