Password Manager Manual: Import Accounts, Organize Vaults, Share Access, and Recover Safely
password managersaccount securitypasskeysautofillpassword vaultsemergency recovery

Password Manager Manual: Import Accounts, Organize Vaults, Share Access, and Recover Safely

MManuals.top Editorial Team
2026-11-17
6 min read

A practical password manager checklist for safe imports, organized vaults, autofill, passkeys, sharing, exports, and recovery testing.

This password manager setup guide gives you a repeatable way to import accounts, organize a vault, enable autofill and passkeys, share selected credentials, and test recovery without creating a new lockout risk.

Overview

A password manager is only as dependable as its setup and recovery plan. The goal is not simply to move passwords into an app; it is to create a controlled system that works across your computer, phone, browser, and any shared household or team devices.

Before choosing settings, confirm how the manager handles your account password, multi-factor authentication, recovery codes, device approval, emergency access, exports, shared vaults, and passkeys. Feature names vary between products, and some options may be limited by the account type or administrator settings. Treat the product’s current help documentation as the final reference when a screen differs from this guide.

Initial setup checklist

  • Install the manager only from its official website or the official app store.
  • Create a long, unique account or master password that is not reused anywhere else.
  • Record recovery codes or other recovery material in a protected offline location.
  • Enable multi-factor authentication if the manager supports it and your recovery plan is ready.
  • Install the approved browser extension and mobile app on the devices you actually use.
  • Confirm that you can sign in manually before enabling autofill.
  • Import a small test set before moving your complete collection.

Do not delete the old password records immediately after importing. Keep the original source available until you have checked important accounts, tested sign-in, and confirmed that notes, usernames, and one-time codes transferred correctly.

Checklist by scenario

How to import passwords safely

Start by identifying the source: a browser export, another password manager, a spreadsheet, or a manually maintained file. Export formats and supported fields differ, so use the destination manager’s import instructions rather than guessing.

Source formatUseful forChecks before importing
Manager-to-manager exportMoving structured logins and selected notesConfirm supported fields, folders, tags, passkeys, and shared items
Browser exportMoving saved website usernames and passwordsCheck duplicate entries, incomplete URLs, and whether the export contains sensitive data in plain text
CSV or spreadsheetHighly customized records or older collectionsMap column names carefully and remove unrelated columns before import
Manual entryA small number of high-value accountsVerify each username, website address, note, and two-factor method

Before exporting, close unrelated applications and save the file only to a location you control. An export may contain readable passwords. Import it promptly, confirm the result, then delete temporary copies from the computer, downloads folder, cloud sync locations, and recycle or trash folders where appropriate. If you use a work computer, follow your organization’s data-handling rules.

Organize the vault

Use a simple structure that makes the correct credential easy to find. Separate personal, household, work, infrastructure, finance, and recovery records when those categories need different access controls. Use consistent names such as “Service — account purpose” rather than relying on a vague title like “Login.”

Keep secure notes with the account they describe. Examples include support contacts, subscription details, device serial information, backup codes, or instructions for rotating a credential. Do not place secrets in ordinary notes, email drafts, screenshots, or unprotected text files.

After the first import, search for duplicates, old accounts, empty entries, and passwords marked as reused or weak. Change credentials at the service itself; editing a password record alone does not secure the underlying account.

Set up browsers, phones, and passkeys

Install the browser extension only in browsers you trust, then check its autofill settings. Many managers allow separate controls for usernames, passwords, payment details, addresses, and one-time codes. Start conservatively: enable only the categories you need and review the confirmation prompt before submitting sensitive information.

On a phone or tablet, select the password manager as the system’s autofill provider if required. Test it in a low-risk account first. If autofill does not appear, check that the app is unlocked, the correct provider is selected, the browser or app is supported, and accessibility or keyboard settings have not disabled the prompt.

Passkeys may be stored in the manager, on a device, or through another platform credential provider, depending on the service and operating system. When creating one, note where it is saved and whether another approved device can use it. Do not remove the old sign-in method until you have tested the passkey and confirmed a fallback.

Share access without sharing your master password

Use shared vaults, collections, delegated access, or an equivalent built-in feature instead of sending passwords through chat or email. Share only the specific credential or group required. Keep personal credentials outside shared areas, and review whether recipients can view, edit, or manage access.

For household or team onboarding, agree on naming, ownership, access removal, and what happens when someone leaves. Rotate credentials when access changes if the service does not support individual sign-ins or reliable access revocation.

Plan and test emergency recovery

Choose a trusted emergency contact or recovery method only after understanding its waiting period, approval process, and scope. Emergency access should not become an untested assumption. Write down the steps a trusted person would follow, without putting the master password in an exposed document.

Run a recovery test using the manager’s supported process. Confirm that you can reach the required email address, authenticator, recovery codes, or approved device. A recovery plan that depends on one lost phone, one outdated email address, or one inaccessible computer is incomplete.

What to double-check

  • Import accuracy: Open several important accounts and compare the saved username, website address, password, notes, and one-time-code information.
  • Autofill destination: Check the domain before accepting a suggestion. A familiar brand name does not prove that the page is legitimate.
  • Device coverage: Sign in on each supported computer and mobile device, but remove old devices that no longer need access.
  • Passkey location: Identify which provider stores each passkey and test sign-in after signing out.
  • Shared access: Confirm that each person has the minimum permission needed and that departed users no longer retain access.
  • Exports: Know how to create an export, where it is stored temporarily, and how to protect or destroy it afterward.
  • Recovery: Test the actual recovery path instead of assuming that a saved code or backup device still works.

Common mistakes

Deleting the source too soon: Keep the original collection until critical records and recovery details have been checked.

Importing a raw file into cloud storage: A plain-text export can be readable by anyone with access to that location. Use a controlled, temporary workspace and clean up copies.

Putting every credential in one shared vault: Shared access is convenient, but personal banking, recovery, and private work accounts usually need separate controls.

Confusing a changed vault entry with a changed account password: Update the service first, then save the new credential in the manager.

Relying on autofill without checking the site: Review the domain and account context before filling or submitting information.

Enabling extra security without a recovery route: Multi-factor authentication, passkeys, and device approvals are valuable only when you can replace a lost device or credential through a documented process.

When to revisit

Return to this checklist whenever you add a device, change browsers, replace a phone, migrate to another password manager, or onboard or remove a household or team member. Revisit it after a major manager update when import formats, passkey behavior, browser support, emergency access, or sharing controls may have changed.

Set a recurring review at least twice a year, and perform an extra review before travel, a seasonal planning cycle, a device replacement, or a change in work responsibilities. During each review, remove unused accounts, audit reused passwords, confirm recovery contacts and codes, inspect shared access, and test one recovery path. If your organization manages the password manager centrally, align this review with its current configuration and offboarding process.

The practical final step is to record the date of your last successful recovery test and the devices currently authorized. That small log gives you a clear starting point the next time an account, device, browser, or workflow changes.

Related Topics

#password managers#account security#passkeys#autofill#password vaults#emergency recovery
M

Manuals.top Editorial Team

Technical Editors

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.