Import from Obsidian and Notion
Move an existing vault or export into Orcha. Orcha keeps the hierarchy, relations, attachments, and links.
Orcha imports Obsidian vaults and Notion exports as ZIP archives. Use the guided flow in the app under Import. Imports keep the folder hierarchy, relations, attachments, and links.
Prepare the archive
- Obsidian: make a ZIP file of your vault folder.
- Notion: use the Notion export (Markdown and CSV). The export downloads as a ZIP file.
Orcha validates each upload carefully. Orcha rejects an archive that has one of these items:
- Path traversal
- Symlinks
- An expanded size that is too large
- Suspicious compression ratios
- Executable attachment types
Preview first
Each import starts with a dry run.
- Upload the archive.
- Select the destination workspace.
- Choose a conflict policy:
| Policy | Behavior when a matching item already exists |
|---|---|
update | Update the existing item (default) |
skip | Do not change the existing item |
duplicate | Import as a new copy |
The preview report shows the items that the import will create, update, and skip. Before Orcha writes data, the preview examines your plan allowances. It examines total storage, indexed content, the archive size, and the largest attachment in the archive.
On free workspaces, the limit is 25 MB for one attachment and 500 MB for the archive. On paid plans, the limit is 1 GB for each attachment and 5 GB for the archive. If an archive is over a limit, the preview shows the name of the file that causes the problem. You cannot start that import. Thus a large asset causes a failure before the import, and not during the import.
Run, monitor, resume
Start the run from the preview. The Import page shows the progress. If a run
fails or you cancel it, you can resume it. Reruns use stored source IDs,
hashes, and destination hashes. Thus the default update policy does not
overwrite a destination that you edited after the import.
Roll back
You can roll back a run during seven days after the import. A rollback removes imported objects that nobody changed after the import. A rollback does not change items that you edited. You can download the full fidelity and execution report for each run.
Restore an Orcha export
The same page accepts the JSON file from Settings → Export All. Use this file to copy content between Orcha workspaces or to restore a backup.
- Choose Orcha export as the source.
- Upload the file.
This path does not use the migration engine. Thus it is different from the ZIP and API imports above:
- Orcha applies the file immediately when you press Restore.
- There is no preview, no conflict policy, and no rollback window.
- The restore does not show in the import history.
The restore creates the files and folder tree from the export again. It does not change existing content.
After the import
Orcha indexes imported files automatically. You can then search them through retrieval. Orcha stores imported binary attachments as assets and serves them through authorized asset URLs. Image embeds show inline. Embeds of other attachment types (PDFs, spreadsheets, audio) show as download links to the stored asset.