![ExtraHop Reveal(x) for IT Operations vs. Nyansa [EOL] report](https://www.peerspot.com/assets/media/images/icons/pdf-80836ec5.svg){kind=icon}
![Nyansa [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_64/i8676a39lscwk1j2bgjuyjwm9p92.png)
![Nyansa [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_30/i8676a39lscwk1j2bgjuyjwm9p92.png){kind=small}
![Nyansa [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_40/i8676a39lscwk1j2bgjuyjwm9p92.png){kind=small}
We're just trying to identify the application interdependencies, which normally reside on different servers, including web servers, database servers, enterprise service bus, et cetera, up to your presentation layer before we start moving stuff around. Normally, the reason why we use these tools is to understand what assets we have, where they're deployed, and how they enter and operate before we decide to go move something from point A to point B. The solution is going to allow me to establish a wave or migration plan where you have different waves of migration and then you actually have move groups to try and get your application moved from A to B seamlessly. A to B could be on-premise to on-premise. It could be on-premise to cloud. Et cetera. The solution can tell me what components can I deploy, for example, into a cloud space, without having to refactor my applications since that can be quite time-consuming and costly.
