-
Notifications
You must be signed in to change notification settings - Fork 40
Import
Zeyu Zhao edited this page May 24, 2026
·
5 revisions
Password-Manager can import:
- CSV files
- RAW files exported from the recovery page
Go to:
Settings -> Import
Select a .csv or .raw file and submit.
CSV files must contain a header row.
Required headers:
name,password
The order is not important.
Example:
name,password,user,url,tags,comment
GitHub,example-password,octocat,https://github.com,dev,Main GitHub account
Example,another-password,user@example.com,https://example.com,personal,Rules:
- The CSV file must be UTF-8 encoded.
- Each row creates one entry.
-
namebecomes the account/item name. -
passwordbecomes the saved password. - Other columns are imported only if their header matches one of your additional field keys.
- If a field does not exist in your Password-Manager customized fields, that CSV column is ignored.
RAW files are exported from the recovery page after decrypting a backup.
Recommended flow:
- Generate a backup from the source instance.
- Open the recovery page.
- Unlock the backup.
- Export RAW.
- Log in to the destination instance.
- Go to
Settings -> Import. - Import the
.rawfile.
RAW import is best used with an empty destination account.
CSV export is no longer treated as a normal one-click export flow.
Recommended CSV export flow:
- Generate a backup.
- Open the recovery page.
- Unlock the backup with the login password used when generating it.
- Export CSV from the recovery page.
This design intentionally makes CSV export require the login password again.
CSV and RAW files should be treated as sensitive plaintext-equivalent data.
After importing:
- verify the imported entries
- delete temporary CSV/RAW files
- generate a fresh backup from the destination instance