Answer
This is most often caused by one specific read-only custom field among the transferred set having invalid calculation logic, rather than a problem with the ACP import process itself. If it isn't immediately obvious which field is at fault, approve and publish the transferred custom fields one at a time instead of all together — this isolates exactly which specific field's logic is triggering the compilation error, since the LU will compile successfully for every field except the problematic one.