Notion to Confluence Migration

Point this agent at your Notion workspace and your Notion-integrated codebase, and ask it to plan your migration to Confluence.

What it does

A Notion migration has two lanes, and this agent works both:

1. Data lane — the page tree, databases, and attachments move via the Notion API into Confluence spaces through the Confluence REST v2 API.
2. Code lane — internal integrations and bots that hit the Notion API are mapped, planned, and translated to Confluence REST v2 equivalents.

The workflow:

1. Map the workspace (page tree, databases with property types, embeds, synced blocks) and the codebase (Notion SDK call sites, webhooks).
2. Plan space design, hierarchy mapping, database translation per property type, and the permission model mapping.
3. Import content: block→storage-format conversion, batched page creation via REST v2, attachment upload, and a link-rewriting pass once Confluence page IDs exist.
4. Translate integrations: Notion SDK call sites → Confluence REST v2 calls, plus a webhook strategy.
5. Sandbox — import a sample subtree into a test space, verify hierarchy, links, and attachments, and report PASS/PARTIAL/FAIL per check.

Prerequisites

• CONFLUENCE_SITE — your <site>.atlassian.net test site
• CONFLUENCE_EMAIL — the Atlassian account email the API token belongs to
• CONFLUENCE_API_TOKEN — API token for that account
• NOTION_TOKEN — optional; a read-only internal integration token so the agent can export the workspace via the Notion API

Current scope

This solution migrates pages, databases, attachments, and API integrations. It does not migrate synced blocks (no Confluence equivalent), does not auto-translate Notion formulas and rollups (flagged for manual redesign), flattens per-block permissions to page-level restrictions, and migrates comments only partially. Some embed types degrade to plain links.