APM Migration Best Practices
search cancel

APM Migration Best Practices


Article ID: 269227


Updated On:


CA Application Performance Management (APM / Wily / Introscope) CA Application Performance Management Agent (APM / Wily / Introscope) DX APM SaaS APM


Part of the APM Lifecycle is migrations.

This includes transitioning from one class of things to another. These include but are not limited to:

  • Changing to other servers
  • Changing to another OS
  • Upgrade OS, Applications, Java etc.
  • Move to another network, load balancer, firewall, etc.


  1. When changing to the above, see if the new environment is valid according to the
  • APM Compatibility Guide

      CA Application Performance Management Compatibility Guides

  • APM Release Notes

      DX Application Performance Management Release Notes

  • APM Sizing sections

      CA APM Sizing and Performance

  • APM knowledge docs

      CA Application Performance Management Troubleshooting

      AIOPs - Troubleshooting, Common Issues and Best Practices

      APM Introscope .Java Agent - Troubleshooting and Best Practices

      APM Introscope .NET Agent - Troubleshooting and Best Practices

      DX APM - UMA - Troubleshooting and Common issues

      DX Platform Troubleshooting

      Manage the APM Database

  1. Doing a phased implementation across Dev/Test/QA environments before production will lead to greater success.
  2. Review Knowledge documents for any special issues with your new environment.
  3. As part of your quarterly architecture review, see how successful the new environment is and what changes need to be made.
  4. Continuously optimizing/maintenance of the new environment is a key to success. This includes reviewing logs, metrics, and load to see if the new environment is keeping up. And determining what changes are needed.

      APM Health Tip - How to improve the performance of APM

      How to perform an APM Cluster Performance Health Check