Crap. It's yet another SCCM bug. The SCCM console GUI reflects what we did: side-by-side migration from machine A to machine B I found and looked at the underlying migrationstatus.xml file.