Protect what matters – even after you're gone. Make a plan for your digital legacy today.
How to Migrate 1Password Vaults to Bitwarden Folders (With Passkeys!) using iOS 26 CXP
I just finished migrating my credentials from 1Password to a fresh Bitwarden setup, and I wanted to share a workaround for a major pain point regarding vault organization and Passkeys. Those who used 1Password v7 will remember that exporting by vault was standard. In v8, this has been reduced to an "all-at-once" account export. If you want to maintain your organization during a move, this creates a mess. The Challenge: Maintaining Structure If you have multiple vaults (Work, Personal, Shared, etc.) and want them to land in specific Bitwarden Folders, an "all-at-once" export creates a massive, unorganized pile. Plus, standard file exports (CSV/1PUX) usually break Passkeys. The Solution: The "Single-Vault Pipeline" (iOS 26 CXP) By using the newly introduced Credential Exchange Protocol (CXP) on iOS 26, you can move your data app-to-app, vault-by-vault, and keep your Passkeys intact. (Note: I used a 1Password Family account and a free Bitwarden account for this). The Migration Manual: Prep 1Password (Web Browser) Log into 1Password.com on a desktop. Go to Manage Account > People > Select your account > Manage Vaults. The Trick: Deselect all vaults until only one is left visible to your user. Now, your mobile app will only "see" that specific vault. The CXP Transfer (iOS Device) Open the 1Password app on your iPhone/iPad. Navigate to Settings > Advanced > Start Export. Enter your account name (there is a hint at the bottom) and approve. Select Bitwarden as the destination. It will open Bitwarden and securely transfer everything from that one visible vault—including Passkeys and TOTP seeds. Assign to Folders (Bitwarden Desktop) Open the Bitwarden Web Vault on your computer. Click on "No Folder" (this shows all the items you just imported that don't have a folder assignment). Click the "Select All" checkbox at the top. Click the three dots (⋮) above the list > Add to Folder. (Note: You’ll need to create the folder first by pressing the + New button). Rinse and Repeat Go back to the 1Password web interface. Deselect the vault you just finished and select the next one. Repeat the iOS export. Because Bitwarden treats these as new "unassigned" items, you can neatly move the next batch into the correct folder. Why this is the optimal way: Passkeys & 2FA: Unlike file exports, CXP moves the actual cryptographic keys for Passkeys and your TOTP seeds. Shared Protocol: Because it uses a modern exchange protocol, misc info and custom fields transfer much more accurately than a messy CSV. Organization: You don't have to manually sort 1,000 items at once. You do it in controlled, vault-to-folder chunks. Hope this helps someone else stuck in the migration process!
I cannot acces my data anymore
after an update I cannot access my data anymore. 1password opens with facecheck and leads me to a page wirh the options to add my account or use a 14 day test version. I know my Password, but not the secret key asked for. Is there any option to reset the software and unlock it by facecehck again?1Password deployment on VDI / Citrix environments - best practices and support status?
Hi everyone, We're evaluating 1Password for our organization and need to deploy it in a Citrix Virtual Apps and Desktops environment. I've read through the deployment documentation, but I'd like to get some clarity on a few points from the community or 1Password team. Our scenario: Citrix Virtual Apps and Desktops (mix of persistent and non-persistent VDI) Windows Server-based session hosts User profiles managed via FSLogix / Citrix Profile Management Questions: Non-persistent VDI: What's the recommended approach for non-persistent/pooled desktops where the VM is reset after each session? Is it sufficient to persist the local data folder via FSLogix or Profile Management, or are there additional considerations? Multi-session hosts (RDSH): Is 1Password supported on multi-session Windows Server environments where multiple users share the same server? Are there any known limitations? Browser extension: Does the browser extension work reliably in VDI scenarios, especially when connecting to a locally installed 1Password app on the virtual desktop? Installer choice: The documentation mentions that MSIX is preferred over MSI. Are there specific VDI-related reasons for this recommendation beyond the passkey limitation? Any insights from organizations running 1Password in similar environments would be greatly appreciated. Thanks!1Password’s new benchmark teaches AI agents how not to get scammed
In 2024, a research team found that GPT-4 could identify phishing websites with near-perfect accuracy. Ask a modern AI model, “is this email dangerous?” and it almost always gets it right. Unfortunately, an AI model’s ability to recognize threats does not translate to an AI agent’s ability to avoid them. AI agents can read your inbox, open links, read secrets on your computer, forward emails, and fill out forms on their own. The problem is what they could do next: open the phishing link, pull your real password from the vault, and type it into the attacker’s fake login page. That’s not a hypothetical. In our testing, one of the most capable AI models available today did exactly that, ten seconds after being asked to check the inbox. To address this risk, we’ve built the Security Comprehension and Awareness Measure (SCAM): an open-source benchmark that tests whether AI models can stay safe when they’re actually doing things like reading emails and filling in passwords. Read the full post and explore SCAM here: https://1password.com/blog/ai-agent-security-benchmark https://1password.github.io/SCAMUser with 1000s of Devices
Hello, I have a question regarding how the 1Password integration with Linux terminals works. We’ve noticed that several employees have over 1,000 devices associated with their accounts in their linked account history, with the vast majority being Linux terminals. Is this expected behavior, or is it something we should be concerned about? Thank you for your insight.
Rename a SSO "supported provider"
I have multiple Google accounts/emails (pers+work+aliases) and if I let 1password register a connection it will only show as "Signs in with Google" So I cannot know when trying to connect, which Google account it may try to use or was registered. On some services I may have multiple accounts, and use username/password for one account, SSO for another. Am I missing something to make the "Google" more descriptive?
