--- title: "Upgrade ScreenMeet for Salesforce to the 2GP Managed Package" slug: "upgrade-screenmeet-for-salesforce-to-the-2gp-managed-package" description: "Migrate ScreenMeet for Salesforce from 1GP to 2GP by upgrading to version 1.28, installing the 2GP package, and verifying your org." tags: ["Salesforce 2GP", "Managed Package Migration", "ScreenMeet Salesforce"] updated: 2026-11-02T19:19:55Z published: 2026-11-02T19:19:55Z canonical: "docs.screenmeet.com/upgrade-screenmeet-for-salesforce-to-the-2gp-managed-package" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.screenmeet.com/llms.txt > Use this file to discover all available pages before exploring further. # Upgrade ScreenMeet for Salesforce to the 2GP Managed Package ### Overview ScreenMeet for Salesforce is moving from a first-generation (1GP) managed package to a second-generation (2GP) managed package. Starting with version 1.29, ScreenMeet is released as a 2GP managed package only, so every org must complete this migration to receive version 1.29 and later. The migration is a two-step process. You first upgrade to transition version 1.28, then install the same version 1.28 in 2GP format. Both packages contain identical functionality; only the packaging method differs. This article is for Salesforce administrators who manage the ScreenMeet package in production or sandbox orgs. --- ### Prerequisites - Salesforce System Administrator access to the target org. - An existing ScreenMeet for Salesforce installation. Check your current version under **Setup** > **Installed Packages**. - A sandbox org to test the migration before you upgrade production. Test in a Sandbox First Complete both steps in a sandbox and confirm ScreenMeet works as expected before you repeat the process in production. --- ### Install Links by Environment Use the link that matches your Salesforce environment. Production and Developer Edition orgs use `login.salesforce.com`. Sandbox orgs use `test.salesforce.com`. | Step | Package | Production / Non-Sandbox | Sandbox | | --- | --- | --- | --- | | 1 | Transition version 1.28 (1GP) | [Install 1.28 transition package in production](https://login.salesforce.com/packaging/installPackage.apexp?p0=04tal000007Brkx) | [Install 1.28 transition package in sandbox](https://test.salesforce.com/packaging/installPackage.apexp?p0=04tal000007Brkx) | | 2 | Version 1.28 (2GP) | [Install 1.28 2GP package in production](https://login.salesforce.com/packaging/installPackage.apexp?p0=04tRo0000017W0zIAE) | [Install 1.28 2GP package in sandbox](https://test.salesforce.com/packaging/installPackage.apexp?p0=04tRo0000017W0zIAE) | #### Install Directly in a Logged-In Org To skip the Salesforce login prompt and guarantee the package installs in the correct org, log in to the target org first. Then append the install path to your org's instance URL. For the step 1 transition package, append: ```plaintext /packaging/installPackage.apexp?p0=04tal000007Brkx ``` For the step 2 2GP package, append: ```plaintext /packaging/installPackage.apexp?p0=04tRo0000017W0zIAE ``` For example, an org with the instance URL `https://yourorg.my.salesforce.com` uses the following step 1 URL: ```plaintext https://yourorg.my.salesforce.com/packaging/installPackage.apexp?p0=04tal000007Brkx ``` --- ### Step 1: Upgrade to Transition Version 1.28 Salesforce only migrates an org to a 2GP package when the installed 1GP version matches the 2GP version exactly. Upgrading to transition version 1.28 aligns your org with the 2GP release. 1. Open the step 1 install link for your environment from the table above, or use the instance URL method. 2. Log in to the target org if prompted. 3. Select **Install for Admins Only**. 4. Click **Upgrade** and wait for the installation to complete. 5. Go to **Setup** > **Installed Packages** and confirm ScreenMeet shows version `1.28` with **Packaging Model** `1GP`. If Your Org Is Already on 1.28 If your org already runs the transition build, Salesforce offers an upgrade from 1.28 to 1.28. Running it is safe. If Salesforce reports that the upgrade is taking a long time, click **Done** and wait for the completion email before you start step 2. Complete Step 1 Before Step 2 Do not install the 2GP package until your org is on transition version 1.28. Skipping step 1 prevents the 2GP package from replacing the existing installation. --- ### Step 2: Install Version 1.28 in 2GP Format This step migrates your existing installation to the 2GP managed package. Salesforce shows this as a package migration rather than an upgrade. Your installed components and existing ScreenMeet data remain unchanged. 1. Open the step 2 install link for your environment from the table above, or use the instance URL method. 2. Log in to the same org you upgraded in step 1 if prompted. 3. On the **Migrate remote_support** page, confirm the installed version and the migration target are both 1.28, then click **Migrate**. No profile selection is shown because the existing access settings are kept. 4. When the **Approve Third-Party Access** dialog appears, select **Yes, grant access to these third-party web sites** and click **Continue**. 5. Wait for the **Migration Complete!** message, then click **Done**. Future Upgrades After this migration, your org receives ScreenMeet version 1.29 and later as 2GP releases. Orgs that remain on the 1GP package cannot upgrade past version 1.28. --- ### Verification 1. Go to **Setup** > **Installed Packages**. On the `remote_support` row, confirm **Version Number** shows `1.28` and **Packaging Model** shows `2GP`. The namespace prefix stays `screenmeet`. 2. Open a Case or other record where the ScreenMeet component is configured and confirm the component loads with its session options and start button. 3. Start a test ScreenMeet session, confirm the session code and link are generated, then end the session. 4. Confirm existing ScreenMeet session records and recordings on the record are still visible. --- ## Related - [Upgrading ScreenMeet for Salesforce](/upgrading-screenmeet-for-salesforce.md) - [Upgrading to ScreenMeet for Salesforce v1.27: Migrating Away from Username-Password Authentication](/upgrading-to-screenmeet-for-salesforce-v127-migrating-away-from-username-passwor.md)