---
schema_version: "1"
id: b0297bf0399f6a3e01b67990446f717fa3d1d2dd3d9ad10c60e4f5ab1ad50159
title: Upgrade Your Managed Package
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/distribution_upgrading_packages.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.distribution_upgrading_packages.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: cd5444a29719a9502243ae8ce92817f257dec51f62da6afed80505a6e3c7464e
description: Salesforce supports upgrades for managed packages only. Providers can publish an upgrade for a managed package and notify installers that the new version is available.
products:
  - Salesforce Platform
  - Cross Cloud
release: "264"
---
# Upgrade Your Managed Package

Salesforce supports upgrades for managed packages only. Providers can publish an upgrade for a managed package and notify installers that the new version is available.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Salesforce Classic (not available in all orgs)</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Group</strong>, <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
      <colgroup>
        <col style="width:50%">
        <col style="width:50%">
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d29076e78">User
            Permissions Needed</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d29076e78 ">To upload packages:</td>

          <td class="slds-cell-wrap" style="vertical-align:top;" headers="d29076e78 ">Upload AppExchange Packages</td>

        </tr>
        <tr class="">
          <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d29076e78 ">To install and uninstall packages:</td>

          <td class="slds-cell-wrap" style="vertical-align:top;" headers="d29076e78 ">Download AppExchange Packages</td>

        </tr>
      </tbody>
    </table>

To install a new version of a managed package, review the list of new items included in the upgraded package.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-setup-264-0-0-production-enus/6f21df35-9ea0-4f53-ac94-45c3b5dfd5bc/images/icon_note.png)

Note Some package items, such as validation rules or record types, don't display in the Package Item list but are included in the package and install with the other items. If there are no items in the Package Items list, the package contains only minor changes not recorded in the Package Items list.

Installers of a managed package can then install the upgrade as follows:

- Then, install the upgrade in the same way you install any other package from the AppExchange. If the publisher provided a link to the new version, follow the link to the package posting and install it in your organization. The first page of the install wizard lists the current version you have installed, the version you’re about to install, and a list of additional components included in the new version.

## Considerations for Upgrading Managed Packages

Consider the following when upgrading a managed package:

- All existing custom objects that were previously deployed are still deployed. Salesforce prompts you to deploy any new custom objects or previously undeployed custom objects.
- Profile settings for components in a package are editable by the customer but not upgradeable by the package developer. If the developer changes any profile settings after releasing the package, those changes won’t be included in an upgrade. Customers will need to manually update the profile settings after upgrading the package. In contrast, permission sets in a package are upgradeable by the developer, so any changes the developer makes will be reflected in the customer organization after upgrading the package.
- If the developer chooses to add universally required custom fields, the fields have default values.
- If an installed package has Restricted API access, upgrades are successful only if the upgraded version does not contain any s-controls. If s-controls are present in the upgraded version, you must change the currently installed package to Unrestricted API access.
- When you upgrade a package, changes to the API access are ignored even if the developer specified them. This behavior ensures that the administrator installing the upgrade has full control. Installers should carefully examine the changes in package access in each upgrade during installation and note all acceptable changes. Then, because those changes are ignored, the admin should manually apply any acceptable changes after installing an upgrade.

#### See Also

- [_ISVforce Guide_: Use Managed Packages to Develop Your AppExchange Solution](https://developer.salesforce.com/docs/atlas.en-us.packagingGuide.meta/packagingGuide/managed_packaging_intro.htm)