Honestly, there are too many to count - better for your site to identify the MICS licensed components (from CA) and any MICS field-developed applications (FDAs) your site may have developed to read in additional SMF/system-log data sources not supported by a CA-distributed component. And, for any given CA-distributed MICS component, identify the MICS 'features' for that component which you are using -- consider whether or not each one would need to be replicated with an MXG-only solution.
Also, consider that MICS and MXG are not truly equals, when considering the different / individual features each provides, to include MICS comprehensive documentation / database dictionary and methodology guidance content. Also, there is at least one MICS component, Accounting / Chargeback, for which you would have to write your own SAS application code/solution to replicate it with an MXG-only solution. And with MICS Base, you also have features (some may not be used today obviously), such as MICF (both adhoc and production reporting), MICS ZONE/HOLIDAY definitions and MICS common elements in most every MICS database file (helps address learning-curve with MICS novice users), and other features like MICS CHECKPOINT processing, and MICS incremental update facility.
Suggest before making such a management change-of-direction (with an MXG only solution), consider the time/effort and administration / system-tailoring necessary to replicate those 'required MICS features' that would need to be ported to MXG.
Regards,
Scott Barry
SBBWorks, Inc.