Movepasswords

Home › Converters › Dashlane to Safari

Dashlane to Safari converter

Dashlane and Safari both use CSV, but Dashlane writes 9 columns; Safari expects 6 in a different order — so Safari rejects a raw Dashlane export or silently files everything into the wrong fields. Drop your export below and get back a file Safari accepts.

Convert your Dashlane export

Drop your Dashlane CSV here or click to choose a file — nothing is uploaded

The conversion runs entirely in this tab using JavaScript. Your file is never sent to a server — you can confirm it by opening your browser's Network tab, or by turning off Wi-Fi before you drop the file in. Prefer not to do this in a browser tab at all? Download the converter and run it from your own disk.

Your export file is plaintext. Both the file Dashlane gives you and the one you download here contain every password in readable form. Delete them as soon as the import is verified, and empty your trash.

What's actually different between the two formats

Only 4 of 9 column names match (username, title, password), and they're in a different order — enough for Safari to accept the file and then put your passwords in the wrong fields.

Dashlane columnSafari columnWhat happens
title Title Renamed and repositioned
username Username Renamed and repositioned
password Password Renamed and repositioned
url URL Renamed and repositioned
otpSecret OTPAuth Renamed and repositioned
note Notes Renamed and repositioned
category — none — Safari has no folder field. Written into notes instead of dropped.

What carries over

FieldDashlaneSafariResult
Item name / title Yes Yes Carried over
Username and password Yes Yes Carried over
Website URL Yes Yes Carried over
Notes Yes Yes Carried over
Folders / groups Yes No Written into the notes field as "Folder: …" so you can re-sort later.
Two-factor (TOTP) secrets Yes Yes Carried over
Favorites No No Not in the source file
Custom fields No No Not in the source file
Multiple URLs per entry No No Not in the source file
File attachments Yes No No CSV export includes attachments. Download them out of Dashlane separately before you close the account — this is the one thing people lose permanently.

Step 1 — Export from Dashlane

  1. Sign in to the Dashlane web app at app.dashlane.com.
  2. Open My account → Settings → Export data.
  3. Choose "Export as CSV" and confirm with your Master Password.
  4. Dashlane downloads a ZIP — unzip it and use credentials.csv.

Official instructions: Dashlane export documentation

Watch out for

Step 2 — Convert it

Drop the file onto the converter above. It parses Dashlane's layout, maps each field onto the universal record, then writes Safari's exact expected columns — including the empty ones its importer requires and, where the two differ, the right shape for 2FA secrets. You'll see a preview and a list of anything Safari can't hold before you download.

Rather not put this file in a browser tab connected to the internet? The same converter is available as a single HTML file you can download and open with your network switched off.

Step 3 — Import into Safari

  1. Open the Passwords app (or Safari → Settings → Passwords on older macOS).
  2. Choose File → Import Passwords…
  3. Select the converted CSV.

Watch out for

Step 4 — Verify and clean up

  1. Open ten entries in Safari at random and check them against Dashlane.
  2. Generate a 2FA code for one account in Safari and confirm it matches Dashlane. A TOTP secret that imported wrong fails silently until you're locked out.
  3. Your folder names were written into each entry's note. Re-sort them however Safari organizes items.
  4. Sign in to one real site using Safari to confirm autofill works.
  5. Delete both CSV files and empty your trash. If your Downloads folder syncs to iCloud, OneDrive or Dropbox, confirm the deletion propagated there too.
  6. Only then close your Dashlane account — and change any password you suspect was exposed while the plaintext file existed.

Questions

Why won't Safari import my Dashlane file directly?

Only 4 of 9 column names match (username, title, password), and they're in a different order — enough for Safari to accept the file and then put your passwords in the wrong fields. The converter rewrites the file into Safari's exact expected layout, including the column order and any empty columns its importer requires.

Do my passwords get uploaded anywhere?

No. The conversion is JavaScript running in your own browser tab — the file is read with the FileReader API, transformed in memory, and handed back to you as a download. There is no upload, no server-side processing and no analytics attached to the file. You can verify this by disconnecting from the internet before you drop the file in: the conversion still works.

What gets lost moving from Dashlane to Safari?

Safari can't natively store: folders / groups, file attachments. Rather than drop that data, the converter writes it into the notes field where Safari has one, so you can move it back by hand. Keep your Dashlane account active until you've confirmed everything you need made it across.

Will my two-factor codes still work after the move?

Yes, as long as Dashlane exported the secrets. Dashlane and Safari store them in different shapes — one uses a bare Base32 secret, the other a full otpauth:// URI — and the converter translates between them, which is the step most manual migrations get wrong. Check a couple of codes against your old vault before you delete it, since a TOTP secret that fails to import is silent until you're locked out.

Is the export file from Dashlane encrypted?

No. A Dashlane CSV export is plaintext — every password in it is readable by anything that can open the file, including other apps on your machine and anything that syncs your Downloads folder to the cloud. Convert it, import it, then delete both files and empty your trash. If your Downloads folder syncs to iCloud, OneDrive or Dropbox, check that the deletion propagated.

Anything unusual about Dashlane's export?

Dashlane exports a ZIP containing several CSVs (credentials, payments, ids, securenotes). Logins live in credentials.csv — that is the file to convert.

Anything unusual about importing into Safari?

Safari and the Passwords app share one iCloud Keychain store and one CSV layout — importing to either lands in the same place.

Related converters

Other routes out of Dashlane

Other ways into Safari

Moving the other way? Safari → Dashlane · All 210 converters