Skip to main content

Enpass-Escape

A lightweight Python CLI to migrate Enpass data to Apple Passwords, Bitwarden, or Google Password Manager.

🚀 Features

  • Converts Enpass CSV or JSON export to Apple Passwords import CSV
  • Converts Enpass logins and secure notes to Bitwarden CSV
  • Converts website passwords to Google Password Manager CSV
  • Keeps the newest safely identifiable duplicate by default
  • Preserves TOTP/2FA secrets with proper otpauth URI formatting
  • Maintains titles, URLs, usernames, passwords, and notes
  • Combines any additional fields into organized notes
  • Excludes archived and trashed items unless requested
  • Writes output atomically with owner-only permissions
  • Zero external dependencies except Typer for the CLI interface

📋 Prerequisites

  • Python 3.11 or higher

🛠️ Installation

Install from PyPI:

pip install enpass-escape

Or install development version:

git clone https://github.com/ake2l/enpass-escape.git
cd enpass-escape
python -m venv .venv
source .venv/bin/activate
make install
make check

Run make help to list the local development commands. For example:

make dry-run INPUT=/path/to/export.json TARGET=google
make export INPUT=/path/to/export.json OUTPUT=google.csv TARGET=google

💻 Usage

Note: The Enpass CSV export does not support all fields completely (e.g., TOTP, notes, extra fields). For best results, it is recommended to use the JSON export from Enpass!

Run the enpass-escape command with your Enpass export and desired output path:

# CSV-to-CSV
enpass-escape enpass-export.csv export-apple-passwords.csv

# JSON-to-CSV
enpass-escape export.json apple-output.csv

# Google Password Manager; website passwords only
enpass-escape export.json google-output.csv --target google

# Bitwarden personal vault
enpass-escape export.json bitwarden-output.csv --target bitwarden

# Analyze without creating a plaintext export
enpass-escape export.json --target google --dry-run

# Keep all duplicates
enpass-escape export.json apple-output.csv --duplicates keep

# Include archived items
enpass-escape export.json apple-output.csv --include-archived

# Replace an existing output file
enpass-escape export.json apple-output.csv --force

# View help
enpass-escape --help

The output CSV will have the header:

Title,URL,Username,Password,Notes,OTPAuth

Input Formats

  • JSON (recommended): Enpass JSON export (recommended for complete data export)
  • CSV: Standard Enpass CSV export (limited field support)

Output Formats

Apple Passwords import CSV with the following columns:

Title,URL,Username,Password,Notes,OTPAuth

Google Password Manager CSV:

url,username,password,note

Google exports contain only entries with an HTTP(S) URL and a password. Only the title and item note accompany the login; arbitrary Enpass fields are not copied into Google's note. Files are split automatically at Google's 3,000-entry import limit. TOTP secrets, attachments, and passkeys are not exported.

Bitwarden personal-vault CSV:

folder,favorite,type,name,notes,fields,reprompt,login_uri,login_username,login_password,login_totp

Choose Bitwarden (csv) when importing. Logins retain their URL, username, password, TOTP, favorite flag, notes, and custom fields. Other Enpass item types are preserved as secure notes because Bitwarden CSV supports only logins and secure notes. A single Enpass folder becomes a Bitwarden folder; multiple folders are retained in the item data. Files are split at Bitwarden's 40,000-item limit. Attachments must be uploaded separately.

Bitwarden does not check imports for duplicates. Import each generated file only once.

Duplicates

  • newest (default): keep the entry with the highest Enpass updated_at for the same normalized URL and username
  • exact: remove only entries with identical migrated content
  • keep: do not remove duplicates

Entries with missing or tied timestamps are kept when their content differs. CSV exports usually have no timestamps, so JSON is recommended for newest.

🔒 Security Considerations

  • All processing is local; no network calls
  • No data is stored or cached
  • Output files are unencrypted and readable only by their owner
  • No external dependencies other than Typer
  • Delete the output after importing it successfully

🤝 Contributing

Contributions welcome! Open an issue or submit a pull request.

📝 License

MIT License. See LICENSE for details.

Release files for enpass-escape 0.3.0

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

Source distribution (sdist)

Source distribution for enpass-escape 0.3.0
File Size Uploaded
enpass_escape-0.3.0.tar.gz 22.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for enpass-escape 0.3.0
File Interpreter ABI Platform
enpass_escape-0.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 36.7 kB

Release files / enpass_escape-0.3.0.tar.gz

Download URL enpass_escape-0.3.0.tar.gz
Size 22.3 kB
Tags Source
SHA-256 checksum
How to use checksums
6a6948874a255f8f717602e140f51d540f68184d9b97698d6bd775be6d505717
BLAKE2b-256 checksum
How to use checksums
ad685edb5edccc975d88ed604d8913431371fca809000b5dcbaebc9e759ba96e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 13, 2026.

Transparency log

Release files / enpass_escape-0.3.0-py3-none-any.whl

Download URL enpass_escape-0.3.0-py3-none-any.whl
Size 14.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
fe4a7c472d12990b59e57aad37b712245606cfcf1c017a61366de73454d22435
BLAKE2b-256 checksum
How to use checksums
e3f8a4a37478552fc100ee9d381e9041ecfe635dc7734623a30ac097a8c80522
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 13, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.3.0 This release

2 release files

0.2.0

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