Preserving OTPAuth when moving to Apple Passwords
A migration that moves passwords but silently drops verification-code seeds is incomplete. OTPAuth values deserve explicit accounting because they represent a second factor and can be highly sensitive.
What OTPAuth contains
An OTPAuth URI commonly describes the provider, account and secret used to generate rotating verification codes. Treat it as a credential. Anyone who obtains the secret may be able to generate the same codes, so it should never appear in logs, screenshots, support tickets or online checkers.
Why converters lose it
Many simple converters target a five-column Apple file or only the three fields Google requires. If they parse an OTPAuth column but export a smaller schema, the loss can be silent. PortaPass counts one-time-code rows during review and writes Apple’s OTPAuth column for Apple-format output.
Verify the destination
Formats and OS capabilities change. After importing, inspect a small number of accounts that previously had verification codes. Keep the original export in a private location until you have confirmed the destination. If the target does not accept OTPAuth, move those factors through the provider’s supported recovery or setup flow.
Clean up securely
Once passwords and codes are verified, remove all temporary CSV files. Empty Trash or Recently Deleted where appropriate. PortaPass can schedule a local cleanup reminder, but it cannot delete files you saved outside its sandbox.