After the track unsharded project completes, the only collections expected to be moved by changePrimary (using the movePrimary coordinator) are those that are client system namespaces. Any other collections should be tracked, and their presence indicates a problem in the sharding metadata.

If changePrimary encounters some untracked collection it does not expect, it should throw an error.