Skip to main content

enpass2onepassword

Tool to migrate from Enpass to 1Password. This tool takes an Enpass JSON export and imports it via the 1Password SDK.

Requirements

  • You need Python 3 installed on your system.
  • You need pip installed on your system.
  • You need to know how to open a Terminal aka Shell.
    • On macOS, for example Terminal.app.
    • On Windows, for example PowerShell.
    • On Linux: You know your way.

Quick-Start

  1. Follow the Preparations section below.
  2. Install uv.
  3. Then, in a terminal of your choosing, run the following command:
    uvx enpass2onepassword ~/Documents/no_backup/enpass_export.json
    
  4. Fill in the information
    • Sa name: The name of your 1Password Service Account
    • Sa token: The token (aka credential) for the 1Password Service Account.
    • Op vault: The name of the empty(!) 1Password Vault.

Preparations

  1. Create a new 1Password Vault.
  2. Create a 1Password Service Account.
    • Call the Service Account whatever you like, for example enpass2onepassword
    • Use the cog ⚙️ to add the write permission to the Service Account
    • See the official documentation for further guidance.
  3. Copy the Service Account Token (and/or save it to 1Password).
  4. Export your Enpass Vault as JSON, for example as export.json.
    • ⚠️ The export is unencrypted!
    • Don't forget to delete the file after a successful import!
    • Ensure, that you export the vault to a place that is not synced to another computer and which is not backed up automatically.
      • If you use Time Machine on macOS, create a folder no_backup in your Documents. Then open the System Settings. Under General click on Time Machine. Now click on Options…. Use the +-button to add the folder you just created to the Exclude from Backups list.
    • A good place would also be an SD card or a USB drive with an encrypted filesystem.

Usage Overview

Usage: enpass2onepassword [OPTIONS] ENPASS_JSON_EXPORT

  Adds items from an Enpass JSON export to a 1Password vault through the
  1Password API.

Options:
  -n, --op-sa-name, --sa TEXT     The 1Password service account name. You
                                  chose this when creating the 1Password
                                  service account.

                                  Can also be supplied as environment variable
                                  'OP_SERVICE_ACCOUNT_NAME'.  [default:
                                  enpass2onepassword; required]
  -t, --op-sa-token, --token TEXT
                                  The 1Password service account token. It was
                                  shown to you when you created the 1Password
                                  service account.

                                  Can also be supplied as environment variable
                                  'OP_SERVICE_ACCOUNT_TOKEN'.  [required]
  -o, --op-vault, --vault TEXT    The name of the 1Password vault. All Enpass
                                  items will be created in that 1Password
                                  vault. This 1Password vault must be empty!
                                  Also, the service account must have write
                                  permissions to it.

                                  Can also be supplied as environment variable
                                  'OP_VAULT'.  [default: Enpass; required]
  --ignore-non-empty-vault        By default, this tool will stop if it
                                  detects that there are already items in a
                                  vault. Use this flag to ignore this behavior
                                  and continue, even if there are already
                                  items in the given vault. If you use this,
                                  you should definitely make a sound backup of
                                  the vault before the import!
  --no-confirm                    By default, this tool will stop before
                                  importing anything to 1Password, and you
                                  need to confirm the import. Use this flag to
                                  ignore this behavior and import without
                                  further confirmation.
  --no-wakelock                   By default, this tool will prevent the
                                  computer to go to sleep while the import is
                                  running. Use this flag to disable this
                                  behavior.

                                  When this flag is defined, then the computer
                                  might go to sleep and interrupt your import.
                                  The import is usually resumed, when your
                                  computer resumes from sleep. The result is
                                  that you won't make the best use of the
                                  1Password rate limits.
  --silent                        By default, this tool will print status
                                  information while importing to 1Password.
                                  Use this flag to disable such reports.
  --skip INTEGER                  Skip the first number of items. This can be
                                  helpful to recover a failed import.
                                  [default: 0]
  --op-rate-limit-hourly INTEGER  1Password enforces a write request rate
                                  limit per 1Password Service Account. The
                                  hourly rate limit as of 2025-01-01 is 100
                                  requests per hour for private, family and
                                  team accounts and 1'000 requests per hour
                                  for Business accounts.

                                  See https://developer.1password.com/docs/service-accounts/rate-limits/ for more info.  [default: 100]
  --op-rate-limit-daily INTEGER   1Password enforces a write request rate
                                  limit per 1Password Account. The daily limit
                                  as of 2025-01-01 is 1'000 requests per hour
                                  for private and family accounts, 5'000 per
                                  day for Teams accounts and 50'000 requests
                                  per hour for Business accounts.

                                  See https://developer.1password.com/docs/service-accounts/rate-limits/ for more info.  [default: 1000]
  --op-client-validity INTEGER    This tool authenticates with the 1Password
                                  server in order to import entries. This
                                  authentication is only valid for a certain
                                  amount of time. With this parameter, you can
                                  adjust the time after which a this tool re-
                                  authenticates with the 1Password server.

                                  The value is in seconds.  [default: 1800]
  --help                          Show this message and exit.

Tip: Load Service Account Credentials via 1Password CLI

Add the credentials of your 1Password Service Account to your private 1Password vault like so:

  • Vault: Private
  • Type: API Credential
  • Name: Service Account Auth Token
  • Username: enpass2onepassword (or whatever you chose as username)
  • Password: ops_… (the secret generated by 1Password)

Note: If you choose other names, you need to adjust the commands below to make it work!

Then install the 1Password CLI and use the following command to run the migration tool:

# unlock 1Password CLI
op signin

# specify the paths to the secrets
export OP_VAULT="Enpass"
export OP_SERVICE_ACCOUNT_NAME="$(op read 'op://Private/Service Account Auth Token/username')"
export OP_SERVICE_ACCOUNT_TOKEN="$(op read 'op://Private/Service Account Auth Token/password')"

# inject the secrets
uvx enpass2onepassword ~/Desktop/export.json

If that does not work, it may help to replace Private with the vault's UUID (which is a value like johaxupyjfamyo2ivigxs64y8n) in the above snippet.

Update

Run the following command to update the tool to the latest version.

uv tool upgrade enpass2onepassword

Roadmap

  • Improved support for credit card's expiry date, once #140 is implemented
  • Support for importing attachments, once #139 is implemented
  • Improved support for Secure Notes, once #141 is implemented
  • Improved support for Wireless Networks, once #142 is implemented
  • Support for favorites, once #143 is implemented

jq tips for developers

These tips require that jq is installed on your computer.

List all categories in export

To list all the categories in the Enpass export, use the following command:

jq '[.items[].category] | unique' export.json

List all field types in export

To list all the field types in the Enpass export, use the following command:

jq '[.items[] | select(.fields != null) | .fields[]] | flatten | [.[].type] | unique' export.json

Split your export by category

To split your export by category, use the following command:

jq '{folders: .folders, items: [.items[] | select(.category == "uncategorized")]}' export.json > export_uncat.json
#                                                               ^^^^^^^^^^^^^ Change category here

Select all items with a note

jq '{folders: .folders, items: [.items[] | select(.note != "")]}' enpass_complete.json > export_hasnote.json

Development

This project uses uv for dependency management, building and publishing.

Run the development build:

uv sync
uv run enpass2onepassword

Update dependencies:

uv lock --upgrade

Linters

This project uses MegaLinter. To run MegaLinter locally:

npx mega-linter-runner

This requires a valid Docker-compatible container runtime to be available, like Podman. Also, it required a Node installation with npm.

Release

Release procedure:

  1. Edit the version in pyproject.toml
  2. uv sync
  3. Commit the change
  4. git push
  5. git tag 0.1.0
  6. git push --tags

The rest is taken care of by the Release GitHub Action.

Copyright and License

Copyright © 2025 Christian Mäder. See LICENSE for license.

Metadata

Release files for enpass2onepassword 0.3.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for enpass2onepassword 0.3.3
File Size Uploaded
enpass2onepassword-0.3.3.tar.gz 22.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for enpass2onepassword 0.3.3
File Interpreter ABI Platform
enpass2onepassword-0.3.3-py3-none-any.whl Python 3 none any Details

Total release size: 46.4 kB

Release files / enpass2onepassword-0.3.3.tar.gz

Download URL enpass2onepassword-0.3.3.tar.gz
Size 22.4 kB
Tags Source
SHA-256 checksum
How to use checksums
a0b77a1f6e6e2dbd8937116dc23f8431f6c7377071223b65ea05b7fc9813ffaa
BLAKE2b-256 checksum
How to use checksums
592360348b17137af420f04c36fd4103928ebc657365eebdb45700a20593dd6a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.8

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Feb 8, 2025.

Transparency log

Release files / enpass2onepassword-0.3.3-py3-none-any.whl

Download URL enpass2onepassword-0.3.3-py3-none-any.whl
Size 24.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8f07b5dec468ac8066b965f06e02fbbc314dcb599ad5e92665a9e4aa8b8d584a
BLAKE2b-256 checksum
How to use checksums
1307c8ba90a6e3a2452ed481e42851cfefcbe62eaea45487621e5326de663467
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.8

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Feb 8, 2025.

Transparency log

Release history Release notifications | RSS feed

This release

0.3.3 This release

2 release files

0.3.2

2 release files

0.3.1

2 release files

0.2.0

2 release files

0.1.2

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page