Cannot import organisation: Bitwarden Encrypted JSON is rejected - "Nothing was imported" #793

New Issue

OVERLORD · 2025-10-09T16:51:48+03:00

OVERLORD commented

2025-10-09 16:51:48 +03:00

Originally created by @thxrben on GitHub.

Unable to import a Bitwarden Encrypted JSON

I have recently turned off my old Bitwarden host. It also used Vaultwarden in a docker container.
I exported my personal passwords and the organisation I had setup both seperately via the "Bitwarden Encrypted JSON" option.

While my personal space was able to import just fine, the organisation does not import and just throws "Es wurde nichts importiert." ("Nothing was imported.").

I tried it on my personal space, and with an organisation with the same name.

Deployment environment

vaultwarden version: 1.28.1

Install method: Docker (vaultwarden:/latest)
Clients used: Web Vault
Reverse proxy and version: Apache/2.4.56 (Debian)
MySQL/MariaDB or PostgreSQL version: None
Other relevant details:

Steps to reproduce

Vaultwarden is started via docker compose
Logged in via mail/password followed by 2FA Auth code (Authy, using regular 2FA codes)
Went to Organisation -> Import Data (Not sure about translation here)
Choosing "Bitwarden (json)
Selecting File
Clicking "Import Data"
Acknowledging the warning about importing data into an organisation
Typing in the export password
Notification about an import error: "Nothing was imported" (Original: "Es wurde nichts importiert.")

Expected behaviour

Successfull import of passwords into Vaultwarden

Actual behaviour

Notification about an error which is non descriptive

Troubleshooting steps

I took a look inside the json and there is no issues with the formatting or similar. All characters are escaped if necessary and the format is correct.

The export looks like it did not export everything (e.g. the "data" portion is relatively small for at least 15-20 passwords).

Importing via the Textbox underneath the "upload file" button also resulted in the same error.

The password I entered is correct. Upon entering a wrong password, Bitwarden complains about a wrong export password being supplied.

Troubleshooting data

None - (e.g. no error in the logs when running via "docker compose up" without detaching)
https://hastebin.skyra.pw/cabocuwivo.yaml

Originally created by @thxrben on GitHub. ### Unable to import a Bitwarden Encrypted JSON I have recently turned off my old Bitwarden host. It also used Vaultwarden in a docker container. I exported my personal passwords and the organisation I had setup both seperately via the "Bitwarden Encrypted JSON" option. While my personal space was able to import just fine, the organisation does not import and just throws "Es wurde nichts importiert." ("Nothing was imported."). I tried it on my personal space, and with an organisation with the same name. ### Deployment environment  * vaultwarden version: 1.28.1  * Install method: Docker (vaultwarden:/latest) * Clients used: Web Vault * Reverse proxy and version: Apache/2.4.56 (Debian) * MySQL/MariaDB or PostgreSQL version: None * Other relevant details: ### Steps to reproduce Vaultwarden is started via docker compose Logged in via mail/password followed by 2FA Auth code (Authy, using regular 2FA codes) Went to Organisation -> Import Data (Not sure about translation here) Choosing "Bitwarden (json) Selecting File Clicking "Import Data" Acknowledging the warning about importing data into an organisation Typing in the export password Notification about an import error: "Nothing was imported" (Original: "Es wurde nichts importiert.") ### Expected behaviour Successfull import of passwords into Vaultwarden ### Actual behaviour Notification about an error which is non descriptive ### Troubleshooting steps I took a look inside the json and there is no issues with the formatting or similar. All characters are escaped if necessary and the format is correct. The export looks like it did not export everything (e.g. the "data" portion is relatively small for at least 15-20 passwords). Importing via the Textbox underneath the "upload file" button also resulted in the same error. The password I entered is correct. Upon entering a wrong password, Bitwarden complains about a wrong export password being supplied. ### Troubleshooting data None - (e.g. no error in the logs when running via "docker compose up" without detaching) https://hastebin.skyra.pw/cabocuwivo.yaml

OVERLORD closed this issue

2025-10-09 16:51:49 +03:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/vaultwarden#793