Hacker News new | ask | show | jobs
by al_borland 20 days ago
I didn’t want to go into too much detail if you were thinking a different route, but since you’re thinking of going with Apple, here are some of the rough edges I remember in the transition.

I exported 1Password to a CSV and imported it into Apple Passwords. I had spend some time cleaning up 1PW first, archiving dead accounts, but the export had everything in a flat file, so I had to go through everything in my archive and delete it from Apple PW.

Custom fields and some other special fields aren’t supported in Apple PW, this is where I had to go through one-by-one and make sure I wasn’t missing anything and add those things to the notes area.

Non-password data in 1PW doesn’t fit well into Apple PW, so I used a password protected Apple Notes file for that. Not ideal, but I didn’t use those things too much. For software registrations, I didn’t bother securing those too much and filed them away as txt files, most were really old anyway.

The CSV export made 2FA pretty obvious, so I could set that up with Apple. I want to say it made passkeys obvious too, but I only had 1 and knew what it was.

I cleaned out Apple Passwords before the import, so it only had app passwords for login-with-Apple. The way they do this leave much to be desired, to the point that I don’t want to use that feature anymore.

After the import I also found that it tried to be smart about handling multiple entries for the same site, or tried to intelligently name stuff based on the website. It got most of this right, but I still needed to clean some things up and do a little investigation to figure out what a few things were and fix them. Some of this was due to importing archived stuff. I did have to go back to 1Password to make sense of some of it.

All-in-all, I did it all over a long weekend. I kept 1PW around for a month to see if I’d need it and I never did.

1 comments

Thank you so much for this!