Import & Export
LockYit can export your vault to CSV and import data back in, including exports from other password managers. Use this to migrate from another app, merge a second vault, or keep a readable backup alongside your encrypted ones.
Both commands live in Settings → Data, and Import is also available from the Tools menu.
Exporting Your Data
- Go to Settings → Data
- Tap Export
- Read the security warning carefully
- Tap Export
- Choose where to save the file
Your vault is exported as a ZIP file containing one CSV file per item type.
The CSV files contain your passwords and other sensitive data in plain text. Handle with care:
- Store on an encrypted drive
- Delete the file after use
- Never email or upload the file
- Never share the file with anyone
Supported Import Formats
LockYit accepts .csv, .zip, .txt and .kdbx files. When you pick a file, the importer inspects it and chooses one of four routes automatically.
| File | What happens |
|---|---|
LockYit export (ZIP or items.csv) | Restored directly, including links and task data |
| Recognized password manager CSV | Columns matched automatically, ready to review |
| Any other delimited text file | Opens the column mapping editor |
KeePass database (.kdbx) | Prompts for the master password, then imports entries |
Recognized password managers
These formats are detected from their column headers, so you can export from the other app and import the file unchanged:
| Format | Notes |
|---|---|
| Bitwarden | The only built-in format that produces mixed item types from one file: logins, secure notes and cards are separated by its type column |
| 1Password | Several header spellings across versions are handled |
| LastPass | Its extra column is mapped to notes |
| KeePass / KeePassXC | The KeePassXC TOTP column is imported when present |
| Firefox | From about:logins → Export Logins |
| Chrome, Edge, Brave, Vivaldi, Opera | These export an identical column set; the browser name is taken from the filename when it says so |
Folder and grouping columns, favourites, and vendor-internal record ids and timestamps are deliberately not imported. They have no equivalent in LockYit and would otherwise land as noise fields on every item.
KeePass databases
A .kdbx file is encrypted, so LockYit asks for its credentials before reading it.
- Pick the
.kdbxfile - Enter the database master password
- If your database uses one, choose the key file as well
- Tap Unlock
KDBX 3.1 and 4.x are supported. Unlocking runs the same deliberately slow key derivation KeePass uses, so it can take a second or more.
Entry attachments, earlier versions of entries, and anything in the database's recycle bin are not imported. When any are present, the importer tells you exactly what it left behind rather than skipping them silently.
Opening the Importer
Start an import from either place:
- Settings → Data → Import
- The Tools menu - the wrench icon in the app bar on phones and tablets, or the Tools button on the desktop navigation rail
Either one opens your system file picker. Choose the file you exported from the other app, and LockYit takes over from there: what it finds inside decides which of the next two screens you see.
When the format is recognized
When the file matches one of the built-in formats, LockYit says so and reports how many items it found. From here you can:
- Import Items - accept the automatic column matching and go straight to the preview
- Adjust mapping - open the column mapping editor first, to change how a column is imported
- Cancel - stop without importing anything
The Generic Importer
When no built-in format matches your file, LockYit opens the column mapping editor. This is also reachable for a recognized file when the automatic match needs adjusting: choose to adjust the import from the confirmation sheet.
The screen is a preview first and a form second. Each column shows the value it will actually import, taken from a real row of your file, with the controls that change it alongside on wide screens or one tap away on phones.
Step 1: Check how the file is read
The Reading the file section controls how the text is split into rows and columns. LockYit guesses these, and the previews below update as you change them, so you can see immediately when a setting is wrong.
| Setting | What it does |
|---|---|
| Delimiter | The character separating columns: comma, semicolon, tab or pipe |
| Skip rows | Drops lead-in rows before the data starts, for exports that begin with a title or blank lines |
| First row contains column names | Turn off when your file has no header row; columns are then named Column 1, Column 2, and so on |
| Skip empty fields | On by default, so a sparse export does not give every item a set of blank fields. Turn it off to keep every column as a field on every item |
If the previews look like nonsense, the delimiter is almost always the reason.
Step 2: Decide what each row becomes
The Mapping to items section decides the identity and type of the items you create.
| Setting | What it does |
|---|---|
| Name column | The column used as the item's name. With none chosen, LockYit falls back to the first usable value in the row |
| Column with item type | Optional. Lets one file produce several item types by reading the type from a column. Unrecognized values fall back to the default type |
| Default item type | The type used for every row that the type column does not resolve |
A sentence under the controls spells out the combined result for a row, so you can confirm the outcome without importing to find out.
Step 3: Map each column
Below the settings, every column in your file gets a row showing its header, an example value, and how that value will be imported. For each one you can set:
- Import - whether the column is imported at all. Turn it off for columns you do not want.
- Label - the name the field carries on the imported item. Suggestions include LockYit's own field names (Username, Password, Website, Email, Phone, Notes, One-time code) plus the fields belonging to the item type you chose, so imported fields land on keys the item editor already knows how to render.
- Field type - Text, Multiline, Notes, Date, Time, Date & time, Password, Task or One-time code.
- Order - move a column up or down to set where its field appears on the imported item. The table follows your arrangement, so it reads in the order the item will.
Use the row navigator at the top of the table to page through your file and check the mapping against several rows, not just the first one. This is worth doing on any file where columns are inconsistently filled.
Columns whose header contains password, passwd, secret, pin, cvv or cvc are locked to the Password field type, so a secret can never be imported as visible text by accident. Their values are also never shown in the preview.
Value conversion
Saying a column is a Date is a statement about what it holds, so LockYit converts the values to match rather than storing a vendor's 03/15/2024 under a type nothing can read. Dates, times and one-time-code URLs are converted into the app's own storage format, and the preview shows the converted value the way the item will display it.
Ambiguous numeric dates are settled per column, not per cell. A single unambiguous value such as 13/04/2024 proves the whole column is day-first and every value in it is read that way.
A value that cannot be understood is kept exactly as it appears in the file. Nothing is dropped or blanked, so a wrong-looking date is always something you can see and correct.
Reusing a mapping
When you finish mapping a file, LockYit remembers the arrangement for that layout: the column mapping, the order, the default item type, and the skip settings. Import a file with the same shape again - next month's export from the same app - and it arrives already configured.
Reviewing and Confirming
Every route ends at the same preview screen.
- Review the list of items to be imported
- Tap any item to inspect the fields it will create
- Choose how duplicates are handled
- Select or deselect individual items
- Tap Import Items
Items are encrypted with your master password as they are written into the vault.
The imported items appear in your vault straight away, and are searchable, editable and syncable like any other item.
Duplicate handling
| Mode | What happens |
|---|---|
| Replace existing | Matching items are updated in place; non-matching items are added |
| Add as new | Every item in the file is added as a new entry regardless of duplicates |
Items already in your vault are flagged Already in vault on the preview list. A LockYit export carries item ids, so it is matched exactly. A third-party file has no ids, so LockYit matches on content instead, using two independent signatures:
- item type and name, which catches the same file imported twice
- website and username, which catches the same credential exported from a different manager under a different title
Both are deliberately conservative, and empty fields never match each other: hiding an item you wanted is worse than showing a duplicate you can deselect.
Rows that produce no item at all are reported in the import summary with the reason, so nothing disappears unexplained.
Tips
For a large migration from another password manager, import into a spare account first to confirm the mapping is right before touching your real vault.
Export your vault monthly and store the file securely offline. This gives you a human-readable backup alongside your encrypted local backups.
A file with several thousand items can take a few minutes to import. LockYit warns you before starting when the file is large enough for this to matter.