Moldavite Portability
Use Moldavite's app UI for archive, migration, and export operations. MCP does not expose import, export, restore, or backup tools. Never simulate a destructive replace import with note-by-note MCP writes.
Choose the Right Operation
| Goal |
Operation |
| Portable Forge content archive |
ZIP export |
| Password-protected Forge copy |
Encrypted .moldavite-backup export |
| Add files without overwriting existing paths |
Import with Merge |
| Restore archive contents as primary notes |
Import with Replace |
| Share selected notes |
Markdown, plaintext, or PDF export |
| Move app preferences only |
Settings JSON export/import |
| Move from Obsidian |
Built-in Obsidian importer |
Safe Backup Workflow
- Confirm source Forge and destination outside that Forge.
- Choose encrypted export when archive privacy matters.
- Keep the password separately; Moldavite cannot recover it.
- Verify the output file exists and has plausible nonzero size.
- Test restore into a disposable Forge when backup assurance matters.
- Keep more than one generation before deleting source data.
Forge archives include daily/, weekly/, notes/, templates/, and images/. They exclude app-managed indexes, trash, plugins, and root agent files.
Merge vs Replace
- Merge skips destination files that already exist. It is safer for combining content but does not reconcile two versions of the same path.
- Replace clears destination daily, weekly, note, and image content before extraction. Export a backup first and obtain explicit user confirmation.
- Templates are handled differently from note directories during replacement; review imported templates after restore.
Do not present Replace as an undoable preview. Treat it as destructive even when a separate backup exists.
Obsidian Migration
Use Moldavite's built-in Obsidian importer instead of manually copying a vault. It reads the source without modifying it and creates a new Forge.
The importer:
- preserves YAML frontmatter;
- converts Obsidian
[[target|Display]] aliases to Moldavite [[Display|target]];
- removes heading and block suffixes from wiki-link targets;
- copies referenced local images into
images/ with collision-safe names;
- normalizes supported daily-note filenames;
- skips hidden files,
.obsidian, .trash, symlinks, .canvas, and unreferenced attachments;
- reports unresolved embeds and skipped Canvas files.
After import, review warnings, aliased links, duplicate basenames, daily-note dates, attachment references, and a sample of frontmatter-heavy notes.
See IMPORT-EXPORT.md for scope and limits.
Settings Export Is Separate
Settings JSON does not contain notes, templates, plugin grants, semantic models, indexes, or the MCP write gate. Use a Forge archive for note data and settings JSON only for supported preferences.
1---2name: moldavite-portability3description: Back up, export, restore, and migrate notes with Moldavite, including encrypted backups, ZIP archives, Markdown or PDF exports, settings JSON, and Obsidian vault imports. Use when the user asks about Moldavite backup, migration, import, export, restore, or moving from Obsidian.4license: MIT5---67# Moldavite Portability89Use Moldavite's app UI for archive, migration, and export operations. MCP does not expose import, export, restore, or backup tools. Never simulate a destructive replace import with note-by-note MCP writes.1011## Choose the Right Operation1213| Goal | Operation |14| --- | --- |15| Portable Forge content archive | ZIP export |16| Password-protected Forge copy | Encrypted `.moldavite-backup` export |17| Add files without overwriting existing paths | Import with Merge |18| Restore archive contents as primary notes | Import with Replace |19| Share selected notes | Markdown, plaintext, or PDF export |20| Move app preferences only | Settings JSON export/import |21| Move from Obsidian | Built-in Obsidian importer |2223## Safe Backup Workflow24251. Confirm source Forge and destination outside that Forge.262. Choose encrypted export when archive privacy matters.273. Keep the password separately; Moldavite cannot recover it.284. Verify the output file exists and has plausible nonzero size.295. Test restore into a disposable Forge when backup assurance matters.306. Keep more than one generation before deleting source data.3132Forge archives include `daily/`, `weekly/`, `notes/`, `templates/`, and `images/`. They exclude app-managed indexes, trash, plugins, and root agent files.3334## Merge vs Replace3536- **Merge** skips destination files that already exist. It is safer for combining content but does not reconcile two versions of the same path.37- **Replace** clears destination daily, weekly, note, and image content before extraction. Export a backup first and obtain explicit user confirmation.38- Templates are handled differently from note directories during replacement; review imported templates after restore.3940Do not present Replace as an undoable preview. Treat it as destructive even when a separate backup exists.4142## Obsidian Migration4344Use Moldavite's built-in Obsidian importer instead of manually copying a vault. It reads the source without modifying it and creates a new Forge.4546The importer:4748- preserves YAML frontmatter;49- converts Obsidian `[[target|Display]]` aliases to Moldavite `[[Display|target]]`;50- removes heading and block suffixes from wiki-link targets;51- copies referenced local images into `images/` with collision-safe names;52- normalizes supported daily-note filenames;53- skips hidden files, `.obsidian`, `.trash`, symlinks, `.canvas`, and unreferenced attachments;54- reports unresolved embeds and skipped Canvas files.5556After import, review warnings, aliased links, duplicate basenames, daily-note dates, attachment references, and a sample of frontmatter-heavy notes.5758See [IMPORT-EXPORT.md](references/IMPORT-EXPORT.md) for scope and limits.5960## Settings Export Is Separate6162Settings JSON does not contain notes, templates, plugin grants, semantic models, indexes, or the MCP write gate. Use a Forge archive for note data and settings JSON only for supported preferences.
mauropereiira