Ova

How Do I Delete Managed Apps in Salesforce?

Published in Salesforce App Management 4 mins read

Deleting a managed app in Salesforce involves uninstalling its associated managed package, a process that removes all its components and data from your Salesforce org.

Understanding Managed Apps and Packages

In Salesforce, a "managed app" typically refers to an application or solution developed by a Salesforce partner and distributed through the AppExchange. These apps are installed as managed packages within your Salesforce organization. Managed packages are distinct because their components (like custom objects, fields, Apex code, Visualforce pages, and Lightning components) are protected and can only be modified by the package developer through new versions or upgrades.

Uninstalling the managed package is the definitive way to "delete" or remove a managed app from your Salesforce environment.

Steps to Uninstall a Managed Package

Follow these steps to successfully remove a managed app by uninstalling its package:

  1. Navigate to Installed Packages:

    • From Salesforce Setup, use the Quick Find box to search for "Installed Packages."
    • Select Installed Packages from the results. This page displays a list of all packages installed in your organization, including both managed and unmanaged packages.
  2. Initiate Uninstallation:

    • Locate the managed package corresponding to the app you wish to delete in the list.
    • Click the Uninstall link next to the package name.
  3. Address Data Retention:

    • Before proceeding, you'll be prompted to decide what to do with the package's data. You have two main options:
      • Save a copy of this package's data (Recommended for backup): This option exports all data associated with the package's custom objects to a CSV file, which you can then download. This is a crucial step if you might need to reference or restore this data later.
      • Do not save a copy of this package's data: This option permanently deletes all data associated with the package's custom objects without creating a backup. Use this with extreme caution.
    • Select the radio button that aligns with your data retention strategy.
  4. Confirm Uninstallation:

    • Carefully review any listed dependencies or remaining components that might prevent immediate uninstallation. You may need to manually delete specific items (like workflows, validation rules, or custom fields that reference package components) before proceeding.
    • Check the box to acknowledge that you understand the data will be permanently deleted (or saved, depending on your choice).
    • Click Uninstall to finalize the process.

The uninstallation process might take some time, especially for larger packages with extensive data. Salesforce will send you an email notification once the uninstallation is complete.

Important Considerations Before Uninstalling

Before you delete a managed app, it's vital to consider the potential impact on your Salesforce organization and users.

  • Data Loss: Uninstalling a package permanently deletes all associated data. Always back up critical data, especially from custom objects introduced by the package, if there's any chance you might need it later. Salesforce offers tools for data export.
  • Dependencies: Salesforce will prevent uninstallation if other components in your org (e.g., custom fields, validation rules, Apex code, reports, dashboards, page layouts) depend on components from the managed package. You must identify and remove or modify these dependencies before you can uninstall the package.
  • User Impact: Users who relied on the managed app for specific functionalities will lose access to those features. Communicate changes effectively to avoid disruption.
  • Licenses: Uninstallation does not automatically remove user licenses associated with the package. You might need to manually deactivate these licenses or reassign them if they are paid subscriptions managed outside of Salesforce billing.
  • Customizations: If you've built custom automations (like Process Builder flows or Apex triggers) that interact with objects or fields from the managed package, these automations will break upon uninstallation.
  • Testing: Whenever possible, perform a full uninstallation test in a Salesforce Sandbox environment first. This allows you to identify and resolve any dependencies or unexpected issues without affecting your live production data.

Best Practices for Managed App Deletion

To ensure a smooth and safe uninstallation process:

  • Backup Data: Always export package data, even if you think you won't need it. It's better to have a backup and not need it than to need it and not have it.
  • Document Dependencies: Before uninstalling, carefully document any custom code, reports, or automations that might rely on the package.
  • Communicate Changes: Inform affected users and stakeholders about the impending removal and the potential impact on their workflows.
  • Review Permissions: Ensure all user permissions and profiles that granted access to the managed app's components are updated to reflect its removal.
  • Consider Alternatives: If you're removing an app due to performance issues or lack of features, explore alternatives thoroughly before permanent deletion.

By following these guidelines and understanding the implications, you can effectively delete managed apps from your Salesforce organization.