Migrate to the Next-Generation SharePoint Connector Updated May 04, 2026 15:18 Microsoft retired the SharePoint Add-In model on April 2, 2026. This means our legacy SharePoint Connector no longer syncs asset updates from SharePoint to Showpad. To keep your SharePoint content syncing smoothly with Showpad and to continue receiving support, you’ll need to move to the Next-Generation SharePoint Connector. Note: This migration is no longer fully self-service. It now requires coordination between your Showpad admin, your SharePoint admin, and Showpad Support. We recommend completing the migration as soon as possible so your assets will continue to sync to Showpad. What’s changed? The legacy SharePoint Connector integration stopped working on April 2, 2026. The Next-Generation SharePoint Connector is a Showpad App and not impacted by this Microsoft change. Asset and tag icons will look different after migration:Migrated assets will continue to display the SharePoint icon: Text-based tag fields: In the legacy SharePoint Connector, when the SharePoint column selected is a text-based field, the tags are automatically separated on : and ; delimeters. For migrations, this is handled automatically, but to achieve the same results in new connections, you'll need to set up : and ; delimiters when mapping attributes. What you need to do Your next steps depend on which SharePoint Connector you’re currently using. If you’re: Already using the Next-Generation SharePoint Connector exclusively: You don’t need to do anything; you can continue using it as is. Still using the Legacy SharePoint Connector: You’ll need to complete the migration to the Next-Generation SharePoint Connector. Using both the legacy SharePoint Connector and the Next-Generation SharePoint Connector: You’ll need to migrate all connections that are on the legacy connector. Before you beginMake sure you have the following: Permissions: Administrator Prerequisites: Showpad Apps access Administrator access to the SharePoint Online site and document library you want to migrate. Microsoft Entra role: (Application Administrator, Cloud Application Administrator, Global Administrator, or a custom role that allows the management of app registrations) PowerShell 7.4.0 or later The PnP PowerShell module installed Next-Generation SharePoint Connector installed At least one SharePoint Online instance Documents available in SharePoint Step 1: Initiate the migration in Showpad Before any scripts are run, your Showpad Admin must prepare the migration in Showpad. Log in to Showpad as an Administrator Go to Settings > Showpad Apps > SharePoint > Connections > Migrate connections. If the SharePoint app is not yet installed, follow these instructions to install and authorize the app. Find the SharePoint site or document library you want to migrate. Select Prepare Migration. Confirm that the Connection status changes to Migration Initiated. At this point, Showpad is ready for the next step, but the migration is not yet complete. Step 2: Generate the migration mapping file This step must be completed by your SharePoint Admin. The SharePoint Admin needs to run the ExportIds.ps1 script for the SharePoint site and document library being migrated. You can download the export asset IDs script from the bottom of this article. The script generates a CSV file that Showpad Support uses to complete the migration. 2.1. Prepare the environment Open PowerShell and verify the version: $PSVersionTable.PSVersion If you are using PowerShell 7.4.0 or later, install the PnP PowerShell module: Install-Module -Name "PnP.PowerShell" 2.2. Run the Export Asset IDs script Download the ExportIds.ps1 script and run it with the following parameters: SharePoint Site URL: The full URL of the SharePoint site being migrated. Document Library Name: The name of the document library being migrated. Output File Name: The name of the CSV file to generate. Example: .\ExportIds.ps1 -SiteUrl "https://yourcompany.sharepoint.com/sites/marketing" -LibraryName "Documents" -OutputFileName "Marketing_Docs_Migration.csv" 2.3. Verify the output GUID: The current external ID tied to the asset in Showpad. FileLeaf: The filename. AssetId: The new external ID required for migration. Make sure the CSV file is generated successfully before moving on. Step 3: Submit the file to Showpad Support After you generate the CSV file, send it to Showpad Support to complete the migration. You can contact Support by clicking the Help button below. Open a new support ticket or reply in your existing migration thread. Attach the CSV file created in Step 2. Include the following details for each CSV file: SharePoint Site ID Document Library ID Showpad Support will then use the file to complete the migration. What happens next? After Showpad Support completes the migration: Your legacy SharePoint connection is migrated to the Next-Generation SharePoint Connector Your assets remain in Showpad Syncing can continue through the new connector setup FAQs Question Response Do I still need to migrate if I already use the Next-Generation SharePoint Connector? No. Only legacy SharePoint Connector connections need to be migrated. Can I still migrate everything myself? No. The process requires support from Showpad and is no longer fully self-service. What happens if I do not migrate? Your assets remain in Showpad, but updates from SharePoint no longer sync through the legacy connector. Does migration change my files? Assets remain unchanged except for an updated External ID to align with the new system. Export asset IDs script ExportIds.zip 3 KB Download Related articles Install the Next-Generation SharePoint Connector Migrate to the Next-Generation SharePoint Connector Sync assets using AEM Install and share content with Showpad for Outlook 365 Invite people to Shared Spaces