mSecure-Unterstützung
Apple Password app - mSecure CSV fails to import
Thank you for contacting us and I'm sorry for the issue you are experiencing. There are no known issues of this happening for other users, so this should be working correctly. I have just tested this feature out on my Mac and I am not dealing with any issues with this CSV import feature. I first want to know if you are seeing any other error messages besides the missing column labels message? I also want to know if you are using fake data to test this feature in mSecure 6. If the data that you are using is fake, you can share this CSV file to me so I can try this out on my Mac. If it is real data, we will try something different.
I also want to know from what version of mSecure did you export the file? Are you using an older version of mSecure on your Mac?
Hey Mark, sorry, looking back I see that my original posting was missing the first line of text I copied and pasted from an email draft I was writing.
I had installed Mac Sequoia 15.0 public beta that day and was playing around with Apple's password app and wanted to see what happened if I imported a CSV export from mSecure to import in to Apple's Password app. Not sure if they have a bug in the import I was sharing the message of the error I got with their app when attempting to import the CSV from mSecure.
Mike - mSecure
Hi Clif,
I wanted to follow up on this issue to make sure you've either got the issue resolved or to help where I can. In mSecure 6, there is a special command you have to enter at the top of the CSV to make sure mSecure imports the data in the file in the right manner. In the newest version, we added a bunch of new functionality that is mSecure-specific, so if you're importing more generic data, you have to tell it that with a command on the first line of the CSV file. It sounds like you got that sorted out but I wanted to make sure.
Thanks Mike but it's actually the reverse. I'm not importing in to mSecure. I am testing exporting out of mSecure as a test to do an important in to the new Apple Password app in Sequoia. The Apple app is reporting the error:
Passwords could not import passwords from the CSV file because it is missing column labels.
If you exported this file from a password manager, export a new file using different settings and try the import.
Mike - mSecure
Ok, I see. I'm not sure of how this works, because I have not tried importing passwords into Sequoia. However, I'm guessing the problem is that there is too much information that macOS doesn't like in the export. In mSecure 6, there are special characters used to tell mSecure different metadata about the record. You'll see this as IDs, numbers and pipe characters in the different fields in each record or row. mSecure doesn't have a special export option right now, so you would need to remove any of those characters and then fix up the CSV file so that it is formatted in a way that Sequoia accepts.
@Clif - I think I found a work around to get your passwords in the proper CSV format to get into Passwords. Go to your passwords app and add at least one password/login. Then export the file from the Passwords app. This will create a .csv file. Then copy and paste your passwords from mSecure into the csv file and save it. Then you should be able to reimport back to Passwords.
I did it and it worked. I assume there is something in the formatting of the .csv for it to work with Passwords/Sequoia
thank you Greg for getting back to me. At some point after our previous conversations I thought I had come across a note that Apple had not yet implemented the import function but I believe that was still before 18 and 15 had been released but thanks for circling back and coming up with that work around regarding csv formatting!
Having the same issue with MacOS 15.01. Has there been a resolution to the issue.
Mike - mSecure
@Charles Are you saying you're trying to export data from mSecure to import into Apple's Password app?
Yes same issue as described in this thread.
Mike - mSecure
@Charles I'm not sure exactly how this works, because the CSV export feature is specifically designed for any one type importer. The idea is that the data gets exported to a semi-generic data structure, then you would need to fix up the data to be able to get imported into whatever other program you choose. I'm guessing the problem is that there is too much information that macOS doesn't like in the CSV export, which would need to be removed from the data. I don't know exactly what the data is that needs to be removed, and, unfortunately, I'm not aware of any specific documentation about how data is supposed to be formed in order to get imported into Apple's systems.
Mike, I appreciate the reply and explanation. However, it seems to me that mSecure being a Mac based app would have an option to support this new feature in Mac and iOS. I continue to use mSecure as my primary password manager, but like the convenience of the Password feature in the new software. It sure would be helpful to your users if the export feature supported the formats for the new software.
Just to be a voice from outside mSecure, I don't see why they need to get behind supporting what could take some of their customer base. Apple has a way of coming along and integrating features in iOS for instance that have been fertile ground for third party developers. The new Password app is a huge improvement on keychain access for sure but doesn't provide a lot of what mSecure is great at. I've been saving passwords from Safari in keychain for years so when I go to login I typically pick Passwords now for the auto fill but always think of mSecure as my real vault for not just passwords but keeping lots of things secure.
Clif
Tested out importing an mSecure exported CSV file and got an error:
Passwords could not import passwords from the CSV file because it is missing column labels.
If you exported this file from a password manager, export a new file using different settings and try the import.
As far as I can tell I have no way to adjust export settings. But I guess I could figure out what the column labels need to be and edit the CSV as a work around.