Move From 1Password to KeePass: Import File Attachments, Custom Fields and More

Strongbox is now more reliable than ever when importing 1Password databases, with improved handling of file attachments, custom fields, tags, and folder structures.


When you migrate from 1Password to another password manager, like Strongbox, you want to be confident that all of your data has come across without anything being lost.

Most password managers will only import your usernames and passwords from 1Password, ignoring or mishandling file attachments, custom fields, tags and folder structures. This means that you will need to check what data is missing and move it across manually. This is time consuming and error prone. With Strongbox you can import your entire 1Password vault in one go.

And we’ve recently improved Strongbox’s import functionality for 1Password, LastPass and Apple/iCloud Keychain. Read on to find out how we’ve made our 1Password import more reliable.

1PUX Support

With the update to 1Password 8, it’s now possible to export your 1Password data to a new file format called 1Password Unencrypted Export (1PUX). 1PUX includes a new data structure. It’s more logically structured than the previous 1PIF format and preserves far, far more data than CSV.

In order to parse 1PUX files, we built a dedicated new importer which preserves as much metadata as possible, copying attachments across and trying to maintain field ordering and Archived items.

1PIF Improvements

We’ve also revamped the way that we import 1PIF files. 1PIF was the file format previously used when exporting databases in older versions of 1Password.

These improvements mean that the entries in the Archive and Trash folders in your 1PIF file will now be imported into Strongbox. We’ve also improved the general reliability of 1PIF imports.

Custom Sections in 1Password

In 1Password, custom fields can be grouped into sections and those custom sections can be named.

This is one aspect of your 1Password database that Strongbox is not able to interpret and import. All custom fields will be imported but they will not be grouped into sections (as they appear when viewed in the 1Password app).

If you have entries that contain a lot of different sections and custom fields, we recommend checking that the custom fields within an entry don’t have duplicate names. And, if that is the case, consider prefixing the custom field name with its section name in the 1Password app before you export your database to a 1PUX file. If you don’t, the custom fields could be difficult to identify once they’ve been imported into Strongbox.


For step by step instructions on how to move your data from 1Password to Strongbox, check out our guide here.

If you have any feedback or issues, don’t hesitate to contact our support team:

CVE-2023-24055 Vulnerability Update

Security researchers have recently discovered a vulnerability in the Windows KeePass app that could allow attackers to obtain stored passwords in cleartext. The bug has been dubbed CVE-2023-24055.

The Strongbox app is not affected by this vulnerability. Which means that if you use Strongbox to work with your KeePass databases you’re protected.

The exploit is based on an attacker being able to edit a configuration file and set up a trigger that silently exports entries from the KeePass database. Strongbox is architected so that configuration files can not be edited by an attacker in this manner.

The Strongbox team is monitoring the situation and will respond if there are any further developments.