The Death of the CSV: Google Overhauls Android Credential Migration to Eliminate Plaintext Security Risks

MOUNTAIN VIEW, Calif. — In a move set to redefine the security and usability of digital identity management, Google has launched a revolutionary password and passkey migration system for Android. Announced on September 10, 2026, this new framework entirely bypasses the traditional, highly insecure practice of exporting credentials into plaintext Comma-Separated Values (CSV) files.

By coordinating direct, encrypted app-to-app transfers at the operating system level, Android now allows users to transition their digital vaults seamlessly. Crucially, the update also supports the secure migration of passkeys—a cryptographic credential type that was previously notoriously difficult, if not impossible, to move between competing password managers.

Executive Overview

For over two decades, migrating from one credential manager to another has been one of the most fraught procedures in personal cybersecurity. Users looking to switch services were forced to export their entire digital lives—usernames, passwords, security questions, and sensitive notes—into an unencrypted, plaintext CSV file. This file would sit in local storage, highly vulnerable to malware, accidental cloud synchronization, or physical theft, before being manually uploaded to a new provider.

Google’s new Android migration protocol, rolling out to all devices running Android 8.0 (Oreo) and above, solves this systemic vulnerability. By leveraging secure Inter-Process Communication (IPC) brokered directly by the Android operating system, users can now initiate a local, encrypted transfer of their vault from one application to another with just a few taps.

[Legacy Method: HIGH RISK]
Old App ──(Unencrypted Plaintext)──> CSV File in Downloads ──> New App

[New Android Method: SECURE]
Old App <──(OS-Brokered Encrypted Handshake)──> Android OS <──> New App

At launch, the ecosystem boasts day-one support from the industry’s most prominent credential managers, including 1Password, Bitwarden, Dashlane, and Google Password Manager. This coalition of industry leaders underscores a collective commitment to eliminating the friction and security hazards associated with credential portability.

Detailed Chronology of a Secure Transfer

The new transfer mechanism represents a paradigm shift in how sandboxed applications interact on a mobile operating system. Traditionally, strict sandbox barriers prevented apps from accessing each other’s data storage to protect user privacy. Google’s new framework bridges this gap safely by acting as a secure, OS-level broker.

+-------------------------------------------------------------+
|                     MIGRATION FLOW                          |
+-------------------------------------------------------------+
|  1. User opens target app (e.g., Bitwarden)                 |
|  2. Selects "Import from another manager"                   |
|  3. Android OS detects source app (e.g., 1Password)         |
|  4. Biometric authentication requested to unlock source vault|
|  5. User reviews and approves credentials to be moved       |
|  6. Encrypted, direct transfer completes locally            |
+-------------------------------------------------------------+

Step 1: Initiation within the Target App

The process begins when a user downloads and opens their new password manager of choice (the target app). Upon navigating to the settings or onboarding screen, the user selects the option to import credentials.

Step 2: OS-Level App Detection and Handshake

Instead of prompting the user to locate a file on their device, the target app calls a specialized Android system API. Android scans the device to identify compatible source password managers installed on the system. The OS then presents the user with a list of verified source applications currently holding their credentials.

Step 3: Biometric Authentication and Decryption

Once the user selects the source app, Android initiates a secure handshake. The source app is launched in a secure background state, prompting the user to authenticate using their device’s biometrics (fingerprint or facial recognition) or system PIN. This ensures that the migration cannot be triggered silently by background malware or unauthorized users.

Step 4: Granular Review and Consent

Before any data changes hands, the system presents a unified interface showing the user exactly what is being prepared for transfer. Users can review the list of accounts, passwords, and passkeys, and selectively deselect specific entries if they wish to clean up their vault during the migration.

Step 5: Direct, Local Encrypted Payload Delivery

Upon final user approval, the source app packages the selected credentials into an encrypted payload. This payload is handed directly to the target app via the Android OS broker. The data never touches the device’s public storage directory, is never written to disk in unencrypted form, and is never uploaded to any intermediary cloud server during the transfer process. The target app decrypts the payload, populates its database, and the migration is complete.

Supporting Context & Cybersecurity Metrics

To appreciate the significance of this update, one must examine the severe security risks associated with legacy migration practices and the technological hurdles that previously blocked passkey portability.

The Inherent Danger of the CSV File

The CSV file format has long been the Achilles’ heel of password management. Because CSV is a simple, unencrypted text format, any file generated during an export contains a user’s entire digital footprint in plain text.

Cybercriminals have long optimized malware to exploit this exact vulnerability. "Infostealer" malware strains are specifically engineered to continuously scan standard device directories—such as /Downloads or /Documents—for files matching patterns like passwords.csv, vault.csv, or 1Password_export.csv.

According to cybersecurity telemetry reports, credential theft via local infostealers remains one of the primary vectors for enterprise network intrusions and personal identity theft. By removing the physical CSV file from the equation, Google has effectively closed a massive attack surface.

Unlocking the Passkey Bottleneck

While passwords can be represented as simple text strings in a CSV file, passkeys cannot. Built on the WebAuthn standard, passkeys rely on public-key cryptography. A passkey consists of a public key registered with a website and a highly secure private key stored within the user’s credential manager.

Because these private keys must be kept strictly confidential to prevent cloning, they cannot be exported into a text file. Consequently, users who adopted passkeys found themselves "locked in" to their specific credential provider. If a user wanted to switch from Google Password Manager to a dedicated third-party tool like Dashlane, they faced the grueling task of visiting every single account online, deleting the old passkey, and registering a new one.

Google’s new migration framework solves this interoperability crisis. By establishing a secure, cryptographically verified pipeline between sandboxed applications, the private key components of passkeys can now be safely packaged, transferred, and imported into a new vault without exposing the cryptographic secrets to the wider operating system or external threats.

Official Statements and Industry Alignment

This release is the result of extensive collaboration between Google and the broader password management industry, largely organized under the auspices of the FIDO Alliance and the World Wide Web Consortium (W3C).

In statements detailing the rollout, industry leaders emphasized that user autonomy and security must go hand-in-hand:

"The ability to choose your own security tools is a fundamental tenet of digital safety," said a spokesperson for Bitwarden. "Historically, the friction of moving passwords—and the outright impossibility of moving passkeys—acted as a barrier to user choice. By partnering with Google on this new Android framework, we are giving users the freedom to select the password manager that best fits their needs, without compromising their security during the transition."

1Password echoed these sentiments, highlighting the elimination of the CSV file as a major milestone:

"For years, we have had to warn users about the dangers of the CSV files they generated when migrating to 1Password. It was a necessary evil of the open web. This new API changes everything. We can now welcome Android users to our platform through a process that is not only faster but fundamentally secure from end to end."

By building this feature directly into the Android platform, Google has also addressed potential antitrust and anti-competitive concerns, demonstrating that it is willing to let users easily migrate away from its native Google Password Manager to third-party competitors.

Future Outlook: The Path to a Passwordless Era

The introduction of secure credential and passkey migration on Android 8+ is poised to accelerate the global adoption of passkeys. Up until now, the fear of vendor lock-in was a significant deterrent for tech-savvy users and enterprise IT administrators hesitant to deploy passkeys across diverse device fleets. With portability solved on the world’s most widely used mobile operating system, a major obstacle to the passwordless transition has been dismantled.

The industry’s attention now shifts to Apple and the iOS ecosystem. While iOS offers robust credential auto-fill capabilities, it currently lacks a comparable, open API that allows direct, secure, app-to-app migration of both passwords and passkeys without intermediary files or cloud sync workarounds. Security advocates anticipate that Google’s proactive implementation will pressure Apple to introduce a similar, interoperable standard in future iOS iterations.

As the FIDO Alliance continues to refine credential exchange specifications, Google’s new Android migration framework stands as a real-world proof of concept. It proves that the tech industry can collaborate to build systems that prioritize both user convenience and ironclad security, bringing the digital world one step closer to a safer, post-password future.