Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
Solved
Is MrC Converter Suite still available?
Hi, I see some references to this suite to assist with migrating to 1Password when searching for guidance on migrating from Keeper. Unfortunately, all the links I find are from the old support comm...
Hi Folks,
Sorry for the delay in responding; I'm just catching up from being out of town for the past two weeks, and getting used to the new forum.
The suite is still available in the same Dropbox location:
https://www.dropbox.com/scl/fo/b65rvwp16c7d9tjs13gt2/AKBtHtOJ7tQz-buum6Wl24Q?rlkey=c9jjjq2e02bti7xuz81k49cwx&dl=0
Before the forum conversion, I copied the content of the main thread. Now I need to decide how I want to replace the info that was contained on that page.
I'm here if you have any questions.
You're welcome.
There are a couple of reasons why I've avoided distributing via GitHub. I've mentioned these on the forum here, but these are now lost due to the migration to this new platform. Here are a few:
- GitHub's landing page is not well suited to non-technical users, the primary audience of the converter suite. I needed a simple landing page (admittedly, over time, Dropbox's UI became rather bloated and obtuse).
- My process for building the documentation from the source code and the final archive isn't well-suited to GitHub, and for me would be less efficient and offers little value.
- Over the years I've provided many custom converters for users, and being able to provide these easily to non-technical users has been extremely effective and efficient.
- For user security and confidence, I didn't want random forks and copies of the code around. I've had some repositories taken down from GitHub.
That said, more recently, I have been thinking about this, but I've been too busy this past year to make any headway. Perhaps 2025 will see some progress.
Thanks, that makes sense! I ended up uploading it to a private repository for my team to reference, but Dropbox just seemed unusual for software/script distribution, I appreciate the thoughts. I would argue that documentation is flexible in GitHub and the display of README.md by default along with the ability to build documentation into GitHub Pages (along with all the custom power available via GitHub Actions--which could build the docs from source) beyond that does lend itself to GitHub well but would definitely involve changes.
But I do also get the reasons for not using it, though the change tracking does seem to be a substantial benefit in terms of both seeing what's changed and not having to track downloaded versions over time manually, since it would be simple for advanced users to clone and update the repository to stay up to date--with releases being downloadable by less technical users still who don't understand Git. Regardless, I appreciate the details and time restraints, thanks again! It's a very useful tool regardless of distribution for sure and I very much appreciate the consistent effort over so long!
My documentation build requires a manual step via some macOS licensed software I own. There are special features I use from it to construct the HTML from MD with other meta-markup. It will take a fair amount of time and focus to convert this over to use command line MD conversion tools.
GitHub would definitely help others who use Git and want to track version changes, like yourself. I get this.
My usage of Dropbox is simply that it's ubiquity predated GitHub.
Makes sense. I don't doubt it is probably convertible, but don't doubt the effort will take time if you even want to. (Of course you could convert locally and push to GitHub still, without much issue.)
GitHub and software supply chain/validation efforts have both evolved quite a bit since you started the script, for sure! (I personally finally figured out Git and GitHub about a year ago, despite multiple attempts in the past and a long history of small personal scripting projects going back over 20 years now, and several (bad!) false starts with version control.) I appreciate the additional info, I'm sure we will make-do until you have the time and desire to make changes, just wanted to make sure it had been considered!
Hi, firstly I want to say thank you for all the work you have put into this converter.
I am however having an issue with the converter from mSecure 6 to 1Password 8. I can see the passwords in the exported csv file but it appears most of the passwords are missing after I have done the conversion and imported them (I'm using the helper on mac). Most other fields appear to be correct, username, website, notes are all there, just the passwords are missing for most of the logins. I have successfully used it before to move from an earlier version of mSecure, any ideas?
Hi GreasyWeasel
You're welcome.
I assume the issue is with the Login category. The last columns of a login record will be the URL, username and password. These are generally in the form of three vertical bar (aka pipe) separated values, like this:
Website|2|http://www.exmple.com,Username|7|joe@example.com,Password|8|supersecretsauceThe first thing in the tuple is the label, the second is an mSecure field type ID, and the third is the value. Do you see all three of these? Perhaps you can share a sanitized version of one Login record. The converter is expecting the label to be exactly "Password".
You can enable debug mode by adding the -d option, and that will reveal how fields are matched:
Finally, is your export from and conversion on macOS or Windows? The exports have slightly different formats.
Hi MrC
Thanks for the quick response.
I've looked in more detail based on your advice and it looks like it's missing the last field of any field type, so on Logins it is usually the password that is not being imported but it is there in the csv. But if there is another field after the password field then it will import the password but miss the field that is last on the line.
The export has been done on a Windows PC but I am performing the import on a Mac since the helper makes it easier.
I will continue to investigate further but I wanted to let you know that the issue in the last field on a line rather than just the password.
