Anyone recently convert netscaler pols from classic to advanced using nspepi in an HA configuration? Sounds like the steps are to disable HA sync on the secondary, rename ns.conf, and rename the new_ns.conf to ns.conf and reboot to confirm all is well? Then do a failover, test, re-enable HA Sync, and reboot the new secondary? https://mickhilhorst.com/citrix/converting-citrix-adc-policies-with-nspepi/

It sounds overcomplicated. I did it for HA pair but I tackled them one by one manually with some tools (https://app.xconfig.io) to identify them as the nspepi is also not 100% correct.

nspepi only converts invalid commands. Most Gateway classic policies are still in 14.1 and thus they are not converted.

NSPEPI was worthless almost any time I tried it. I agree with @jvitech and @Carl Stalhood - it's more trouble than it's worth. It's better to manually write the advanced versions. The policies need changing, but not the actions or servers, etc. Plus, you cannot mix and match classic and adv, so if global bindings of classic are on, the NS needs a restart to adjust. (side note - classic p0ols still work - despite the threats for the last 5 years or whatever it has been).

so technically upgrading from 13.0 to 13.1/14.1 will be fine? Thought i saw some items in nspepi too about features and gateway themes.

there are things that break

I have migrated some from 13.0 to 13.1 recently. Used the latest check_invalid_config script from github to get the list of unsupported & deprecated config. Tried nspepi once, but decided not to bother after that and just fixed up manually. https://github.com/netscaler/ADC-scripts/tree/master/nspepi