Import & export

Import

From Markdown

1. Go to Settings → Import.
2. Drag and drop one or more .md files, or click to browse.
3. Each file becomes a new page. Markdown formatting is converted to native blocks.

Supported: headings, paragraphs, bullet/numbered/todo lists, code fences, blockquotes, bold, italic, and links.

From Notion

1. Export your Notion content as Markdown & CSV from Notion's export settings.
2. Go to AuroraDocs Settings → Import.
3. Drag in the exported .zip file.
4. Pages and databases are imported as native AuroraDocs objects.

TIP

Notion's export doesn't include embedded images. Inline images will be converted to links pointing to Notion's CDN.

Export

Single page — Markdown

1. Open the page.
2. Click ··· (page menu) → Export → Markdown.
3. A .md file downloads to your device.

Single page — JSON

1. Open the page.
2. Click ··· (page menu) → Export → JSON.
3. A .json file downloads containing the raw block structure.

Readable exports and E2EE

Markdown and HTML exports are readable plaintext. If the workspace is encrypted, Aurora blocks readable export until the workspace is unlocked and warns before creating files outside Aurora's encryption boundary.

Inline databases, linked databases, inline task blocks, and inline collections export as best-effort static snapshots. Some Aurora-native structures may still be represented as fallbacks rather than full-fidelity editable content.

Full workspace — ZIP

1. Go to Settings → Export.
2. Click Export workspace.
3. A .zip file downloads containing all pages as Markdown files and all databases as CSV files.

TIP

Workspace ZIP export is a great way to back up your data or move to another tool. The Markdown files are plain text you can open in any editor.

AuroraBak backups

AuroraBak files (.aurorabak and .aurorabak-bundle) are AuroraDocs' native backup and restore format. They preserve the workspace structure, object data, workspace settings, and bundled media needed for an Aurora restore.

Encrypted workspace backups stay encrypted. AuroraBak does not turn encrypted workspaces into readable plaintext during backup creation. Restore requires the same account password, recovery phrase, or other E2EE key material that normally unlocks the workspace.

Encrypted AuroraBak files can be restored into their original workspace identity. Creating a new workspace from an encrypted AuroraBak is blocked until Aurora can re-wrap the encrypted workspace key for that new workspace.

Use Markdown or HTML export when you intentionally want a readable plaintext copy of an unlocked encrypted workspace.

Clean Markdown local folders

Clean Markdown is a Local folders mode, not the same thing as one-time export. Keep mirrored writes readable Markdown out of Aurora; Clean sync also imports supported Markdown body edits back into Aurora for enrolled workspaces.

See Sync & storage.

File attachments

Files attached to pages are stored in the active workspace storage path: local folder storage for folder-backed workspaces, AuroraCloud object storage for cloud workspaces, and encrypted storage when E2EE covers the file path. They are included when the export path supports them.

Download individual attachments by clicking the file block in the editor.