Confluence → Sana

Catalog plan outline

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

Migration friendliness

Confluence 6/10 · Sana 5/10

Speed to live

Confluence 5/10 · Sana 6/10

Catalog migration difficulty

Confluence high · Sana 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.
• Sana is not flagged for: synced email and calendar links, installed marketplace apps.
• Confluence is flagged with an open API, which is the export path to test.
• Sana is flagged with an open API for the load.
• Confluence is cataloged as a fit for: Atlassian-standardized orgs.
• Sana is cataloged as a fit for: AI company search plus learning.

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 Sana only after the field map is written down. AI knowledge and learning — the company brain that is not another wiki. Neither product is flagged for custom objects. Keep the object list short.

3. Prove a sample

   Sana scores 6/10 on speed to live and 5/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 Sana. 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 Sana: what the vendor docs actually cover

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

What to export from Confluence

Atlassian's space-export article, reopened 2026-10-17, is the file path if someone insists on taking pages out. A space admin uses More actions, Space settings, General, Export space, and picks PDF, CSV, HTML, or XML. CSV is described as the choice for another Confluence Cloud, XML for Data Center, HTML for a static site, and PDF for a manual. PDF omits blog posts and comments. HTML omits blog posts, and page comments are missing, tracked as CONFCLOUD-57908. Team Calendars stay out. A site admin running CSV or XML exports content that admin could not otherwise see. Organization admins can block exports. A single page export to Word or PDF leaves unpublished edits behind, and Word files are meant to open in Microsoft Word. Timing guidance for about one hundred pages is generally a few minutes. Confluence's price page the same day shows Free at 0 dollars forever for 10 users, Standard at 5.78 dollars per user per month, and Premium at 11.16 dollars per user per month. Enterprise says billed annually and tells you to switch the toggle; that annual figure was not copied. The catalog's free plan and zero starting price match Free. Sana does not need this export if you use the connector below. The file is a fallback, and Sana's guide does not say it accepts the zip.

• Confluence export a space — checked 2026-10-17
• Confluence pricing — checked 2026-10-17

How Sana imports

Sana's centralized Confluence guide, written by Maureen Changawa and dated July 11, 2025, reopened 2026-10-17, is an index of pages in place. It says read is supported and write is not. Indexed content includes spaces and pages. Whiteboard, database, blog, and smart link are not marked supported in the indexed-content table. The asset cap on the Enterprise tier is 50,000. Sync runs once a day for pages and permissions. Setup is three steps even though the intro says two: a Confluence admin approves Sana at admin.atlassian.com by enabling Sana AI (Centralized) and Sana AI (Permissions), a workspace admin clicks Connect centralized and chooses all spaces or a subset, and every user connects Confluence (User Permissions Only) because Atlassian requires each person to consent. You only see pages that are public or shared with you or your group. Folder trees are not shown, but pages inside folders remain reachable. Selecting a space limits the conversation to that space's homepage, not the whole space. The guide says Sana does not train models on the content. Sana's pricing page the same day shows one card, Enterprise, custom pricing, with unlimited members per workspace and unlimited documents per integration, SAML SSO, and SCIM. No dollar and no trial length. The catalog's null price and custom model match. The catalog trial flag does not. Third-party connector availability by tier is a different help article that was not the one used for the field limits above. Pages stay in Confluence. Sana reads them.

• Sana Confluence centralized guide — checked 2026-10-17
• Sana pricing — checked 2026-10-17

Object and field mapping

• A Confluence page is what Sana says it indexes. A blog post is excluded from that indexed-content table, and it is also omitted from PDF and HTML exports.
• A space selection in Sana is not a space export. The guide says choosing a space limits chat to the homepage.
• Permissions are not copied into a Sana ACL you edit. Each user must connect User Permissions Only, and visibility follows Confluence sharing.
• Attachments are in the scope table as content attachments for the OAuth grant. The guide does not say an HTML zip's attachment folders are the ingest path.
• Whiteboards and databases are checked on Confluence's own price table for several plans. Sana's indexed-content table does not mark them supported.
• Comments fail HTML export and are not a Sana indexed type in the table that was read.
• Confluence user prices and Sana's custom enterprise card are different bills. Connecting does not cancel Confluence.

What will not carry over

• Write-back. The centralized guide says creating and updating pages is unsupported.
• Blogs, whiteboards, and databases as indexed content.
• Team Calendars, which the Atlassian export article excludes.
• Unpublished edits on a single-page Word or PDF export.
• A Sana dollar amount.
• A space-file importer. The guide is OAuth and a daily sync.
• Folder hierarchy as a visible tree. Pages inside folders can still be reached.

Cutover checklist

1. Have a Confluence site admin enable both Sana apps, or perform the centralized connect themselves.
2. Choose all spaces or a named subset. Do not assume a space picker searches every page in the space.
3. Require every reader to connect User Permissions Only. Skipping a person means that person cannot see their restricted pages.
4. Count assets against 50,000 on Enterprise before you promise the whole wiki.
5. Expect a daily sync, not a live edit. A page changed this morning may wait.
6. Keep Confluence as the authoring system. Sana will not write the page back.
7. If you also take a zip, use XML or CSV when blogs matter, and do not expect Sana to ingest it. That bridge is not in the guide.
8. Quote Confluence's monthly figures and Sana's custom card separately. Enterprise Confluence annual was not on the monthly view.

Common pitfalls

• Exporting HTML and then asking why comments vanished. Atlassian documents that gap.
• Telling a user the centralized connect already mirrored their permissions. The FAQ says each person must consent.
• Promising whiteboard search because Confluence Premium unlocks unlimited whiteboards. Sana's table does not index them.
• Canceling Confluence seats because Sana is connected. Authoring still happens in Confluence.
• Computing an annual Standard price from 5.78 dollars. The page did not print that annual number.

Related catalog pages

• Best AI-native Confluence alternatives (2026) — Which tool, compared
• What should replace Confluence? — Switch narrative
• Sana product page — AI knowledge and learning — the company brain that is not another wiki.
• Sana vs Confluence — Head-to-head already in the catalog
• Knowledge category — Catalog hub for this category