From 0f6751849337293afbdbaa783ab8db6dd22a8e7b Mon Sep 17 00:00:00 2001
From: thePR0M3TH3AN <53631862+PR0M3TH3AN@users.noreply.github.com>
Date: Sun, 13 Jul 2025 09:26:46 -0400
Subject: [PATCH] docs: describe automatic parent seed migration

---
 README.md                                             | 3 +++
 docs/docs/content/01-getting-started/04-migrations.md | 9 +++++++++
 2 files changed, 12 insertions(+)

diff --git a/README.md b/README.md
index bd26a2e..d4de0c3 100644
--- a/README.md
+++ b/README.md
@@ -215,6 +215,9 @@ The encrypted index file `seedpass_entries_db.json.enc` begins with `schema_vers
 > `seedpass_passwords_db.json.enc` (Fernet) to AES-GCM as
 > `seedpass_entries_db.json.enc`. The original file is kept with a `.fernet`
 > extension.
+> The same migration occurs for a legacy `parent_seed.enc` encrypted with
+> Fernet: it is transparently decrypted, re-encrypted with AES-GCM and the old
+> file saved as `parent_seed.enc.fernet`.
 
 ## Usage
 
diff --git a/docs/docs/content/01-getting-started/04-migrations.md b/docs/docs/content/01-getting-started/04-migrations.md
index 3c9f18e..f6a1ce0 100644
--- a/docs/docs/content/01-getting-started/04-migrations.md
+++ b/docs/docs/content/01-getting-started/04-migrations.md
@@ -36,3 +36,12 @@ is renamed to `seedpass_entries_db_checksum.txt.fernet`.
 
 No additional command is required – simply open your existing vault and the
 conversion happens transparently.
+
+### Parent seed backup migration
+
+If your vault contains a `parent_seed.enc` file that was encrypted with Fernet,
+SeedPass performs a similar upgrade. Upon loading the vault, the application
+decrypts the old file, re‑encrypts it with AES‑GCM, and writes the result back to
+`parent_seed.enc`. The legacy Fernet file is preserved as
+`parent_seed.enc.fernet` so you can revert if needed. No manual steps are
+required – simply unlock your vault and the conversion runs automatically.