I found out this was a knock-on effect of an earlier error. Plone should really have halted migration at the point of that error, instead of continuing to this stage.