Importing from exported Bitwarden JSON wipes out categories #1961

Closed
opened 2025-10-09 17:39:09 +03:00 by OVERLORD · 5 comments
Owner

Originally created by @hank on GitHub.

I had nicely categorized logins from Lastpass and after exporting and re-importing into another instance those were gone. I assume they weren't carried with the exported data. Please allow export and import of these. Thanks!

Originally created by @hank on GitHub. I had nicely categorized logins from Lastpass and after exporting and re-importing into another instance those were gone. I assume they weren't carried with the exported data. Please allow export and import of these. Thanks!
Author
Owner

@hank commented on GitHub:

... and now I realized that it also doesn't seem to import categories! So all the categorized logins are actually GONE COMPLETELY. Good thing I have the original instance around as a backup.

@hank commented on GitHub: ... and now I realized that it also doesn't seem to import categories! So all the categorized logins are actually GONE COMPLETELY. Good thing I have the original instance around as a backup.
Author
Owner

@mprasil commented on GitHub:

When you say categories, do you mean collections? Because collections are in organization and user-side export does not contain organization passwords. For that you need to do the export in the organization interface.

@mprasil commented on GitHub: When you say categories, do you mean collections? Because collections are in organization and user-side export does not contain organization passwords. For that you need to do the export in the organization interface.
Author
Owner

@hank commented on GitHub:

A workaround for now is to just copy the old bitwarden data directory from the old container (mprasil/bitwarden) to the new bind mount for the bitwardenrs/server container and start it up. It seems to work just fine with the old database and everything shows up nicely.

If you want to actually back up your data for safe keeping, make sure you're saving off the sqlite database itself.

@hank commented on GitHub: A workaround for now is to just copy the old bitwarden data directory from the old container (mprasil/bitwarden) to the new bind mount for the bitwardenrs/server container and start it up. It seems to work just fine with the old database and everything shows up nicely. If you want to actually back up your data for safe keeping, make sure you're saving off the sqlite database itself.
Author
Owner

@mprasil commented on GitHub:

I'm closing this as there is no response, but feel free to reopen if you need more help with this.

@mprasil commented on GitHub: I'm closing this as there is no response, but feel free to reopen if you need more help with this.
Author
Owner

@hank commented on GitHub:

Just tried exporting CSV, and it appears to lack all categorized logins.

@hank commented on GitHub: Just tried exporting CSV, and it appears to lack all categorized logins.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#1961