Home › Converters › KeePassXC to Keeper

KeePassXC to Keeper converter

KeePassXC and Keeper both use CSV, but Keeper reads its CSV positionally with no header row, so column order is the whole format — so Keeper rejects a raw KeePassXC export or silently files everything into the wrong fields. Drop your export below and get back a file Keeper accepts.

Convert your KeePassXC export

Drop your KeePassXC CSV here or click to choose a file — nothing is uploaded

The conversion runs entirely in this tab using JavaScript. Your file is never sent to a server — you can confirm it by opening your browser's Network tab, or by turning off Wi-Fi before you drop the file in. Prefer not to do this in a browser tab at all? Download the converter and run it from your own disk.

Your export file is plaintext. Both the file KeePassXC gives you and the one you download here contain every password in readable form. Delete them as soon as the import is verified, and empty your trash.

What's actually different between the two formats

Keeper imports positionally with no header row — the columns have to be in its exact order.

KeePassXC column	Keeper column	What happens
`Title`	`column 2`	Renamed and repositioned
`Username`	`column 3`	Renamed and repositioned
`Password`	`column 4`	Renamed and repositioned
`URL`	`column 5`	Renamed and repositioned
`TOTP`	`— none —`	Keeper has no 2fa secret field. Written into notes instead of dropped.
`Notes`	`column 6`	Renamed and repositioned
`Group`	`column 1`	Renamed and repositioned

What carries over

Field	KeePassXC	Keeper	Result
Item name / title	Yes	Yes	Carried over
Username and password	Yes	Yes	Carried over
Website URL	Yes	Yes	Carried over
Notes	Yes	Yes	Carried over
Folders / groups	Yes	Yes	Carried over
Two-factor (TOTP) secrets	Yes	Yes	Carried over
Favorites	No	No	Not in the source file
Custom fields	No	Yes	Not in the source file
Multiple URLs per entry	No	No	Not in the source file
File attachments	Yes	No	No CSV export includes attachments. Download them out of KeePassXC separately before you close the account — this is the one thing people lose permanently.

Step 1 — Export from KeePassXC

Open your database in KeePassXC and unlock it.
Choose Database → Export → CSV file.
Pick a location and save.

Watch out for

KeePassXC CSV export writes attachments and entry history nowhere — if you need those, keep the .kdbx file as your archive.
Group paths use a forward slash and include the database root, e.g. Passwords/Work. Strip or keep the root depending on where you want entries to land.

Step 2 — Convert it

Drop the file onto the converter above. It parses KeePassXC's layout, maps each field onto the universal record, then writes Keeper's exact expected columns — including the empty ones its importer requires and, where the two differ, the right shape for 2FA secrets. You'll see a preview and a list of anything Keeper can't hold before you download.

Rather not put this file in a browser tab connected to the internet? The same converter is available as a single HTML file you can download and open with your network switched off.

Step 3 — Import into Keeper

Open the Keeper Web Vault → Settings → Import.
Choose "Import from file" and pick CSV.
Upload the converted file. Keeper reads it positionally — there is no header row.

Official instructions: Keeper import documentation

Watch out for

Keeper CSV has no header row. The column order is fixed: folder, title, login, password, website, notes, shared folder, then custom field name/value pairs. Adding a header row makes Keeper import it as an entry.
Subfolders use a backslash: Work\Clients. Forward slashes stay literal.

Step 4 — Verify and clean up

Open ten entries in Keeper at random and check them against KeePassXC.
Generate a 2FA code for one account in Keeper and confirm it matches KeePassXC. A TOTP secret that imported wrong fails silently until you're locked out.
Sign in to one real site using Keeper to confirm autofill works.
Delete both CSV files and empty your trash. If your Downloads folder syncs to iCloud, OneDrive or Dropbox, confirm the deletion propagated there too.
Only then close your KeePassXC account — and change any password you suspect was exposed while the plaintext file existed.

Questions

Why won't Keeper import my KeePassXC file directly?

Keeper imports positionally with no header row — the columns have to be in its exact order. The converter rewrites the file into Keeper's exact expected layout, including the column order and any empty columns its importer requires.

Do my passwords get uploaded anywhere?

No. The conversion is JavaScript running in your own browser tab — the file is read with the FileReader API, transformed in memory, and handed back to you as a download. There is no upload, no server-side processing and no analytics attached to the file. You can verify this by disconnecting from the internet before you drop the file in: the conversion still works.

What gets lost moving from KeePassXC to Keeper?

Keeper can't natively store: file attachments. Rather than drop that data, the converter writes it into the notes field where Keeper has one, so you can move it back by hand. Keep your KeePassXC account active until you've confirmed everything you need made it across.

Will my two-factor codes still work after the move?

Yes, as long as KeePassXC exported the secrets. KeePassXC and Keeper store them in different shapes — one uses a bare Base32 secret, the other a full otpauth:// URI — and the converter translates between them, which is the step most manual migrations get wrong. Check a couple of codes against your old vault before you delete it, since a TOTP secret that fails to import is silent until you're locked out.

Is the export file from KeePassXC encrypted?

No. A KeePassXC CSV export is plaintext — every password in it is readable by anything that can open the file, including other apps on your machine and anything that syncs your Downloads folder to the cloud. Convert it, import it, then delete both files and empty your trash. If your Downloads folder syncs to iCloud, OneDrive or Dropbox, check that the deletion propagated.

Anything unusual about KeePassXC's export?

KeePassXC CSV export writes attachments and entry history nowhere — if you need those, keep the .kdbx file as your archive.

Anything unusual about importing into Keeper?

Keeper CSV has no header row. The column order is fixed: folder, title, login, password, website, notes, shared folder, then custom field name/value pairs. Adding a header row makes Keeper import it as an entry.

Related converters

Other routes out of KeePassXC

Other ways into Keeper

Moving the other way? Keeper → KeePassXC · All 210 converters