Copy Structure with dependency knowledge
I can't understand why I get errors that a list doesn't exist when it's processing a lookup field, even when the dependent list was already selected as a list to migrate. That seems like just doing some simple dependency logic ahead of time.
Now, I have to run the same migration 3 times to slowly migrate the objects up the "dependency tree" , each migration has less and less errors, this just seems silly.
Steve Hughes commented
I went ahead and populated the lookup lists first using copy content only migration. It is kind of disappointing that the copy structure and content migration doesn't try and populate any lookup lists first then populate the lists dependent on the look up lists last.