SharePoint → Glean

Catalog plan outline

General guidance from the Afterstack catalog for SharePoint → Glean. Not SharePoint or Glean vendor documentation.

Migration friendliness

SharePoint 5/10 · Glean 4/10

Speed to live

SharePoint 3/10 · Glean 5/10

Catalog migration difficulty

SharePoint high · Glean medium

Data to export from SharePoint

• synced email and calendar links
• workflow rules
• saved reports
• installed marketplace apps
• AI assistant configuration
• records for the catalog use cases: files, wiki

How the catalogs differ

• Neither product is flagged for custom objects. Keep the object list short.
• Glean is not flagged for: installed marketplace apps.
• SharePoint is flagged with an open API, which is the export path to test.
• Glean is flagged with an open API for the load.
• SharePoint is cataloged as a fit for: Microsoft 365 enterprises.
• Glean is cataloged as a fit for: Companies whose knowledge is scattered across many SaaS apps.

Phases

1. Export

   Take SharePoint as the source of truth for this pair. Export synced email and calendar links; workflow rules; saved reports; installed marketplace apps; AI assistant configuration; records for the catalog use cases: files, wiki. Microsoft’s knowledge incumbent — libraries, intranet, and 365 gravity.

2. Map

   Load into Glean only after the field map is written down. AI search and assistants across the tools you already pay for. Neither product is flagged for custom objects. Keep the object list short.

3. Prove a sample

   Glean scores 5/10 on speed to live and 4/10 on migration friendliness. Run one sample load and one report the team already uses in SharePoint before a full cutover.

4. Cut over

   SharePoint scores 5/10 on migration friendliness and is marked high difficulty in the catalog. Keep SharePoint readable until the team is working in Glean. SharePoint is where enterprise files and intranet pages go to become a permission maze. Copilot sits on top of 365. Teams leave the ‘find anything’ job for Glean-class AI search while still keeping SharePoint as a system of record.

SharePoint to Glean: what the vendor docs actually cover

Linked sentences come from vendor documentation opened for this page. Everything else is general guidance, not SharePoint or Glean vendor documentation. This section does not move data and does not change the catalog outline above.

What to export from SharePoint

The file-download API on Microsoft Graph is the only SharePoint export procedure opened for this pair, and it is the wrong mental model for Glean. GET content on a drive item returns 302 to a short-lived URL, and only objects that have a file facet qualify. Delegated work accounts can use Files.Read. Application permissions start at Files.Read.All. JavaScript clients are told to read the downloadUrl property instead of following /content, because CORS rejects the redirect when an Authorization header is present. Partial bytes use a Range header on the download URL and may come back as 206. That machinery moves bytes out of a library. Glean's connector page does not ask you to do it. Microsoft's business price page prints Business Premium with Copilot at 32 dollars per user per month on annual billing and names SharePoint in the app list. A one-month trial is in footnote 2. There is still no SharePoint-only sticker, which is why the catalog starting price stays empty. The catalog note, updated 2026-10-19, records this $32 with-Copilot card and the separate $21 add-on, and it still stores no SharePoint-only starting price.

• Microsoft Graph download driveItem — checked 2026-10-17
• Microsoft 365 business plans and pricing — checked 2026-10-17

How Glean imports

Glean's SharePoint connector document, last updated September 21, 2026 and opened 2026-10-17, says the connector indexes sites, pages, document libraries, files, and lists, scoped to each user's permissions. Authentication is a certificate with application permissions. The required scope it prints is Sites.FullControl.All on both Graph and SharePoint REST. The parent connector is Microsoft 365. Two setups exist. Deployments created on or after August 14, 2026 use a new setup in the Admin console and do not prepare an app registration. Older deployments configure the Microsoft 365 parent app registration. Real-time search fetches from SharePoint at query time and stores nothing in the index; it is on by default in the new setup and must be enabled by an admin on the previous setup. Read and write tools act as the user. Crawl scope can be limited with greenlists, redlists, and draft exclusions. Glean's pricing URL the same day is a demo page. It lists SharePoint in a row with Slack, Google Drive, Jira, Confluence, GitHub, and Salesforce, and it prints no fee. Marketing figures on that page are not repeated here. No public price, checked 2026-10-17. The catalog's custom model matches. A trial is not stated, so the catalog trial flag is unverified. Content stays in SharePoint. Glean crawls it. A separate core-suite pricing doc describes connectors as included in a seat fee and does not print a dollar on the page that was opened, so no seat price is quoted from it.

• Glean SharePoint connector — checked 2026-10-17
• Glean pricing — checked 2026-10-17

Object and field mapping

• Sites, pages, libraries, files, and lists are the indexed set Glean names. Graph's download API only covers the file facet. Lists and pages are in Glean's sentence and not in a download.
• Sites.FullControl.All is the scope Glean asks for. Files.Read is the least privilege for a one-file download. They are not interchangeable.
• Identity is enforced at query time on Glean's page. A downloaded file has no remaining SharePoint ACL once it sits on a laptop.
• The August 14, 2026 cutover changes setup, not the index definition. Old tenants do not run a migration to the new setup. The choose-your-setup page says connectors already configured keep crawling.
• Real-time search is a live fetch with nothing stored. Indexed search is the crawl. Turning one off does not delete SharePoint.
• Greenlists and redlists are crawl filters. They are not a field map from a Graph item id.
• Microsoft 365 seats and a Glean quote are separate. Connecting does not retire the library.

What will not carry over

• A file dump as the Glean onboarding path. The connector page does not mention one.
• A Glean dollar amount. The pricing URL is a demo.
• SharePoint itself. The index points at content that remains in Microsoft 365.
• A requirement to rebuild the app registration if the tenant was created before August 14, 2026.
• Drafts you redlist. The overview says draft exclusions exist.
• Permission for people who cannot open the item in SharePoint. Enforcement is at query time.
• Marketing statistics printed on the Glean demo page.

Cutover checklist

1. Decide whether the Glean tenant was created on or after August 14, 2026. That date picks the setup, not the SharePoint content.
2. Grant Sites.FullControl.All on Graph and on SharePoint REST if you are on the previous setup. The overview calls that the required scope.
3. Leave the libraries where they are. Do not run a Graph download as the migration.
4. Set greenlists or redlists before the first crawl if a sensitive site must stay out.
5. Turn on real-time search only if you are on the previous setup and an admin still needs always-live results. New setups include it.
6. Keep Microsoft 365 licensed. People who open SharePoint directly still need it, and Glean's permission check depends on those rights.
7. Quote the 32-dollar Copilot bundle as a Microsoft bill, and quote Glean as a demo. Do not add the numbers.
8. Skip the demo-page adoption figures when you brief finance.

Common pitfalls

• Downloading the corpus because an export API exists. Glean's page is a crawl.
• Granting only Files.Read because that is least privilege for Graph downloads. Glean prints a different scope.
• Scheduling a migration project for tenants created before the cutover. The setup page says there is nothing to migrate.
• Deleting SharePoint after the first successful query. The content was never copied out.
• Repeating token and hour claims from the pricing URL. They are not connector facts.

Related catalog pages

• What should replace SharePoint? — Switch narrative
• Glean product page — AI search and assistants across the tools you already pay for.
• Glean vs SharePoint — Head-to-head already in the catalog
• Knowledge category — Catalog hub for this category