How to convert legacy Custom packages to windows!

As already mentioned above when using 3rd-Party Packages it is recommended to do some formals checks before executing the conversion from Legacy to windows. Regarding to this point we can have ~3 tracks

  • Package is available for windows
  • Package can be made available for windows (conversion, worked by the author)
  • Package can be replaced by alternates e.g. alternate packages, workarounds, code statements.

To get some more guidance feel free to checkout our InfoSet resource related to Leagcy to Windows migrations