I use PSADK for every single SCCM application and have also been working on migrating from Zenworks for the last 1.5 years. I started using it with Zenworks just before we had SCCM up and running. Customize the Toolkit folder as much as you like once, then reuse it as a template for future projects. Begin your project by copying and renaming your Toolkit template folder as step one, then populate the files folder, supportfiles folder and edit your Deploy-Application.ps1 script. There will be times you may want to alter AppDeployToolkitConfig.xml for a particular application, such as when you set the User Experience Installation Behavior as Install for user vs. Install for system for the deployment type and the <Toolkit_RequireAdmin>True</Toolkit_RequireAdmin> item in the xml (target user profiles, etc.). If I ever need to install something that isn’t managed by SCCM (like another agency), I just grab the folder and run Deploy-Application.exe and everything is present and works as scripted. Once a new version of PSADK came out, I did the same with the new toolkit and kept moving forward – no need to worry about existing scripts with changes in PSADK versions.