Data from LastPass, Penn's previous password management tool, can be transferred to Dashlane through several methods. The University's contract with LastPass expires September 26, 2024. Data from LastPass vaults will not be lost after that date and can still be migrated--Premium accounts will revert to free accounts, as may Enterprise accounts (see the links in the Resources section below for details). However, users are strongly encouraged to migrate their data before the contract expires.
Considerations
There are several considerations when migrating data from LastPass to Dashlane. There are different methods of transferring data, and shared passwords, in particular, need an extra set of considerations.
LastPass data does not map one-to-one with Dashlane
LastPass' shared folders are replaced by "collections" within Dashlane, with a separate set of considerations. There is no hierarchy of folders, so any sub-folders in LastPass will be transferred as individual collections.Ownership/permissions data does not transfer to Dashlane
Any shared passwords must be re-shared in Dashlane, as user accounts and ownership are not captured or reapplied during the transfer.Different methods of transferring data have different considerations
Data can be exported from LastPass or imported directly from the Dashlane console, but what data can be captured differs on the method.Trying to import an existing username/password into a Dashlane vault will fail
If you try to import an existing username/password combination into a Dashlane vault, it will not overwrite the previous entry. If the previous username/password combination was incorrect, delete it from Dashlane before importing it again. (It is possible to get duplicate usernames/passwords in Dashlane, but usually when importing the same combination from different sources)
Using the migration tool in the Dashlane console
The integrated Dashlane migration tool can transfer personal vaults directly from LastPass into Dashlane. This method does not transfer data from shared folders and linked LastPass accounts. The migration tool is the preferred method of transferring data from a LastPass Premium account.
To migrate data using the migration tool:
Log into the Dashlane web console and open your personal vault.
Click on "My Account" in the upper-right corner of the screen and select "Settings."
In the Settings menu that appears, click "Import Data."
From the drop-down menu that appears, click "LastPass."
Select "Directly from Lastpass (encrypted)" and select "Go to LastPass."
Log into LastPass in the window that appears.
If your LastPass data is locked (likely) you'll get an error and be presented with an "Unlock your data with your LastPass login" screen. Enter your LastPass username and master password here, and click the "Unlock Data" button.
You'll be presented with a list of items to import--select where you want each item to go in the drop-down menu and click "Import Items."
Importing data using a .CSV
You can export a .csv of your LastPass data and import it into Dashlane. This method has the notable downside of putting password data in an unencrypted .csv file, but it is the only method of transferring data from LastPass shared folders.
Step 1: Export your data from LastPass
Log into your LastPass vault.
Click on "Advanced Options" in the lower-left and select "Export" from the pop-up menu that appears.
You'll get an email notification asking you to confirm the export. Approve the export and return to your vault. (If you don't see a prompt immediately, select "Export" from the Advanced Options menu again)
You'll be prompted to re-enter your master password. Do so and you'll download a .csv file of your vault, including shared passwords and any linked accounts.
IMPORTANT: Open your .csv file and verify that the format is correct. A comma indicates a new cell in a CSV file, so any passwords that had commas in them will be split into multiple cells. You'll need to manually fix any passwords that were broken in the export.
Step 2: Import your data from LastPass
Log into the Dashlane web console and open your personal vault.
Click on "My Account" in the upper-right corner of the screen and select "Settings."
In the Settings menu that appears, click "Import Data."
From the dropdown menu that appears, click "LastPass."
Select "From a downloaded CSV (unencrypted; compatible with LastPass SSO)" and click "Get Started."
At the next screen, drag-and-drop your .csv file or select it for upload and click "Next."
You'll be presented with a list of items to import--select where you want each item to go in the drop-down menu and click "Import Items."
Collections vs Shared Folders
Collections are Dashlane's equivalent of the LastPass shared folder; while there are some similarities, there are some significant differences to take into consideration when importing LastPass shared folders, especially into Dashlane Business accounts:
Similarities
Collections can be shared with individuals or groups. (Groups are a Dashlane Business feature)
Permissions can be assigned to individual collections to restrict access, password visibility, provide read-only access, etc.
Differences
A single item can exist in multiple collections in Dashlane instead of being tied to a single shared folder as in LastPass.
There is no hierarchy of collections; you cannot have a sub-collection like a sub-folder in LastPass.
Some permissions apply to the entire collection in Dashlane rather than to a user/group level.
For Dashlane Business accounts, collections are not globally visible like shared folders are in LastPass
Best practices for migrating shared data
How to migrate shared data will depend heavily on the organization doing the migration, so it is difficult to make global suggestions for how to do so. However, here are some tips and best practices for migrating LastPass shared folders into Dashlane collections that you may find useful:
Determine who will be importing shared passwords in advance
If multiple people import and/or try to share the same password data into Dashlane, it is not strictly deleterious--in most cases, the worst that will happen is that you end up with multiple password entries and/or collections with the same name. That being said, to minimize confusion it is generally best to have only one person import each individual shared folder or collection. In addition, this will minimize the number of individuals that will need to use the .csv import option.Share with groups, rather than individuals
It is generally easier to manage access to shared resources by creating a group in Dashlane, then sharing collections with the group rather than with an individual. Then as you add/remove users, you can add them to the group that needs access to specific collection(s) rather than having to individually add/remove users.Consider how you will manage any sub-folders, if any
If you are using nested folders in LastPass, you may want to reorganize how passwords are share and/or who has access. If some users had access to a superset of passwords and others had access to a subset, you might want to consider creating a "superset" collection and a "subset" collection, and putting the "subset" passwords in both.
Add a comment
Please log in or register to submit a comment.