Hello Ignazio,
If you are attempting to migrate between 2 NetApp backends, then you shouldn't need to worry about correctly setting the data_node_access_ip. Your ideal migration scenario is a driver-assisted-migration, since it is between 2 NetApp backends. If that fails due to misconfiguration, it will fallback to a host-assisted migration, which will use the data_node_access_ip and the host will attempt to mount both shares. This is not what you want for this scenario, as this is useful for different backends, not your case.
if you specify "manila migration-start --preserve-metadata True" it will prevent the fallback to host-assisted, so it is easier for you to narrow down the issue with the host-assisted migration out of the way.
I used to be familiar with the NetApp driver set up to review your case, however that was a long time ago. I believe the current NetApp driver maintainers will be able to more accurately review your case and spot the problem.
If you could share some info about your scenario such as:
1) the 2 backends config groups in manila.conf (sanitized, without passwords)
2) a "manila show" of the share you are trying to migrate (sanitized if needed)
3) the "manila migration-start" command you are using and its parameters.
Regards,