Can't import from SplashID

tbader

Hi,

just bought 1Password 4 for Mac and wanted to import data from Splash ID. However, it does not work at all.

Here's what I did:

• go to Splash ID 6.2
• choose File / Export / Splash vID
• choose "all records"
• select destination folder and filename
• leave optional password field blank and also choosed "no" when asked if the file should be emailed
• then go to 1password 4
• choosed File / Import
• select Splash ID vID from the file format drop down
• selected above exported file

All I'm getting is a short beep (standard sound) from my mac and that's it. Looking into console gives the following message:

13.11.13 21:38:32,260 1Password[1948]: 405001 [IMPORT:0x600000265a80:] E importFileAtURL:ofType:subtype: | Failed to read import data: Error Domain=NSCocoaErrorDomain Code=261 "Die Datei „SplashID Test2.vid“ konnte nicht mithilfe der Textcodierung „Unicode (UTF-8)“ geöffnet werden." UserInfo=0x618000262880 {NSFilePath=/Users/xxxx/Documents/SplashID Test2.vid/SplashID Test2.vid, NSStringEncoding=4}

I tried also the following:

• Export as Splash vID3
• Export as CSV
• Export with option "all records in current view"
• Export option with or without attachments

No succes.

The only thing I could do was exporting a single record and import it, but I have hundreds of records and don't want to import them one by one...

Anything else I could do?

Thanks for any help!

tbader

I just saw that the editor here scrambles up my post a bit. There should be a line break before every "-"… sorry for the confusing look now.

Doctordun

I am having the same problem. I can't import vid or csv. I really need this to work.

tbader

Well, I need this to start working with 1password, too…

I really would appreciate an official answer to this, because I already bought the software from the AppStore, as they listed on their website an import function from Splash ID. If this feature doesn't work in near future, the software is just useless to me, and then I would like to get my money back.

Anyone form Agile Bits listening here?

Jasper

Hey @tbader and @Doctordun, try using a text editor to re-save your vID file with UTF-8 formatting.

For example, you should be able to open it using TextEdit.app, then File > Save... and for Plain Text Encoding choose Unicode (UTF-8). And then try importing that newly saved file into 1Password.

Doctordun

JasperP......the Mac TextEdit.app would not recognize the .vid format. 1Password see's the file as greyed out on my computer even after selecting the SpashID format. I also brought the .csv into Excel and exported it back out to another file name with csv format selected and 1Password would not recognize it. Nothing that SpashID exports seems to be recognized by 1Password.

Jasper

@Doctordun If you right click on the .vid file and choose Open With > TextEdit (or Open With > Other... and select TextEdit from the dialog window), what happens? Do you have another text editor you could try using such as TextWrangler?

Just to confirm, are you having the exact same issue as described by @tbader in their original post? Someone else who was having that problem said that using a text editor to resave the vID file in UTF-8 resolved that it.

Doctordun

I'm not sure if I am having the exact problem. I just opened the vid with Text Wrangler and saved the file as Unicode (UTF-8). When attempting to import I got a message of 0 items imported / 0 items failed. Bottom line is that I am having to do this one record at a time and I have several hundred.

tbader

Thanks, JasperP, I forgot to mention that I also tried this. The console log says it could not read the file because it wasn't UTF-8. So I opened the vID in Textwrangler and converted it accordningly. No success so far...

Jasper

Sorry guys, I'm not really sure what else the issue could be. Like I said, another user posted that converting to UTF-8 fixed this issue, but I haven't tried it myself.

Hopefully someone from AgileBits is able to help you out soon (though be patient since they've been super busy since the launch of 1Password 4).

The only other thing you could potentially try is downloading 1Password 3, and try importing it there. If it works, then you could just open your keychain created with the old version in 1Password 4. Here's a direct download link if you're interested.

sjk

Hey guys,

Here's the method I've used to successfully import a +900 item file exported from SplashID Safe 6.2 (no attachments) into 1Password 4 (4,0.8 and 4.0.9) on 10.8.5 and 10.9:

• Followed the first five steps under "Here's what I did" from @tbader's original post
• Opened the resulting .vid file with TextEdit and selected File > Save As… (Option-Shift-Command-S)

• In the save dialog window:

  • Changed Plain Text Encoding from Western (Mac OS Roman) to Unicode (UTF-8)
  • Appended -UTF-8.vid to the Save As filename

• Confirmed Use .vid when saving the new file

• Followed the remaining four steps under "Here's what I did" from @tbader's original post

In Finder, the icon for the UTF-8 version of the vID format (.vid) file that successfully imported looked like this:

@Doctordun: Could your vID filename have been missing a .vid extension? And did you export with SplashID vID, not SplashID vID3, format?

@tbader: Have you tried doing the UTF-8 conversion using TextEdit?

@JasperP: Thanks for your assistance here.

If anyone still can't get this working we'd like to get a sample of your data (with personal info masked) to analyze and figure out what the problem is. If that's doable I'll post specific instructions.

Doctordun

Could be my problem is my SplashID version is 7.0.10
Icon does look like what you show above.
OSX version 10.9 Text Edit Version 1.9 (310).
The exported and massaged files are always greyed out when selecting with 1Password import SplashId (vid) format, even though I can select them.
Could be that the operating system and program versions are outpacing your import functions?

sjk

Hi, @Doctordun.

It's still a successful process here starting with exporting from SplashID Safe 7.1 on OS X 10.9, ignoring that the .vid file being selected for importing in 1Password 4 is "greyed out" since it can be selected anyway. Its probably best updating to SID 7.1 since "Mavericks support" is mentioned in its release notes.

I suggest trying this using a small number of items (under 10) exported from SplashID. If you're still stuck then maybe you could send us the originally exported file (minus any personal info) to check here. Duplicating a few items in SID, changing personal info in them, then exporting just those is one way to create a sample file.

Doctordun

Ok, when I do one record, it works. Anything more and it fails. I updated to 7.1 with no luck on the import.
Where would I send the file?
Thank you.....

sjk

Hi, @Doctordun. Sorry the importing is still giving you problems.

It would be best if you can attach an original vID format file exported from SplashID (before any conversion) along with a Diagnostics Report from the Mac that you've been using. Instructions for generating the report and where to send it, with vID file included, are here:

Sending us your Diagnostics Report to help us help you!

Please do not post your Diagnostics Report in the forum, but do include a link to this topic and your forum username in the email so we can "connect the dots" when we receive it. Thanks!

tbader

Hi sjk, thanks for chiming in and helping here, much appreciated!

I initially used TextWrangler to save the file in UTF-8 format. I did now another test with TextEdit, exactly like you described. However, without success. I get now a message that 0 objects have been imported and 0 errors occurred. I will see if I find some time these days to create a sample vid for you so you can hopefully find out where the culprit is.

Let me know if you have new information, or if I can do something else for you. Thanks!

sjk

Thanks for the feedback, @tbader. Sorry to hear you also haven't gotten importing to work yet.

In your original post I noticed the German text from the console output, making me wonder if the results might differ switching to English as the system language. It didn't matter with brief testing after switching to German here.

Let me know if you'd like me to upload a short sample vID format file that successful imports here for you to download and test there. The result could help us isolate where the problem is.

tbader

Hi sjk, yes, you can do that and I will test if it imports correctly. Let me know where I can download the file. Thanks!

Doctordun

Well, with all of this playing around, I've come to a conclusion, that one or more of my SplashId records must be an issue with 1Password. When I export up to 10 records at a time, it imports just fine. When I try the entire database, it fails. So I suppose I will try 20 or 30 at a time until I find a group that won't import.

sjk

Hi, @tbader. Please check your Messages Inbox for details about the sample files.

Hi, @Doctordun. Thanks for the new information. It sounds like UTF-8 conversion of your original SID export is overlooking something that's causing 1P4 import to choke on it. I'm not sure if that could also be @tbader's issue.

tbader

Hi sjk,

Test done and here's my result: the files you provided imported correctly in 1p4. The UTF-8 could directly be imported, the other one I converted with Text Edit to UTF-8, which worked also.

So I created an own sample with Splash ID that fails. Let me know where I can upload or send it to you.

My guess is, either some special characters have problems, like quotation marks, or german characters like äöüß...
Or customized fields / types / categories. Maybe attachments are problematic, too, but I tried to export a version without attachments, which didn't work either.

Looking forward to hearing from you!

sjk

Thanks for the testing and results, @tbader. Now it's seeming more like you and @Doctordun do have the same underlying "special characters" issue.

See post #15 about sending a Diagnostics Report with your vID sample file attached. Thanks again!

tbader

Done! This should help you nailing the bug down! If not, let me know, so I can see if the issue is other related.
Thanks for great support, guys!

sjk

Looks like it's nailed, @tbader. :)

For some reason your exported vID file has -v4.0 instead of -v3.0 in its first line, even though we've both tested with SplashID Safe 6.2. Try changing the first line from:

SplashID vID File -v4.0

to:

SplashID vID File -v3.0

Save it with UTF-8 format, then try importing again… with "toes crossed" for success. :)

Eager to hear your feedback after trying that.

Always a pleasure to help!

hawkmoth

As a former SplashID user in the not-to-distant past, I recall that SplashID doesn't support special characters. That was a source of irritation to international users. Could this be the root cause of these problems? Never mind if this is just a useless random thought.

sjk

Thanks for the non-useless random thought, @hawkmoth. We're still doing plenty of speculation about this. :)

I've used certain "special characters" in SplashID going back several versions that never interfered with its ability to export vID files that could be imported with 1P3/1P4. Based on some testing here those in @tbader's sample file are why -v4.0 instead of -v3.0 appears in the file header. And the 1P4 vID importer seems to work fine after changing it to -v3.0; my hunch it's for the sake of differentiation with the SplashID importer.

hawkmoth

More than a year ago I abandoned my first effort to migrate from SplashID to 1Password because 1Password couldn't import my data. But as I reported elsewhere in this forum, that was most likely because I had extensively modified the database from its defaults over several years of use, dating back to Palm PDA days. I don't remember anymore exactly what happened though. I just know that I had categories that 1Password didn't recognize and also I had categories in which some records had fields that were entirely different from other records in the same category. I don't think there was a complete failure to import my vID file, but what I got into 1Password at the time was just unusable.

I've been following this thread even though I don't have much to contribute, and each time I read another post, I am prompted to wonder if something like an over-customized SplashID database is contributing to the problems.

After resisting the move away from SplashID for a long time, there was enough family pressure to move that I finally manually moved all my data. I didn't enjoy that, so I hope these users don't end up taking that route too.

Doctordun

That is basically what I am reduced to doing. One record at a time. My SplashId database is extensively modified as well and I really want to use 1Password going forward. Pain in the butt, but once it's done, that's it!

hawkmoth

once it's done, that's it!

My thoughts exactly. And do consider the effort to have been worth my time.

sjk

Hi, @Doctordun.

Was the suggestion I gave @tbader in post #26 also helpful for you? By doing that I was able to get the sample multi-item vID file he sent me imported into 1P4.

hawkmoth

@sjk said,

I've used certain "special characters" in SplashID going back several versions that never interfered with its ability to export vID files that could be imported with 1P3/1P4.

Maybe it was Unicode characters that choked SplashID.