As part of the migration from API Connect v5 to API Connect v10: After the unpack, is it possible to convert existing APIC v5 APIs to v10 native mode using the AMU utility? I've attempted running AMU port-to-apigw but the resulting migration produces artifacts that still contain a parse and proxy (v1.5.0) policy in the assembly. My understanding is that native v10 APIs should contain an invoke policy (v2.0.0) and no parse policy as these set of APIs are pure "proxy".

thanks

Yes, this is completely possible.  Please see this section in the API Connect documentation: https://www.ibm.com/docs/en/api-connect/10.0.5.x_lts?topic=deployment-converting-apis-datapower-api-gateway.  There are subsections that talk about the options you can set for port-to-apigw including which versions of policies to use.

Hi Vikesh,
I'll also add to Steve's comment that the reason the default policies are version 1.5.0 policies are that these policies are meant to be fully compatible with the way APIC v5 worked.  It's perfectly fine to override these defaults and specify the 2.0.0 policy versions, but I would suggest when doing so you fully test all of your APIs in case some behavioral difference between the policy versions cause your APIs to behave differently if not incorrectly.  You'll definitely get the best performance from the 2.0.0 policies, but test and verify that the migrated APIs are working as expected.
Best Regards,
Steve

I guess you attempted with default migration configuration (./apicm archive:port-to-apigw <path>). If no parameters are specified, then the default parameters are used. when you are porting to DataPower Gateway you can specify migration configuration parameters. 

Please refer the below link to port with migration configuration parameters.

Configuring migration options for DataPower API Gateway - IBM Documentation

You can specify the invoke_2.0.0 policy to replace the proxy_1.5.0 in migration configuration. Then migration utility converts the proxy policy to invoke 2.0.0, but specifying invoke_2.0.0 can cause migration errors or run-time errors. After porting, you have to review and verify all changes in the API YAML file.

Parse actions will be added to the assembly depending on the policies specified in the migration configuration. You have to remove them, when you are fine-tuning APIs after migration. Please refer below link for more information.

Parse actions added to the API assembly after migration - IBM Documentation