[GH-ISSUE #2092] Dates not imported from 1Password correctly. #1155

New issue

Closed

opened 2026-03-03 02:06:42 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 02:06:42 +03:00

Owner

Originally created by @EmnaX on GitHub (Nov 9, 2021).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2092

Hello,
I have recently moved over to Vaultwarden from 1Password. I exported my 1Password vaults as 1Password Interchange Format (.1pif) but when I import them into Vaultwarden, the date fields are shown as a long number instead of a date. For example:

Date in 1Password: 2021-11-09
Date in Vaultwarden: 1636482973

Here are the versions for both:
1Password: 7.9.1 (70901007)
Vaultwarden: 2.23.0 (Bitwarden)

Originally created by @EmnaX on GitHub (Nov 9, 2021). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2092 Hello, I have recently moved over to Vaultwarden from 1Password. I exported my 1Password vaults as 1Password Interchange Format (.1pif) but when I import them into Vaultwarden, the date fields are shown as a long number instead of a date. For example: Date in 1Password: 2021-11-09 Date in Vaultwarden: 1636482973 Here are the versions for both: 1Password: 7.9.1 (70901007) Vaultwarden: 2.23.0 (Bitwarden)

kerem closed this issue

2026-03-03 02:06:42 +03:00

kerem commented

2026-03-03 02:06:43 +03:00

Author

Owner

@BlackDex commented on GitHub (Nov 9, 2021):

Processing of the imports are done by the client, in this case the web-vault. Vaultwarden only stores the information it gets, which is all encrypted. This would probably be best to report at Bitwarden. But i think that is already the case.

@BlackDex commented on GitHub (Nov 9, 2021): Processing of the imports are done by the client, in this case the web-vault. Vaultwarden only stores the information it gets, which is all encrypted. This would probably be best to report at Bitwarden. But i think that is already the case.