The Package Conversion Manager (PCM) in System Center 2012 Configuration Manager (SCCM) SP1 is an essential tool for migrating legacy packages and programs into the modern, state-based application model. Transitioning to applications provides advantages like user-device affinity, dependencies, requirements, and single-instance storage.
The operational best practices for deploying the Package Conversion Manager include: Establish a Tiered Migration Strategy
Do not attempt to process your entire package library at once. Use a systematic, multi-phase testing workflow to minimize production impact:
Isolate Test Packages: Select a small, diverse subset of representation packages to prioritize first.
Use a Test Environment: Always migrate and analyze packages inside a staging or test environment prior to executing conversions in production.
Validate Readiness: Use PCM to run bulk analysis and bucket your software into readiness states: Automatic, Manual, or Fix.
Export and Re-import: Successfully converted and tested applications can then be exported from staging and cleanly imported into production. Fix Content Sources and Storage
PCM relies heavily on clean package history and structures to translate information correctly: Package Source Best practice – Configuration Manager 2012