That sentence is the sign-in prompt shown by a browser or password manager when you start a sync or import; it's asking for permission to sign you into an account and pull your saved passwords, bookmarks, and settings onto this device. The "more" covers browsing history, open tabs, autofill entries, and payment methods.
The catch: it appears in at least three different products, and each one handles your data differently. A browser sync prompt, a standalone password manager import, and an operating-system credential transfer all look similar on screen. Reading the fine print on that particular dialog tells you which one you're in.
Google's own support documentation, Microsoft's account pages, and Apple's iCloud Keychain guide each describe a different data set behind nearly identical wording. Before you press the blue button, confirm the vendor. The next nine sections run through what's typically included, what's usually left behind, and what breaks when the transfer stalls.
What the Sign-In Prompt Actually Asks Before You Tap Continue
The prompt is a consent dialog, and its legal weight varies by product. In Chrome and Edge, syncing your passwords to a Google or Microsoft account stores them on that company's servers, encrypted with a key tied to your sign-in. In a dedicated password manager, the same wording typically means importing a local file, and the file never leaves your device. Same words, opposite privacy outcome.
Underneath the friendly phrasing sits a permission scope. Chrome's sync offers granular toggles that let you sync passwords without also syncing history or autofill. Edge labels the equivalent setting "Sync" with separate switches. Apple's iCloud Keychain prompt rolls passwords and passkeys into one toggle that you can't split without disabling the whole keychain. If a family member shares an Apple ID, that toggle also exposes their keychain to the same account.
The prompt usually names the account email in bold at the top. Check it. A second Gmail address, an old Microsoft account from a work laptop, or a shared family Apple ID is a common reason people "lose" their saved passwords after signing in. They signed into the wrong account, and the correct credentials sit under a different address entirely.
If the email shown doesn't match the one you actually use for saved passwords, cancel and switch accounts first. Signing in twice is faster than recovering deleted sync data, and Google's account recovery for a wrong-account sync takes days rather than seconds.
Which Products Show This Exact Wording and What Each One Transfers
Four mainstream products use near-identical language: Google Chrome, Microsoft Edge, Apple's iCloud Keychain, and dedicated managers like 1Password or Bitwarden during first-run import. The wording overlaps, the data sets don't.
| Product | Triggers the prompt | Passwords included | History included | Autofill / payment | Syncs to cloud |
|---|---|---|---|---|---|
| Chrome (Google account) | First sign-in on a new device | Yes, via Google Password Manager | Yes, if toggled | Yes, if toggled | Yes |
| Edge (Microsoft account) | First sign-in on a new device | Yes, via Microsoft account | Yes, if toggled | Yes, if toggled | Yes |
| iCloud Keychain (Apple ID) | Enabling Keychain on a new Mac or iPhone | Yes, plus passkeys | No (Safari history separate) | Card info only if added to Wallet | Yes, end-to-end encrypted |
| 1Password / Bitwarden import | Manual import, not a sign-in dialog | Yes, from a CSV or 1PIF file | No | No | Yes (or self-hosted) |
The table reveals a divide. Browsers sync history and passwords together because they live in the same profile store. Apple splits them. Password managers ignore history entirely, which is why importing into Bitwarden won't restore your Chrome browsing history even though the prompt said "and more."
If history is what you actually want, browser sync is the only tool that carries it across devices. If passwords are the only thing you care about, a dedicated manager is a better destination and the "history" line in the prompt is essentially noise you can ignore.
The Password History Feature Most People Miss Inside the Sign-In Flow
Once signed in, most managers keep a version history for each saved password entry, and that history is separate from your browsing history. Google Password Manager, for example, shows a "Password changed" timestamp on individual entries but doesn't expose prior values unless you've enabled the option in Chrome's settings. Bitwarden and 1Password both keep per-item password history accessible from the item's detail view.
This matters when a sync conflict overwrites a password. Say you change a bank password on your phone, then sign into Chrome on a laptop that still has the old value, and the sync pushes the stale one to the server. The current password is gone from the active field, but the history log preserves the older and the newer value so you can identify which one works before locking yourself out.
Browser-based password history has limits. Chrome's password manager does not store deleted entries indefinitely β removing a saved password removes its history too. If you delete the entry to "clean up" and later need the old value, it's gone. Exporting a CSV backup before any bulk cleanup is the workaround, and Chrome's export function lives under Settings, then Autofill and passwords, then Password Manager, then Settings on the manager's own page.
A failure case worth knowing: if you import a CSV into a manager and the CSV contains duplicate usernames for the same site, most managers keep only one entry and silently discarding the others. Check the entry count before and after import; the numbers should match or the missing rows are your old passwords.
Bookmarks, History, Autofill, and Cards: What "and More" Covers
The "more" is the vaguest part of the prompt. In Chrome, the sync bundle covers bookmarks, history, extensions, settings, themes, open tabs, addresses, phone numbers, and payment methods β nine categories, and each has its own toggle. Edge mirrors this list with "Favorites" instead of bookmarks and adds collections. Apple syncs Safari bookmarks and Reading List but keeps history separate, and iCloud Keychain carries passwords and passkeys only.
Payment method sync is the category people forget. Chrome can store card numbers and expiration dates in your Google account, and syncing them means every signed-in Chrome instance can autofill the card. That includes a shared or family device. If you lend your laptop to a guest, they can check out with your saved card without knowing the number.
Bookmarks sync is usually the least risky and the most useful for people moving between machines. A job change is the classic case: you sign into Chrome on the new work laptop to pull your bookmarks and saved logins, and every personal account you saved on the old machine lands in a browser tied to your work profile. Sign out of the browser after the initial sync, or create a separate Chrome profile for work.
Transferring Passwords from Chrome to a Dedicated Manager Step by Step
Browsers lock you into their sync if you let them, so the safest migration is export-then-import. The steps below are Chrome on desktop as of Chrome 120 and later; Edge and Safari have equivalents under similar names.
1: Open Chrome and go to chrome://password-manager/settings. 2: Click Export passwords, then confirm with your OS password or biometric. 3: Save the CSV somewhere short-lived, like your Downloads folder β the file is unencrypted plaintext. 4: Open your manager (Bitwarden, 1Password, or similar), go to its import screen, choose "Chrome (CSV)" as the source, and upload the file. 5: Review imported entries against the export count. Delete the CSV securely after import using your OS's shred or secure-delete tool.
If the import throws a "column mismatch" error, the CSV's header row was likely edited by Excel or Google Sheets before upload. Both apps rewrite the header when you save, dropping the name,url,username,password order the manager expects. Re-export and import directly without opening the file in a spreadsheet.
A real failure case: Chrome's export only includes entries saved to your Google account, not any passwords saved under a passphrase-protected profile. Passphrase users must unlock or disable that protection first, or the CSV will come out empty and you'll assume the passwords are gone.
Sync Conflict Rules: What Happens When the Same Account Exists Twice
When you sign in on a second device, the sync engine has to merge two copies of the same credential store. Each product resolves this differently, and the wrong assumption costs access. Chrome keeps both versions and flags one as "conflicting" in the password manager, letting you pick which to keep. Edge keeps the newer timestamp and silently overwrites the older value. iCloud Keychain pushes the most recently modified record across devices.
Password managers offer a real advantage here. Bitwarden shows the conflicting entry inline with both username and password values side by side. 1Password keeps the older value in the item's history and presents a "which one do you want" dialog. Both leave you with a record.
The vulnerable window is the device that hasn't synced yet. If you change a password on your phone and the laptop is offline when you sign in, the laptop has the old value. Chrome's merge rule protects you; Edge's overwrite rule may flip the value back to the old one if the laptop's timestamp is later for any reason β including clock drift.
A contradiction worth naming: Google's support pages describe Chrome sync as "keep everything in sync," while the conflict UI implies duplicates can survive. Both are true. The UI exposes conflicts the sync engine can't auto-resolve, and "in sync" means consistency across devices, not deletion of duplicates.
The Exact Settings That Decide Whether Your History Leaves the Device
The toggle page in Chrome sits under Settings, then You and Google, then Sync and Google services. Each syncable category has a switch. Turning off history sync doesn't delete existing synced history; it just stops future uploads. Turning off passwords but leaving history on gives you a strange hybrid profile where the browsing record travels across devices but credentials don't.
Edge's equivalent lives under Settings, then Profiles, then Sync, and Microsoft account data travels to the same Microsoft account used for Office and Xbox. On a shared PC, that's the whole household's data in one account, not just yours.
Apple's iCloud setting is under Settings, then your name, then iCloud, then Passwords and Keychain on iOS. Disabling Keychain asks whether to delete the keychain from the device or keep it locally on that device only. Choosing "delete from device" doesn't delete it from iCloud or other devices, but it does leave the current iPhone without the saved passwords it had before.
If your goal is stopping history upload but keeping password sync, remember that browsers treat these as independent switches only in sync-enabled mode. In some enterprise-managed Chrome profiles, an administrator forces both on and the toggle is greyed out.
When the Sign-In Fails: Expired Tokens, Wrong Accounts, and Locked Vaults
The prompt sometimes returns an error before the transfer starts. A "sign-in expired" message usually means the OAuth token aged out while the dialog sat open; close the tab, reopen the sync settings, and try again. An "account not found" message commonly means the address was typed with the wrong domain, like a work .com when the personal account is .co.
A less obvious failure: a password manager's import screen may ask you to master-password-authenticate before the import. If the master password was changed on another device, the vault is locked and the import stalls silently. Re-authenticate with the current master password, not the one the browser remembers.
The most painful failure is the sync loop. You sign in, sync starts, the browser crashes mid-sync, and the next launch shows the prompt again on the assumption that sync never completed. Chrome's sync internals page at chrome://sync-internals shows whether the server holds your data, but the visible UI just keeps asking. Waiting for the "sync complete" indicator before closing the browser is the fix.
Lockout is the genuinely risky edge case, especially with iCloud Keychain. If you sign into an Apple ID you've forgotten the password to, Keychain remains inaccessible until you recover the account through Apple's recovery flow, which can take days to weeks. Verify the account first from a device you already trust.
Comparing Sign-In Behaviour Across Chrome, Edge, and iCloud Keychain
These three products prompt identically but offer different controls, different scopes, and different failure modes. Where the same feature scores differently, the deciding factor is usually how much the vendor segments the data.
| Dimension | Chrome | Edge | iCloud Keychain |
|---|---|---|---|
| Account email shown in prompt | Yes, in bold | Yes | Yes, plus Apple ID recovery hint |
| Passwords and history separable | Yes, per-category toggles | Yes, per-category toggles | No, Keychain is one toggle |
| Passkeys supported | Yes | Yes | Yes |
| Export format | Encrypted or CSV | CSV | Not supported directly; use a Mac export |
| Conflict visible to user | Yes, in Password Manager | Auto-overwrite | Auto-merge, oldest overwritten |
| End-to-end encryption default | Optional, via passphrase | Optional, via Microsoft account | On by default |
| Family-shared account risk | High, if account shared | High, if account shared | High, Keychain is account-wide |
Chrome offers the most granularity but its end-to-end encryption is opt-in. iCloud Keychain offers the strongest default encryption but the least control. If privacy wins, Apple; if flexibility wins, Chrome; if you're inside Microsoft's ecosystem, Edge is the sane default and you accept the auto-overwrite.
Behaviour-Changing Settings to Set the Day You Sign In
The moment right after sign-in is when settings get frozen by habit, so change the ones that matter before you close the tab. In Chrome, turn on the passphrase for sync, which is the only way to make the synced data end-to-end encrypted rather than encrypted-at-rest. Without the passphrase, Google can technically decrypt synced data for support purposes per its policy. Recovering the passphrase is your responsibility, and losing it removes synced data from your view until you reset sync entirely.
In Edge, disassociate browsers you don't need on the Microsoft account. Microsoft's account device list lives at account.microsoft.com; removing the device doesn't delete data but does stop sync from resuming on that device if you misplace it.
In 1Password or Bitwarden, turn on item history retention and set the retention window. Bitwarden's free tier keeps one password per entry; premium keeps more, per Bitwarden's pricing pages checked at purchase time, and the setting is in the item's advanced section.
Finally, sign out of the sync after the initial transfer if the device is temporary. A borrowed laptop, a hotel business centre, or a friend's machine that you needed once for a file: sync once, copy the file, then sign out and clear local data.
FAQ
What does "bring over your passwords history and more" mean in a sign-in prompt?
It means the product intends to copy your saved passwords, your record of password changes where it stores them, plus other profile data β bookmarks, browsing history, autofill entries, and saved cards β from the account onto this device. The word "history" refers to password-change history or browsing history depending on the product showing the dialog. Check the account email before accepting.
Why does Chrome ask me to sign in again even after I already synced?
Chrome's sync token expires after 90 days of inactivity on that device, so it re-prompts to re-authenticate. If you see the prompt on every launch, the sync session isn't completing β check chrome://sync-internals to confirm whether the server holds your data. A failing sync also fires the prompt repeatedly.
Will signing into a shared family Apple ID expose my saved passwords?
Yes. iCloud Keychain is account-wide, and there's no per-device or per-person split inside a single Apple ID. If a family shares one Apple ID for App Store purchases, the same keychain is accessible to everyone signed in with that ID. Apple's recommended setup is Family Sharing, which gives each person their own Apple ID and keeps keychains separate.
Can I transfer my Chrome passwords to a new password manager without exposing them?
Yes, but the export file is plaintext CSV and is readable by anyone with access to your disk for the minutes it exists. Export to a folder, import immediately, and securely delete the file. Chrome's export does not include passphrase-protected passwords until you unlock the protection, so the exported count may be lower than the saved count.
What is the difference between password history and browsing history?
Password history is the record of past values for a saved credential; browsing history is the log of sites you visited. Browsers treat them as separate data categories with separate sync toggles. Apple syncs Bookmarks and Reading List but keeps Safari history out of Keychain; Chrome and Edge sync both under the same account.
How do I stop a failed sync from deleting a working password?
Turn on the per-item history feature in your password manager before bulk changes, and avoid signing in on a device whose clock is wrong. Chrome keeps conflicting entries rather than overwriting; Edge and iCloud overwrite silently. Export a backup before any cross-device sign-in if you're unsure which timestamp will win.
Can signing out of Chrome sync remove my saved passwords from Google?
No, signing out disconnects the device but leaves synced data on the Google account. Deleting the synced data requires wiping the account's sync data in Google's account settings β a separate action from sign-out. On a shared or work machine, sign out is enough to stop further updates, but the remote data survives.
Does importing passwords overwrite existing entries with the same site?
Most managers keep only one entry per username and site, so duplicate usernames in the import cause silent drops. Bitwarden and 1Password prompt on duplicates; some free tools do not. Check the imported count against the export count to confirm nothing vanished during import.