You are here:
Experience Cloud Licenses Eligible for Upgrades
In general, you can upgrade from most customer licenses to the Customer Community Plus or Partner Community licenses.
Required Editions
| Available in: Salesforce Classic and Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions |
| Applies to: LWR, Aura, and Visualforce sites |
Specifically, we support license upgrades for all users where their UserType equals CSPLitePortal (in the Salesforce API) to PowerPartner or PowerCustomerSuccess.
You can upgrade the following licenses to the Customer Community Plus or Partner Community licenses.
- Customer Community
- External Identity (enables access to the Salesforce Customer Identity product)
- High Volume Customer Portal
- Overage High Volume Customer Portal
- Authenticated Website User Overage
- Authenticated Website User
There are other customer licenses associated with the CSPLitePortal user type that support license upgrades, but with some loss of
data access. For example, the user can lose access to some objects they previously had
access to, or the new license might not include one or more user permissions available with
the previous license. For example, the Modify All Records and View All Records permissions
aren’t available with Customer Community Plus or Partner Community licenses.
We strongly recommend that you explore what permissions are affected before you upgrade a user’s license. The user’s new license, profile, role, and permission set assignments should provide at least the same or comparable level of data access as previous assignments.
Considerations When Upgrading a User’s License
- Self-registration with a Customer Community license is twice as fast as self-registration using a Customer Community Plus license. If your site requires a large number of users to register at a time, configure self-registration to use micro-batching for Customer Community Plus sites.
- The Customer Community Plus and Partner Community licenses require the user to have a
role, which imposes a few restrictions. We recommend that you use account role
optimization for role-based licenses to help avoid performance and scale issues.
- An upgrade to a license that requires a role is irreversible.
- If the user belongs to an account that doesn’t have roles, we create one for you.
- If the account does have roles and you don’t specify one, we associate the user with the lowest role in the hierarchy: Partner <Account Name> User or Customer <Account Name> User.
- Users can own up to 50,000 person accounts. If more person accounts are needed, create a Person Account Owner Power User. A Person Account Owner Power User can own more than 50,000 accounts.
- Before upgrading a user to the Partner Community license, enable the user’s account as a partner account. A partner account can be associated with both customer and partner users, so customer users on the same account aren’t affected.
- A license upgrade automatically removes sharing sets, permission sets, and permission set license assignments previously associated with the user.
- License upgrades are subject to most limits that apply to new users, such as the maximum number of licenses and roles in your org and username uniqueness requirements.
- Consider the scale of your org when upgrading your license. For example, a Customer Community license can support 100 million users, whereas a Customer Community Plus license can support 10 million.
- Changes in profiles and permission sets can affect site membership. Ensure that upgraded users have access to the intended Experience Cloud sites.
- We recalculate sharing rules that apply to the upgraded user, for example through their public groups, criteria-based sharing, and record ownership (implicit sharing).
- Users upgraded to the Customer Community Plus are automatically associated with the All Customer Portal Users public group. Similarly, users upgraded to the Partner Community licenses are associated with the All Partner Users public group.
License Conversion and Upgrade Compatibility
To upgrade users with other license types, you must deactivate them, create user identities for them, migrate their data over, and associate it with their new user records.



