How to Import Your Passwords from LastPass, 1Password, and Others

The biggest thing standing between most people and a better password manager is not the new app. It is the hundred logins already sitting in the old one. Re-entering them by hand is the kind of chore that never gets done, so the move keeps getting postponed.

Kinship Vault closes that gap with one feature: Import from File. Nearly every password manager, LastPass, 1Password, Bitwarden, Chrome, and Apple Passwords among them, can export your logins to a CSV file. Kinship Vault reads that file and brings every login into your vault in a single step, and it does the whole thing on your device.

Step 1: Export a CSV from your current manager

Every manager keeps this in a slightly different place, but it is almost always called "Export" and it produces a .csv file. Here is where to look in the common ones.

Step 2: Open Import from File in Kinship Vault

1. Open Kinship Vault and go to Passwords.
2. Tap the add button (the + in the top corner) to open its menu.
3. Choose Import from File.
4. Pick the CSV you exported. On iPhone and iPad you may need to reach it through Files; on a Mac, through the file picker.

Importing logins is a Vault Pro feature, the same plan that covers the rest of the password manager, so if you already have Pro there is nothing extra to buy.

Step 3: Let Kinship Vault map the columns

Different managers name their columns differently. One writes username, another login_username, a third just email. Rather than a brittle importer with a separate branch for each vendor, Kinship Vault reads the header row of your CSV and maps the columns by meaning. That is why one importer handles so many managers, and why an export from a tool we have not named will usually still work, as long as its columns are recognizable.

Two things happen automatically as it reads:

• Duplicates are skipped. Every row is matched against what you already have, by the site's domain and the username, so re-importing or bringing in an overlapping export will not create a second copy of a login.
• Blank rows are skipped. Empty lines, and rows with no username, password, or URL, are quietly dropped instead of cluttering your vault.

When it finishes, Kinship Vault tells you exactly what happened, for example "Imported 214 logins, skipped 6 duplicates." Your 2FA codes come across when the export includes their otpauth or TOTP secret, so the six-digit codes keep generating right next to the login they protect, and any notes come along too.

The whole import happens on your device. The plaintext CSV is read into memory, turned into encrypted logins, and never written to disk or sent anywhere by the app.

Step 4: Delete the CSV, on both ends

Once you have confirmed the logins landed, finish the job:

• Delete the CSV file from your device (and empty the trash or Recently Deleted). It is a plaintext copy of your passwords with no reason to linger.
• Delete the export from your old manager if it kept one, and, once you are confident everything came across, close down that account so there is not a second live copy of your vault out there.

Right after you import

A migration is a good moment to tidy up. Two things worth doing once your logins are in:

• Run Security Checkup. It reviews your imported logins on device and flags the weak, reused, and old ones, and, if you allow it, the ones caught in known breaches, using a privacy-preserving check that never sends a full password anywhere.
• Turn on AutoFill and the browser extension so your freshly imported logins fill themselves in on your phone, in apps, and across your desktop browsers.