If the overall goal is PAN migration, I'd go about that a bit differently.
The original question was about how to configure a network for a particular Channel, which isn't possible in our ZB protocol stack (though the SC parameter essentially does the same thing, but offers more configurability as well). You are very correct that the SC command would cause the network to reform (in the case of a Coordinator), or leave a network in the case of a Router/End Device. When the device leaves the network it was originally on however, it will attempt to re-join a network on the same PAN ID, then probe each channel within the PAN until it finds the correct one. This then is the key to what you'll want to do to accomplish your overall goal.
Going back a step further than SC, you'll want to pre-configure a PAN ID for that network (ID parameter) to use on the Coordinator, and all devices you want to join that Coordinator's network. This way when a Network Reset occurs due to the SC parameter, the Devices which were network reset will begin looking for a new channel within "SC" for the pre-configured PAN ID "ID". Assuming all devices on the network were pre-configured for the correct PAN ID, they shouldn't have any problem migrating to the new channel on that PAN ID.
If instead you want to migrate to a new PAN ID altogether, you'd configure the new PAN ID of the current network devices over-the-air from the Coordinator (which will cause the devices to leave their current network as the ID command is applied). When the now-orphaned devices are searching for a new network, they will probe the channels on the pre-configured PAN ID. You then migrate the Coordinator to the new PAN ID last, so that all the orphaned devices attempting to join on that PAN would now find their Coordinator and re-join their original network, on the new PAN ID.