You need to create several alternate project definitions to complete the conversion process. Because the SCLM migration utility can only run against development libraries, which are in the lowest layer of the hierarchy, you need an alternate project definition for each layer of the proposed hierarchy. The first alternate project definition you use defines only the topmost group. That group becomes a development group. The second project definition defines the topmost group and those groups that promote into it, and so on. You do not need to define non-key groups in the alternate project definitions you use for the conversion process because they should not contain any members.