Handle engineering revision transfer after migration

I’m attempting to resolve the exact same issue. Did you ever find a solution?

I would recommend you use Part Assortments instead of Engineering Transfer.  Create Parts per Site only creates parts that are not already created on each site.  Assortments also gives you more options for setting defaults as well as simulaneously creating parts for every site selected instead of one site at a time.  You also have the option to create the purchase part, supplier for purchase part, sales part with the inventory part.

An assorment is a hierarchy, with each node in the structure inheritenting the defaults from its parent.  As such, you only have to set the default values that differ from the hierarchy above each node.  A part is then connected to a node and it inherits all the part defaults set for invntory part, supplier for purchase part, purchase part, and sales part.  You will want to keep the Sales Parts and Supplier for Purchase Parts group together under their own node structure as you will not want to create those parts for every part you are transfering.  You will see what I mean when you run the Create Parts per Site.

Once setup, you can then go back to the part assorment main screen, RMB or select the node you want to create parts for (depending if you are on Cloud or not), and choose Create Part per Site.  Add the sites you want to create the part and choose if you want the sales part or supplier for purchase part created as well.  

A batch process is then spawn, which does everything for you in a single step.  You will be asking yourself, why didn’t I do this a long time ago.