- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-11-2025 06:46 AM
Hi all EA/APM Friends!
I have not been able to find any documentation or posts for what is recommended/best practices for documenting when a business application moves from on prem to cloud. Especially when the app service is different. Ex. Legacy kronos needed servers new UKG is SASS. Essentially are you retiring the old bus app record or modifying the current apm record?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2025 06:02 AM
Probably not a best practice, but I have been changing my business apps to a hybrid while we are in transition of moving from on-prem to a cloud environment. We will create another app service to represent the new environment. As the process completes, the hybrid goes away, app services are retired and services are migrated to their respective app service. It is messy but it works, would love to hear how others are handling this situation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2025 08:22 AM
I would also agree with this approach.
In more words, the Business App is the logical entity that represents the tech stack. If you are changing the underlying tech stack (ie - migrating to the cloud), the Business App would not change from a life-cycle perspective. The Business App metadata of Install Type would be hybrid during the transition, and then cloud after, to represent that migration. In agreement with Taylor and what you are already doing, it is the operational records (App Services & supporting infrastructure) and their respective relationships that are changing.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2025 06:02 AM
Probably not a best practice, but I have been changing my business apps to a hybrid while we are in transition of moving from on-prem to a cloud environment. We will create another app service to represent the new environment. As the process completes, the hybrid goes away, app services are retired and services are migrated to their respective app service. It is messy but it works, would love to hear how others are handling this situation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2025 08:22 AM
I would also agree with this approach.
In more words, the Business App is the logical entity that represents the tech stack. If you are changing the underlying tech stack (ie - migrating to the cloud), the Business App would not change from a life-cycle perspective. The Business App metadata of Install Type would be hybrid during the transition, and then cloud after, to represent that migration. In agreement with Taylor and what you are already doing, it is the operational records (App Services & supporting infrastructure) and their respective relationships that are changing.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2025 08:33 AM
Consideration is to be given to modernization requirements. It depends if going from On Prem to Cloud is a simple "lift-and-shift" or requires an application redesign. If the app can easily be "lift-and-shift" to Cloud, all you're doing is updating the Infrastructure relationships to the existing application. If redesign, in some cases it may be easier or cost-effective to replace the app with a Cloud native solution rather than redesign/recode the antiquated app. It starts with your strategy choices, case by case.
