Bring your passwords, leave the spreadsheet

Claim: migration in should be boring

Nobody switches tools for the pleasure of data entry. The export from your old password manager — a CSV of four hundred rows with idiosyncratic column names — should become structured vault items without retyping, without a cloud round-trip, and without silently dropping the rows the importer did not understand.

The CSV import wizard walks the file column by column. It maps familiar headers to credential fields automatically, lets you reassign the ones it guessed wrong, and shows exactly what each row will become before anything is written. Skipped rows are listed with reasons, not swallowed. The whole operation runs on your device; the file never uploads anywhere, because a migration tool that exfiltrates the thing it migrates is a contradiction.

Structured on arrival

Imported logins do not land as second-class notes. Each row becomes a real credential item in a real template — username, password, URL fields with masking, copy buttons, and search behavior identical to items you typed by hand. Password health sees them, duplicates detection sees them, the checkup sees them. A migrated vault is a first-class vault from row one.

Out is a file, always

Ease of entry is only half of the promise. The other half is that leaving is equally boring: .nt2backup carries the whole vault anywhere, and .nt2legacy carries continuity forward. NT² competes on being the better vault, not on making departure painful. If the import wizard is the front door held open, the export formats are the fire exit kept clear — both are part of the architecture, not favors.