For those of you who have unfortunately found yourself managing applications for a company that is closing its doors, you’ve undoubtedly been faced with the task of decommissioning an application or platform. Hopefully, your application documentation is thorough enough to make this process less painful but this article aims to outline the steps involved and open a conversation to address any gaps and refine the process. Please note that while some of the content may apply across platforms, this article is specific to applications that are managed on-premise as opposed to cloud-based (SaaS) apps.
Not all items listed below will apply for all scenarios and the order or execution is dependent on your own environment.
⭐ALWAYS decommission lower-environments (dev, test, staging) first before decommissioning your production environment.⭐ Another good rule-of-thumb before fully decommissioning any application is to first disable services for a period of time. If no issues surface, proceed with the decommission process. You will also want to take a final backup in the event that you need to restore the application.
I hope this helps. Please feel free to suggest edits to this article!
Laurie Sciutti
Platform Administrator
FRB
San Francisco, CA
207 accepted answers
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
0 comments