How to migrate entries between password managers without losing anything

if you are valuing change password managerIt's normal to worry about what will happen to all your passwords, login credentials, and even passkeys. Nobody wants to get stuck in a tool they can't exit without losing information or going crazy with incomplete exports.

In this article we will break down, calmly but in detail, How to migrate entries between different password managersWhat export and import formats are used, what real limitations exist (for example with passkeys), and what you should keep in mind to avoid sacrificing security while moving.

Why is portability in a password manager so important?

One of the most common fears is ending up “chained” to a manager simply because there's no easy way to transfer the data to another service. This fear isn't unfounded: some providers have unclear, limited, or hidden export functions, and that can turn a seemingly simple change into a real headache.

The reality is that nowadays Most reputable managers allow exporting Your passwords are converted to standard formats, almost always CSV (comma-separated values), and in some cases, JSON or other proprietary formats. The problem is usually not so much being able to export them, but rather:

• What data exactly is included? (username and password only, or also notes, labels, folders, etc.).
• How is that data structured and if the new manager knows how to interpret them.
• What happens with more advanced elements, such as passkeys, custom fields, or card credentials.

Therefore, if data portability is a concern for you, it makes a lot of sense. prioritize export capacity When choosing a password manager, consider this: it's not a whim, it's a guarantee that you can move freely if you find a better option in the future.

Most common export formats (CSV, JSON, etc.)

The dominant format for moving passwords between managers remains the CSV fileIt is a plain text format, easy to read and edit, and recognized by virtually all managers, at least for the basic fields.

In the environment of Google password manager (the one built into Chrome and your Google account), CSV is not just an option: it's the only Supported import format. This means that if you want to import your passwords to Google, you'll need a .csv file, even if the source password manager uses more sophisticated formats like JSON or encrypted exports. If you prefer not to use the browser's built-in password manager, see how prevent web browsers from remembering passwords.

In the specific case of Google, it is very important that the CSV file has the appropriate structureThe first line must contain at least these three columns with those exact names:

• url
• username
• Password

If your original export does not include those headers, or uses different ones (for example, "website", "login", "pass"), you will need to edit the CSV file manually or with a spreadsheet to rename the columns so that Google can recognize them correctly.

Other password managers, such as Bitwarden, 1Password, LastPass, or NordPass, often offer richer formats such as JSON or custom exports These formats include many more details: secure notes, custom fields, folder structure, tags, etc. These formats are very useful as a backup for the manager's own ecosystem, but when migrating to another brand you will almost always end up resorting to CSV because it is the common denominator.

How to import and export passwords in Google Password Manager (Chrome)

If you want to move your passwords to or from the Google password manager Integrated into Chrome, there are some key steps and limitations that you should be clear about from the start.

To import passwords on a computer From another manager to Google, the general flow is:

1. Export your passwords from the source password manager in CSV format. If that manager doesn't provide clear instructions, it's best to consult its specific help documentation, as each one places the export button in a different location.
2. Verify that the CSV has the correct columns in the first line: "url", "username" and "password"If not, modify them manually before continuing.
3. On your computer, open Google Chrome.
4. Go to the three-dot menu in the upper right corner and enter "Passwords and Autofill" and then on Google Password Manager.
5. Within the manager's settings, locate the section "Import passwords"Click on "Select file" and choose the CSV file you just prepared.
6. Follow the on-screen instructions to complete the import.

There are two important limits that many people overlook: on the one hand, You can only import 3000 passwords at a time.If you have more, you'll need to split the content into multiple CSV files and import them in batches. On the other hand, your Google account can store up to 10.000 passwordsSo if you're coming from a manager with lots of old and duplicate records, you might need to do some preliminary cleaning.

Once you complete the import, Google recommends checking if there are weak or leaked passwords In the event of data breaches, you can use the password review features built into the password manager itself. This helps you take advantage of switching password managers to also improve the security of your passwords.

Conversely, if you want to extract your passwords from Google and transfer them to another CSV-compatible password manager, the process is simpler:

1. Open Chrome on your computer.
2. Go to "Passwords and Autofill" and select it again. Google password manager.
3. In the settings, look for the section "Export passwords".
4. Click on «Download file» and save the CSV file to your device.

It is essential that, after the import into the new manager, delete the CSV file Delete the file from your computer or any other location where you've stored it. A CSV file containing passwords is essentially a plain text list of all your passwords: if someone gains access to that file, they have access to your accounts. Delete the file and, if possible, also empty the recycle bin or similar system on your device to avoid any unpleasant surprises.

Bitwarden: security, export and migration from other managers

Bitwarden has gained fame as one of the more comprehensive and transparent password managersThis is especially relevant for those who value open-source software and well-explained security. When migrating, the most important factors are how it handles data import and export, and what happens with privacy.

At Bitwarden, all your vault data is encrypted end-to-end with 256-bit AES-CBC before being stored on any server. This includes, but is not limited to:

• Folder names, collections, items, and attachments.
• All fields of each item type: logins, credit cards, identities, and secure notes.
• All combinations of name and value of custom fields.

The databases and their backups are also stored encrypted, and Bitwarden maintains automatic backups for disaster recovery. If you ever delete your account or organization, that information is permanently erased along with all associated data.

In preparation for migration, Bitwarden allows import data to your individual vault from other password managers or from exported files. It also offers a similar procedure for importing directly into an organization (useful for families, teams, or businesses). In both cases, it's recommended to follow the detailed guides in their help center, which explain which format to use and how to prepare the file for each source password manager. For more practical details, see how Manage your passwords with Bitwarden.

Regarding exporting, Bitwarden is quite flexible: you can export the contents of your vault in standard formats like CSV or JSON, designed precisely so that if you ever decide to leave, you can take your data with you. However, there are some nuances: for security reasons, some exports may not include certain particularly sensitive data or may be sent unencrypted, so it's best to treat them like any critical file (keep only as much as necessary and delete as soon as possible).

passkeysHerein lies one of the most common questions for many users migrating to modern authentication systems. Bitwarden's traditional export to plain text or JSON isn't designed to universally transfer passkeys to another manager, partly because the passkey ecosystem itself doesn't yet have a... common standard for simple export and import among all providers. Although managers are improving in this area, you can't expect a "classic" CSV or JSON export to include and transfer passkeys in a fully interoperable way between services.

In addition to the personal vault, Bitwarden allows you to securely share passwords and other data through organizations and collectionsAny user can create a free organization for two people and share posts with another user. For families and businesses, there are Families, Teams, or Enterprise plans, which also upgrade your individual account to Premium at no extra cost if you're added to one of those organizations.

Bitwarden also offers options for self-cateringThis allows you to manage your password infrastructure on your own servers if maximum data control is your priority. All of this is within a rigorous compliance framework: it adheres to GDPR, HIPAA, CCPA, and the Data Privacy Framework, undergoes regular external audits (such as those from Cure53 or Insight Risk Consulting), and is aligned with SOC 2. Furthermore, its open-source code is constantly reviewed by the community.

NordPass and other providers: how they handle import and export

NordPass is another of the operators that It makes migration much easier from other tools. For starters, it can automatically detect if your browser (currently Chrome or Firefox) has saved passwords and guides you through transferring them in just a few clicks.

If your passwords are in another manager like LastPass, 1Password, Dashlane, KeePass o Proton PassThe process, once again, involves exporting to a CSV file or another compatible format. NordPass even offers a custom CSV template so you can ensure the fields match your import system and avoid errors during the process.

In addition, their help center includes step by step tutorials to transfer data from the most popular file managers. This is especially useful for less technical users, as it reduces the likelihood of errors when exporting or reformatting files.

Other well-known managers, such as 1Password, have also greatly improved their competitor data import features. Overall, the pattern is the same: export from the source manager (usually to CSV or a custom format), and then use an import wizard in the target manager that automatically maps the fields as much as possible.

The biggest difference between managers is usually in:

• What extra fields do they support (secure notes, tags, categories, custom fields, etc.).
• If they provide conversion templates or scripts from specific managers.
• How well do they explain the process in their documentation, and do they offer support when something goes wrong?

Common limitations and problems when exporting from some export managers

Users coming from Chrome, LastPass, and other services have commented in forums and communities that, sometimes, Exporting isn't so clean. as expected. The most frequent problems are usually:

• Exports that not all fields are included (for example, notes or certain metadata are lost).
• CSV formats with non-standard headings which require editing the file before importing it into another manager.
• Limitations on the number of entries that can be exported or on the type of data (e.g., not all categories).
• Export functions hard to find or that are only available in the desktop or web version, but not on mobile.

In some cases, the concern reaches the point of wondering if All managers allow exportingVirtually all serious managers do it, but sometimes the option is somewhat hidden to reduce risks (it is still a very sensitive security operation) or it is accompanied by strong warnings.

That's why it makes sense, before marrying a manager, to check two very specific things: first, if there are clear official documentation Regarding how to export, and secondly, what formats it offers. The more transparency and standard formats, the better for you in the long run.

As for whether you should prioritize export capacity When choosing a database management system, if freedom and interoperability are your priorities, the answer is yes. It's true you won't be exporting every week, but when you do need to, you'll want it to be a straightforward process, not an ordeal.

Passkeys: the big challenge for migrations between managers

passkeys These are cryptographically based credentials that aim to replace traditional passwords. They offer many security and convenience advantages, but currently pose a significant challenge when migrating between account managers.

The doubt of many users, for example of someone who wants move from Bitwarden to 1PasswordThe question is whether there's a simple way to extract all the stored passkeys and transfer them to the new tool. They've tried direct transfer between apps and, in some cases, encountered messages such as the vault being too large or exports that clearly didn't include passkeys.

The underlying problem is that it still There is no universal, consolidated, and widely supported way to export and import passkeys between all managers and platforms. Each ecosystem (browser, operating system, password manager) is implementing its own mechanisms, and interoperability is improving, but it's not yet at the level of simply exporting username and password CSV files.

Furthermore, for security reasons, many solutions limit or restrict the bulk export of passkeysThis prevents them from being extracted en masse to a plaintext format, as happens with private keys for certificates or FIDO2 keys. In some cases, passkey migration between platforms is done more through synchronization between devices and accounts from the same provider than through a classic portable file.

Therefore, if you use passkeys extensively, it's a good idea to check which ones specific support Each service provider offers different services and handles migrations. Currently, it's common that if you switch service providers, you'll have to... manually reconfigure some passkeys in the services where you use them, at least until there is a clear standard adopted by everyone.

Security best practices when migrating between password managers

A migration of this type is not just a technical operation; it is also a delicate moment from a security point of view, because you will be handling files that contain Your entire digital life in plain textIt is advisable to keep in mind some good practices:

• Perform export and import operations in a trusted and up-to-date devicewith antivirus and no unusual software.
• Avoid at all costs saving the CSV in cloud services without additional encryption (Drive, Dropbox, etc.) or send it to you by email.
• If you need to edit the file, do so with local programs (for example, an offline text editor or spreadsheet) and close them as soon as you're finished.
• Once you import the passwords into the new manager, delete CSV file and empty the trash or deletion system of your operating system.
• For a few days, check all critical accounts (main email, online banking, social media, etc.) they continue working and that logins are completed without problems.

It can also be a good time to take advantage of the tools of review of compromised, weak, or reused passwords offered by most modern managers, thus ensuring you emerge from the migration with a higher level of security than you had before.

Ultimately, migrating your passwords between managers is more an exercise in organization and patience than technical complexity. Knowing the export and import formats Given the specifics of each service, the unique features of advanced elements like passkeys, and the limitations of platforms like Google Password Manager, it's perfectly possible to switch tools without losing data or sacrificing security. Choosing a transparent password manager from the start, with good export options and clear documentation, makes all the difference between feeling trapped and knowing you can always switch when needed.