Need help moving data from SplashID to 1Password
Comments
-
Please have a look at @MrC's conversion utility referred to in this thread. He's the forums import expert and is exceptionally helpful with import issues. He's often here on the forum.
Stephen
0 -
HI @rkempton,
I think you'll find the README included in the converter download is the step-by-step you are looking for to convert from SplashID to 1Password's importable 1PIF format. Give it a try at the link provided by @Stephen_C above.
See also these similar threads:
https://discussions.agilebits.com/discussion/comment/170085#Comment_170085
https://discussions.agilebits.com/discussion/comment/169459#Comment_169459
0 -
Thank you for that input - I'll check it out.
THANK YOU!
~ Rick ~0 -
You're welcome. I just posted the 1.02 update, so let me know if there are any issues.
0 -
I have tried using your converter (OS10.10.2 YOSEMITE) making corrections as I go along to conform to the specifics of Yosemite, SplashID's export file name idiosyncrasies, etc. at least half a dozen times. None work: This is the Terminal command line result (both folder and pm_export.vid file are on the desktop):
Last login: Thu Feb 12 15:50:48 on ttys001
Henrys-MacBook-Air:~ HM-J$ cd Desktop/convert_to_1p4
Henrys-MacBook-Air:convert_to_1p4 HM-J$ perl5.16 convert_to_1p4.pl splashid -v ../../pm_export.vid
Unable to open VID file: ../../pm_export.vid
No such file or directoryHenrys-MacBook-Air:convert_to_1p4 HM-J$
As noted above, both the correct folder and file (properly named for a SplashID vid export) are on the desktop. So, what is going wrong. (Splash is v.7.22).
Rgds,
H.0 -
Next time you re-write the ReadMe file with these instructions I also strongly urge you to group the Windows and Mac instructions in separate modules/paras and clearly indicate that major changes to the scripts required by each of the password mgrs, such as SplashID, since there are significant differences in the command line script for each and the way they are now organized is very confusing and leads to easy and annoying mistakes
0 -
Hi @henrymj,
Sorry for your troubles. There was a typo in the README, as noted in the update notes in this post (and others):
https://discussions.agilebits.com/discussion/comment/178468/#Comment_178468
Use the command (with one set of "../" removed):
perl5.16 convert_to_1p4.pl splashid -v ../pm_export.vid
0 -
Next time you re-write the ReadMe file with these instructions I also strongly urge you to group the Windows and Mac instructions in separate modules/paras and clearly indicate that major changes to the scripts required by each of the password mgrs, such as SplashID, since there are significant differences in the command line script for each and the way they are now organized is very confusing and leads to easy and annoying mistakes
There's no easy way to do this. I don't want to duplicate sections or content, and a large portion of the instructions are common between platforms. The disparity increased only recently when I updated the instructions to switch from ActivePerl to Strawberry Perl.
Can you expand on what you mean here?
clearly indicate that major changes to the scripts required by each of the password mgrs
And by this:
since there are significant differences in the command line script for each
I assume the word "each" refers to the platforms OS X and Windows.
I didn't chose Markdown as the language to write the README, and unfortunately, it is very limited. Otherwise, I could color-code or otherwise call out Windows vs. Mac portions to help users here.
0 -
I have to migrate my data from Splash ID Safe 8 to 1password. Do I have some hope of success ?
- Gurmy -
0 -
Hi @gurmy,
I just tested the conversion from SplashID for Mac version 8.0.1.826, and it worked.
I also took a look at the differences between two SplashID exports for Windows versions 7.2.4.760 and 8.0.0.834. The changes are minor and the 1.03 converter should handle them. I tested the version 8 conversion and import. It worked. However, one thing to note, once again, the crazy folks at SplashData cannot get encoding correct, so certain characters in your Notes and perhaps other places will be botched upon updating from version 7 to version 8 on Windows.
0 -
Thanks MrC, Export process was completed with success using Windows PC. Step 2d, 2e and 2f cannot be terminated with error=0. I had error after every step, and no step seemed to be completed. But export was done, and 1password for MAC has imported all the records.
The real problem is that most of them have a category type unknown to 1password and was imported like Secure Note.
Manually work is always necessary :)Thanks a lot for your job, wonderful script
0 -
Hi @gurmy.
The output from the steps 2 d-f is chatty for sure, and nigh impossible for non-techies to interpret (error=0 is a GOOD result; 0 means No Error).
As for the records being imported into Secure Notes, have you Edited and changed the names of the stock SplashID Types? If so, then we can adjust the converter to known your new type names.
By the way, this is one of the HUGE problems of customized record types in password managers. Only you can understand their meaning, so export and import into other tools becomes sub-optimal.
0 -
By the way, this is one of the HUGE problems of customized record types in password managers.
No kidding! This fact caused me to start all over from scratch when I moved to 1Password, rather than deal with what seemed like random importing from my earlier manager. As a result, I've stopped wishing for the ability to customize categories and I refrain from adding custom fields in 1Password now.
There were some benefits to starting over. I got rid of old relic records that had outlived their usefulness. But it was still painful.
0 -
OK, after deleting the superfluous ../ from the script, the import worked... sort of. There seems to be no way to simply drag and drop records from one category to another (even though most of the data the import captured went into the notes section, it would be a lot easier to cut and paste WITHIN a category than try to move item by item between categories!).
0 -
Regarding the need for a rewrite: you shouldn't care how much is redundant! It doesn't matter: make it easy for the user to get all the info he needs (and correct the wrong info such as the ../ mistake) in one place and not have to hunt for slight changes somewhere down the page... It doesn't cost you anything to cut and paste what is the same, but it costs the user a hell of a lot of time and grief to think he has it all when he doesn't and has gone through half a dozen iterations wondering why the damned script doesn't work!
0 -