Update on migrating from mSecure 6 [Solved]

@netefx7

Tried using MRC Converter Suite (mSecure 5) but got an uncaught error on validating date around line 200. Might want to work this further if MRC is interested.

Can you provide more of the error message so I can take a look?

@netefx7

Ok, this is an easy one to spot.

The converter is trying to convert the credit card's month / year expiration value, but it is seeing the entire string "Expiration Date|11|11/2024" as being that month / year. Since the mSecure CSV export dos not contain any labels, your data must have that label / value as the date data. And clearly that's isn't a "date", let alone a month / year value.

Would this data have been imported by mSecure from some other password manager, or did you add that? I thought I recall that mSecure5 validated date input, but perhaps it doesn't on importing from another password manager.

Either way, I recently updated some of the date conversion routines to better handle such egregious data (normally I like to know when a password manager can create bogus data so that I get reports like yours).

I just updated the development (not release) version of the suite. Can you retrieve that and give it a try? It's in the folder mrc-converter-suite - development version at top level of the download site. Follow the mrc-converter-suite home link here:

https://1password.community/discussion/101693/moving-to-1password-from-another-password-manager

Close your terminal window, toss your existing mrc-converter-suite into the trash, replace it with the unzipped development version I just posted, launch your terminal again, change directories and retry the conversion.

Here is my run with your bad month / year value:

$ perl convert.pl msecure5 /tmp/msecure5_mac.csv -v
Import summary:
   11 items discovered
Export summary:
    1 Bank Account item
    1 Credit Card item
    1 Email Account item
    1 Reward Program item
    2 Login items
    2 Membership items
    3 Secure Note items
   11 total items
You may now import the file below into 1Password 8:
    /Users/cappella/Desktop/MCS_converted.1pux

Progress...

@netefx7

In order to get you a converter as quickly as possible, I'll focus on what you need for your data, and will flush out the converter later.

I'm working first on the stock Templates (and these will map to 1Password "Categories"). I've completed Login, Credit Card, Secure Note, Bank Account. I'll now add the other stock templates you list (Prescription, Combination, Frequent Flyer, Email Account).

For your custom templates, I'll need to know how you want them mapped into 1Password's categories (without this, they will end up as Secure Notes and many will anyway). Your custom templates are: Computer Login, Serial Number, Account, Frequent Flyer Hotel.

The converter currently is matching the field labels within each item to map these into 1Password's field's for a category. So if you've changed those labels, we'll have to add the appropriate pattern into the converter's field label pattern match definition. You'll know this when you examine the results, and we can adjust accordingly.

Is the "Name" field in Prescription a person's name, or a medication name?

@netefx7

OK on the mappings. I need to know the exact field names of those templates (case sensitive).

Regarding Insurance info, I have most converters map these into Membership, and have the converter add custom fields for things like Group #, Policy #, etc. In fact, I'm already handling this:

So, as soon as you provide me with the field labels for each of those custom templates, we can start testing your new conversion.

Also, see my other questions above too.

@netefx7

Sorry for the delay. I wanted to test on both Windows and macOS, since the CSV export differs based on platform.

The Email account mapping may be wonky. The 1Password Email Account template was built when POP email and dial-up ISP access was common. If you don't like the mappings, let me know.

I've updated the dev. release so you can test. The converter's name is msecure6. So use it as in:

perl convert.pl msecure6 -v ..\msecure_export.csv

You can add the --debug (or -d) option if you want to review the mappings without importing into 1Password.

Some notes on your custom templates:

1. I am not mapping the Custom # fields; they will go into the Notes area. If you want them mapped, let me know.

2. The Serial # and Reseller fields for your Serial Numbers template does not map naturally to any fields in the Software License category, so they will become custom fields. I don't know what data type your Purchase Date is, and I've presumed it is a Date Field type (which has a date picker and ID value 10 in the CSV export (the middle value in the pipe-separated value, as in label|id|value). This is important because the date value is in a specific format that gets converted to 1Password's internal representation for date values for date fields. If your Purchase Date is just text, I'll redefine that definition to not attempt to convert this value.

3. I have not created custom templates identical to yours, so haven't tested with any data - you'll have give me feedback on the mapping.

I'll await your feedback.

Edit: I updated the dev version to resolve an issue with placing empty string tags in each item.

Edit: I updated the dev version so that the README is now updated with this new msecure6 converter.

@netefx7

I've updated the dev version of the suite to support all of the stock mSecure 6 templates:

The templates added are: Router Settings, Software License, Vehicle Info, and Voice Mail.

@netefx7

You're very welcome. Those results do look better. Thanks for all your help on this.

I'll keep your customized definitions around for a bit, in case you want a little more fine tuning.

And I'll make an official update to the suite this weekend.

Enjoy 1Password!