Monica full db import

[sebastian-c]

Description / 功能描述

Full database import of a Monica set up. Monica can provide a db dump which could be imported by Bonds.

Motivation / 动机

While the existing json import is great (#72), it doesn't allow imports of user accounts and images.

Proposed Solution / 建议方案

When starting up for the first time or in the advanced options, it should be possible to do a full import to replace existing data.

Alternatives Considered / 备选方案

User accounts can probably be done manually, but images are a real pain

Additional Context / 补充信息

No response

[naiba]

Thanks for raising this. I want to push back a bit on the "full DB dump import" framing and clarify the current state, because I think the real pain point can be solved more safely.

On importing a Monica DB dump directly: I'd rather not go this route. Bonds has its own schema (Go + GORM), completely unrelated to Monica's Laravel/MySQL tables. A DB-dump importer would mean re-deriving the full table→table mapping that we already maintain for the JSON path (server/internal/services/monica_import.go), but more fragile — it would break whenever Monica changes a table, and it'd be pinned to a specific Monica DB version. The "replace existing data on startup" idea is also risky on a multi-tenant (Account / Vault / User) instance.

On images: the current JSON import already imports photos and documents. Monica's official JSON export embeds the binary as base64 dataUrl inside the photos/documents collections, and we decode them to the filesystem and even set the first photo as the contact avatar (importPhotos / importDocuments in monica_import.go). So images shouldn't be lost via JSON — could you confirm which Monica version / export you used? If your export didn't contain embedded photos, that's the bug we should chase, possibly by also accepting Monica's storage/ directory alongside the JSON.

On user accounts: I'd intentionally keep these out of any importer. Password hashes, 2FA/passkey/OAuth bindings don't migrate cleanly across systems, and importing them is a security risk. Bonds already has User Invitations with permission levels — recreating accounts that way is the safer path, and we can document it as part of a migration guide.

So my proposal: rather than a DB-dump importer, let's (1) verify photo import actually works end-to-end on a real Monica export, (2) if needed, extend the JSON importer to also ingest a Monica storage/ folder, and (3) document account migration via invitations. Could you share details on the export you tried so we can confirm whether photos are really being dropped?

---

关于"整库 DB dump 导入":不建议走这条路。Bonds 的 schema 与 Monica 完全不同，DB dump 导入需要重写一套更脆弱的表映射，且会绑定 Monica 具体版本；"启动时整库替换"在多租户实例上风险很高。关于图片：现有 JSON 导入已经支持照片和文档（Monica 官方 JSON export 内嵌 base64，我们会解码落盘并设头像），所以图片不应丢失——能否确认你用的 Monica 版本/导出方式？关于账号：密码哈希、2FA/passkey/OAuth 绑定无法安全跨系统迁移，建议用现有的 User Invitations 重建账号。