# Dashlane Migration Guide

Export your Dashlane data and import it into DVE. Dashlane often produces **separate files per category** (logins, secure notes, payments, personal info).

## Prerequisites

- Dashlane desktop app or web app with export permission
- DVE **IT Admin** or **Super Admin** role
- Dashlane account unlocked
- Space to store multiple export files if using CSV category exports

## Step-by-step export from Dashlane

### CSV export (category files)

1. Open **Dashlane** and sign in.
2. Go to **My Account → Export Data** (wording may vary slightly by client version).
3. Choose **Export to CSV**.
4. Dashlane creates **separate CSV files** per category, for example:
   - Logins
   - Secure notes
   - Payments / credit cards
   - Personal info / identities
5. Save all CSV files to one encrypted folder.

You can upload each category file as a separate DVE import job, or combine workflows per your admin process.

### JSON export

1. Open **Dashlane**.
2. Go to **My Account → Export Data**.
3. Choose **JSON** export when available.
4. Save the `.json` file locally.

JSON is preferred when your Dashlane plan supports it — one file contains all categories.

## Category-per-file structure

When using CSV, each file's **column headers** tell DVE which Dashlane category you exported:

| Typical file / headers | DVE detection |
|------------------------|---------------|
| Login columns (`username`, `password`, `url`) | `login` |
| Secure note columns (`content`, `note`) | `secure_note` |
| Payment columns (`cardNumber`, `expireMonth`) | `credit_card` |
| Personal info columns (`firstName`, `lastName`, address fields) | `identity` |

DVE autodetects the category from CSV headers during import — you do not need to rename columns if they match Dashlane defaults.

## DVE field mapping

| Dashlane source | DVE field | Notes |
|-----------------|-----------|-------|
| `title` / `accountName` | `name` | Required |
| `username` / `login` | `username` | Login items |
| `password` | `password` | Login items |
| `url` / `domain` | `url` | Website |
| `note` / `notes` / `content` | `notes` | Notes or secure note body |
| `category` | `folder` | Dashlane category label |
| `otpSecret` / `otp` | `totp_secret` | Validated during import |
| Card number / expiry fields | `custom_fields` | On payment items |
| Address / identity fields | `custom_fields` | On personal info items |

## Known limitations and quirks

- **Multiple CSV files** — import each category file or use JSON for a single upload.
- **Dashlane sharing groups** are not exported — recreate access in DVE.
- **Attachments and IDs** (driver license scans, etc.) are not included.
- **Plaintext exports** — delete files immediately after successful import.

## Import into DVE

1. Open **Import** in DVE.
2. Select **Dashlane JSON** or **Dashlane CSV** matching your export.
3. For CSV, upload the file for the category you are importing (logins first is a good order).
4. Repeat for additional category CSV files if needed.
5. Confirm each job completes before deleting source files.

## Post-import verification checklist

- [ ] Login count matches Dashlane login export rows.
- [ ] Secure notes have content in `notes` without URLs.
- [ ] Payment cards show card-related custom fields.
- [ ] Identity/personal info items imported as `identity` type.
- [ ] Review TOTP warnings in job summary.
- [ ] Delete all Dashlane export files from disk.
- [ ] Disable Dashlane auto-fill after user cutover.

## Related guides

- [Migration Overview](overview.md)
- [LastPass Migration Guide](lastpass.md)
- [Generic CSV Migration Guide](generic-csv.md)