For now, (unfortunately) auto-migration doesn’t happen for machines with attached volumes, which is likely also why OP is seeing this error (it is normally hidden away by the auto-migration process). For now the recommended solution to this for machines with volumes is to manually fork a new volume from the old one, which is also covered in the docs (though under a different section).