Migrating from Sticky Password to Bitwarden: A Guide

Moving your password manager is a significant decision that requires careful execution. If you have been using Sticky Password and are considering Bitwarden for its open-source nature, stronger encryption options, or self-hosting capabilities, this guide walks through the entire migration process with practical examples and automation tips suitable for developers and power users.

Understanding the Migration Challenge

Sticky Password stores your data in a proprietary format, while Bitwarden supports various import formats including CSV, JSON, and KDBX (Keepass). The migration involves exporting your data from Sticky Password, converting it to a Bitwarden-compatible format, and then importing it into Bitwarden. Unlike some competitors, Bitwarden provides multiple import pathways that accommodate different use cases.

Before starting the migration, ensure you have both applications installed and your Sticky Password master password available. This process requires temporary storage of your passwords in an intermediate format, so work in a secure environment and delete temporary files immediately after completing the migration.

Exporting Data from Sticky Password

Sticky Password provides an export feature that generates a CSV file containing your stored credentials. Launch the Sticky Password application and navigate to the menu options. The exact location varies slightly depending on your version, but typically you will find this under Settings or the main menu.

In Sticky Password, access the export function:

Open Sticky Password and click the menu icon (three horizontal lines or gear icon)
Select “Settings” or “Options”
Look for “Export” or “Backup” sections
Choose “Export to CSV” format

The exported CSV contains columns for website URLs, usernames, passwords, notes, and other metadata. Verify that the export includes all your entries before proceeding. If you have a large vault, this export process may take several minutes.

Sticky Password also supports exporting to KDBX format, which provides better compatibility with password managers that support Keepass databases. This format preserves more metadata and is generally the preferred approach for advanced users.

# After exporting, verify your CSV file exists and check its structure
ls -la sticky-password-export.csv
head -5 sticky-password-export.csv

Preparing Data for Bitwarden Import

Bitwarden accepts CSV imports directly, which simplifies the process considerably. However, you may need to adjust the column mapping to match Bitwarden’s expected format. The required columns for a standard Bitwarden import include:

folder
favorite
type
name
login_uri
login_username
login_password
login_totp
notes
fields
reprompt

For most users migrating from Sticky Password, you will need to create a mapping script or manually adjust the CSV. Here is a Python script that handles common conversions:

#!/usr/bin/env python3
import csv
import sys

def convert_sticky_to_bitwarden(input_file, output_file):
    """Convert Sticky Password CSV export to Bitwarden import format."""

    field_mapping = {
        'URL': 'login_uri',
        'Login': 'login_username',
        'Password': 'login_password',
        'Notes': 'notes',
        'Title': 'name'
    }

    bitwarden_fields = [
        'folder', 'favorite', 'type', 'name', 'login_uri',
        'login_username', 'login_password', 'login_totp',
        'notes', 'fields', 'reprompt'
    ]

    with open(input_file, 'r', encoding='utf-8-sig') as infile:
        reader = csv.DictReader(infile)

        with open(output_file, 'w', newline='', encoding='utf-8') as outfile:
            writer = csv.DictWriter(outfile, fieldnames=bitwarden_fields)
            writer.writeheader()

            for row in reader:
                new_row = {
                    'folder': '',
                    'favorite': '',
                    'type': 'login',
                    'name': row.get('Title', ''),
                    'login_uri': row.get('URL', ''),
                    'login_username': row.get('Login', ''),
                    'login_password': row.get('Password', ''),
                    'login_totp': '',
                    'notes': row.get('Notes', ''),
                    'fields': '',
                    'reprompt': ''
                }
                writer.writerow(new_row)

    print(f"Converted {input_file} to Bitwarden format: {output_file}")

if __name__ == '__main__':
    if len(sys.argv) != 3:
        print("Usage: convert.py input.csv output.csv")
        sys.exit(1)

    convert_sticky_to_bitwarden(sys.argv[1], sys.argv[2])

Save this script as convert.py and run it with your export files:

python3 convert.py sticky-password-export.csv bitwarden-import.csv

Importing into Bitwarden

Once your data is in the correct format, importing into Bitwarden is straightforward. You can use either the web interface, desktop application, or CLI. For developers who prefer command-line workflows, the Bitwarden CLI provides efficient batch import capabilities.

Using Bitwarden CLI

Install the Bitwarden CLI first if you have not already:

# macOS
brew install bitwarden-cli

# Linux (via npm)
npm install -g @bitwarden/cli

# Verify installation
bw --version

Authenticate with your Bitwarden account:

bw login your-email@example.com

After authentication, import your converted CSV:

# Import command requires unlock first
bw unlock
# Copy the session key from the output, then:

bw import bitwardencsv --file ./bitwarden-import.csv

The import process handles duplicate detection, though you may want to review the results carefully, especially for entries with similar URLs or usernames.

Using the Web Interface

Alternatively, log into vault.bitwarden.com and navigate to Settings > Import Data. Select “Bitwarden (CSV)” as the format and upload your converted file. The web interface provides visual feedback during import and displays a summary of imported items.

Verifying Your Migration

After importing, verify the integrity of your migrated data. Check a sample of entries to confirm usernames, passwords, and URLs transferred correctly. Pay particular attention to entries with special characters in passwords, as these sometimes cause encoding issues during conversion.

# Using Bitwarden CLI to list recently imported items
bw list items --search "import" | head -20

Review folders and favorites if you used these organizational features in Sticky Password. The mapping script may require adjustment if these did not transfer correctly.

Cleaning Up

Delete all temporary files containing your passwords:

# Remove export and conversion files
rm sticky-password-export.csv bitwarden-import.csv convert.py

Clear your command history if it might contain password references:

# Clear the session from Bitwarden CLI
bw lock
bw logout

Post-Migration Considerations

After successfully migrating, take time to update your browser extensions and ensure automatic fill functionality works correctly. You may also want to enable two-factor authentication on your Bitwarden account if you have not already done so.

For developers using Bitwarden for secrets management, explore the Bitwarden Send feature for sharing sensitive information securely, and consider integrating the CLI into your development workflow for programmatic secret retrieval.

The migration process, while requiring some technical steps, provides an opportunity to audit your password inventory and remove outdated entries. This periodic cleanup improves your overall security posture and reduces the attack surface of your password vault.

Built by theluckystrike — More at zovo.one