In any case, on the CR Vm they are the good numbers of Vif, and if there is a match between NIC and VIF between Prod server and CR server, the CR VM seem to have the right ones

Yes, for exemple on a "prod" server I have a VM like this:

PROD SERVER ( with 3 network interfaces)
NIC1: cabled on cisco switch port with VLAN1 and Network name associated ont this NIC: VLAN1
NIC2: cabled on cisco switch port with VLAN2 and Network name associated ont this NIC: VLAN2
NIC3: cabled on cisco swtch port with VLAN3 and Network name associated ont this NIC: VLAN3

VM1 on PROD SERVER:
network1 : VLAN1
network2 : VLAN2
network3 : VLAN3

and on the CR SERVER:

CR SERVER ( with 2 network interfaces)
NIC1: cabled on cisco switch port with VLAN1 and Network name associated ont this NIC: VLAN1
NIC2: cabled on cisco switch port with TRUNK and 2 Networks name associated on the NIC: VLAN2 (tagged vlan2) and VLAN3 (tagged vlan3)

The CR of VM1 on the CR SERVER becomes:

VM1-CR:
network1: VLAN1 (good)
network2: VLAN1 (bad)
network3: VLAN1 (bad)

The VLAN1 associated as the fist network have the same name on the same number of NIC and it's OK
For the rest, the name of the network is the same, but not on the same NIC number, ans it seems to be the problem ?

I was sure that the important thing was the name of the network, but in fact it is rather the NIC number I think