Salesforce Dictionary — Free Salesforce GlossarySalesforce Dictionary

AppExchange Upgrades

Platform🟡 Intermediate

Definition

AppExchange Upgrades refers to the process of updating an installed AppExchange managed package to a newer version. When a publisher releases a new version, subscribers receive a notification and can install the upgrade, which updates the package components while preserving customizations and data. Push upgrades allow publishers to automatically upgrade subscribers' packages.

Real-World Example

Consider a scenario where an architect at Skyline Consulting is working with AppExchange Upgrades to extend their Salesforce implementation to meet growing business demands. AppExchange Upgrades provides the additional capability they need without requiring a separate third-party system, keeping everything within the trusted Salesforce ecosystem and reducing integration complexity.

Why AppExchange Upgrades Matters

When an ISV releases a new version of a managed package, existing subscribers receive notifications through their Setup and can choose to upgrade. Upgrades replace the package components (Apex classes, Lightning components, custom objects, metadata) with the new versions while preserving subscriber customizations outside the package and all existing data in custom objects. Managed package namespaces and components are upgraded safely because the installing org cannot directly modify managed components.

Publishers also have the option to deliver Push Upgrades, which automatically upgrade subscribers without requiring them to click. Push Upgrades are commonly used for security patches, critical bug fixes, and small incremental releases. Larger or breaking releases are typically distributed as Pull Upgrades, where each subscriber chooses when to apply. Pre-release notes and compatibility information are typically published alongside each version so admins know what to expect before upgrading.

How Organizations Use AppExchange Upgrades

  • Skyline ConsultingAlways installs AppExchange upgrades into a full sandbox first, runs regression tests, and only then promotes to production. This catches compatibility issues with other installed packages before they affect real users.
  • Vertex GlobalReceives Push Upgrades for security patches automatically but has a change management policy that manually reviews feature upgrades before applying them. This balances staying current with controlling change risk.
  • NovaScaleMonitors the release notes of every installed package and tracks the version gap between their installed version and the latest. Any package more than two versions behind triggers a review of whether to upgrade.

🧠 Test Your Knowledge

1. What happens to subscriber customizations and data during an AppExchange upgrade?

2. What is a Push Upgrade?

3. What is the recommended testing approach before a production upgrade?

See something that could be improved?

Suggest an Edit