Confluence → Glean

Catalog plan outline

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

Migration friendliness

Confluence 6/10 · Glean 4/10

Speed to live

Confluence 5/10 · Glean 5/10

Catalog migration difficulty

Confluence high · Glean medium

Data to export from Confluence

• synced email and calendar links
• workflow rules
• saved reports
• installed marketplace apps
• AI assistant configuration
• records for the catalog use cases: 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.
• Confluence is flagged with an open API, which is the export path to test.
• Glean is flagged with an open API for the load.
• Confluence is cataloged as a fit for: Atlassian-standardized orgs.
• Glean is cataloged as a fit for: Companies whose knowledge is scattered across many SaaS apps.

Phases

1. Export

   Take Confluence 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: wiki. The wiki incumbent every team meant to keep current.

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 Confluence before a full cutover.

4. Cut over

   Confluence scores 6/10 on migration friendliness and is marked high difficulty in the catalog. Keep Confluence readable until the team is working in Glean. Confluence is Atlassian’s knowledge base: spaces, permissions, and the graveyard of stale pages. AI (Rovo and friends) is arriving on a wiki that already lost the search war for many orgs. This is the incumbent Glean-class tools replace.

Confluence to Glean: what the vendor docs actually cover

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

What to export from Confluence

Atlassian's Confluence Cloud export article is the source side of this pair. A space administrator exports from Space settings, then General, then Export space, and the formats are PDF, CSV, HTML, and XML. The article calls CSV the best choice for another Confluence Cloud, XML the choice for Data Center, HTML the choice for a static site, and PDF the choice for a manual. PDF drops blog posts and comments. HTML drops blog posts, and page comments are missing from HTML, tracked as CONFCLOUD-57908. Team Calendars stay out. An organization admin can forbid exports. People receive only content they can already see, unless the exporter is a site admin running CSV or XML, which includes content that admin could not otherwise open. A Word download is meant to open in Microsoft Word. A single page leaves unpublished edits behind. Atlassian's own timing guidance for a space of about one hundred pages is generally a few minutes. Confluence's price page, same day, shows Free at zero dollars forever, Standard at five dollars and forty-two cents per user per month, and Premium at ten dollars and forty-four cents per user per month, on the monthly toggle that was captured. Enterprise's annual figure was behind the other toggle and was not copied. A banner says save up to seventeen percent. That banner is not an annual Standard price. Free allows ten users. The catalog's free plan matches Free.

• Confluence export content — checked 2026-10-12
• Confluence pricing — checked 2026-10-12

How Glean imports

Glean's pricing URL loaded a marketing page with a demo call to action, not a price table and not an import specification. The page lists Confluence in a row of connectors that also names Slack, Google Drive, Jira, SharePoint, GitHub, and Salesforce. A connector is not a description of how a space XML, HTML tree, or PDF manual is ingested. No dollar was printed, which matches the catalog's custom model and null starting price. Adoption statistics, hour-saved claims, and customer quotations on that marketing page are omitted here. Nothing in the loaded page says Glean will accept the four export formats Atlassian documents. The object match below is general guidance.

• Glean pricing — checked 2026-10-12

Object and field mapping

• A Confluence page is the conceptual document Glean might index if a connector is later configured. The marketing page does not describe the index fields.
• Blog posts survive a CSV or XML choice more honestly than a PDF or HTML choice, because those two formats omit them. Glean is not said to prefer one.
• Comments are in even worse shape: PDF omits them, and HTML omits page comments. Do not promise comment search in Glean from an HTML export.
• Attachments and permissions are not a column list in the export article's format summary. A connector that respects permissions is a Glean marketing claim this page does not restate as an import guarantee.
• Space CSV aimed at another Confluence Cloud is the wrong mental model for Glean. The article's 'best for' line is about Confluence, not about an AI search vendor.
• User accounts on Standard or Premium are a Confluence bill. They are not Glean seats. Glean did not print a seat price.

What will not carry over

• Team Calendars.
• Blog posts and comments inside PDF.
• Blog posts, and page comments, inside HTML.
• Unpublished single-page edits.
• A Glean price.
• A documented space-file import. The page that loaded is a connector list and a demo.
• Marketing statistics from the Glean page.

Cutover checklist

1. Confirm the exporter is a space admin, and that an org admin has not blocked export.
2. Choose XML or CSV if blog posts matter. Do not choose PDF for that purpose.
3. Expect HTML to lack page comments.
4. Use a site-admin CSV or XML only when hidden content must be included, and treat that as a privilege decision.
5. Read Glean's loaded page as a connector advertisement. Do not attach the export file to a button that was not documented.
6. Quote Confluence's monthly-toggle prices and say Enterprise annual was not captured.
7. Leave Glean's commercial terms as a demo. The catalog already says custom.
8. Keep Confluence up until someone with Glean access can show the same page title in search, by whatever method Glean actually sells. That method was not in the pricing URL.

Common pitfalls

• Equating the word Confluence on Glean's connector row with an XML upload.
• Exporting HTML and then filing a bug because comments vanished. The article predicts that.
• Computing an annual Standard price from $5.42 and the seventeen-percent banner.
• Repeating Glean's hour and adoption figures. They are not migration facts.
• Assuming a hundred-page space always finishes in minutes. That timing is Atlassian's general guidance, not a contract.

Related catalog pages

• Best AI-native Confluence alternatives (2026) — Which tool, compared
• What should replace Confluence? — Switch narrative
• Glean product page — AI search and assistants across the tools you already pay for.
• Glean vs Confluence — Head-to-head already in the catalog
• Knowledge category — Catalog hub for this category