Hi Jeremy,

Thank you for checking the Credit Card type in the older mSecure app. The strange thing is, even if you had removed the default "Credit Cards" type and not just renamed it, the records you see in mSecure 5 now should be using the new "Credit Card" type you may have created, so there's something wrong here regardless of exactly what happened with that type in the old app.

I think the easiest thing to do here will be to simply create a backup of your data in the old mSecure app and then restore from that backup in mSecure 5. That should import the "Credit Card" type you have in the old app, and then it should be used by your credit card records as long as they are assigned to that type in the old mSecure app.

First, I think you have done this already by telling me no records are using the Unassigned type, but just make sure all your credit card records are using the "Credit Card" type you mentioned. Confirm that for me in your next response. Also, when I have you create a backup in the old app and then restore from that backup in v5, all your current data in v5 will be overwritten with the data in the backup file. You'll need to make sure that any new information you added to v5 after you upgraded is documented somehow. I'm hoping you haven't added much, as you just upgraded, but if you have, there is no way to merge data in from a backup file during the restore process. Does that make sense?

The first thing to do is check in the old app to see what the name of the type is for the credit card records that were imported as Unassigned. Go ahead and open the old app, and double-click on each of the Credit Card records. In the dialog that pops up, you'll see a dropdown menu that should show you which type is currently selected for each record. Let me know which type is selected for each of the records. If the type is named "Credit Card," please click the dropdown and see if there is another type in the system called "Credit Card" or something similar.

Hi Jeremy,

Thank you for contacting us. My guess as to why this happened is because the type of record you were using for your Credit Card records was the Unassigned type in mSecure 3/4. This is only a guess, because I don't have enough information to know for sure, but we don't have any known bugs that cause the import of Credit Card type records to fail in the manner you described. The bad news is, you are not able to change the type of an existing record in mSecure 5. That feature is returning in mSecure 6, but it's not available in mSecure 5. The good news is, if you still have access to your information in mSecure 3 or 4, I should be able to help you fix the issue without you having to recreate your Credit Card records.

Do you still have access to your information in mSecure 3/4? If so, please let me know on what types of devices you have that access.

Hi Steven,

Thank you for your feedback here. Due to all the feedback on this missing feature, we've decided to add back the ability to change record types on Mac and Windows. When in the edit screen, you'll be able to change the assigned record type of your record. When changing record types, the fields will simply move over in the order they are currently set and any custom fields will move over as custom fields as well.

So if you change a record from a Login record type to an Email Account record type:

Login

1. URL

2. Username

3. Password

it'll move to 

Email Account:

1. Username

2. Password

3. Incoming Server

If you change a record type from a record type has many fields in it to one that doesn't, all additional fields for the record will be changed to custom fields for the newly selected record type. For example:

Login:

1. URL

2. Username

3. Password

4. Note

changed to Secure Note:

1. Note

2. Custom Field (URL)

3. Custom Field (Username)

4. Custom Field (Password)

@Stephen I'm not entirely sure what you are saying here, but it's possible you are just asking for a "Tags" feature, which is implemented in mSecure 6. In the new version, you will be able to add multiple tags to records for organizational purposes. It's not exactly what you are saying here, but any tag can be used for any purpose by the user, so it should be flexible enough for what you are describing here.

@Andy Thank you for chiming in here to answer @Ed's question.

@ Ed I can add you as a beta tester, but I won't be to do so right away. We have had to divert some of our resources over to helping with an issue affecting the older, unsupported mSecure app after recent iOS devices, so we aren't adding new beta testers now. If you can reply the beginning of next week, I should be able to get you on the list shortly thereafter as long as we are able to keep things under control in support.

Regarding your questions, as @Lawrence said, mSecure 6 installs over the top of your mSecure 5 app, and it updates your data. It is not a different app, so we make sure everyone creates a backup of their mSecure 5 data before downloading the beta version so that if anything happens, it's not difficult to revert back to v5. We've only had a couple of testers do that, but it wasn't due to a data-related problem. They just wanted to stop beta testing.

@Jonathan In v6, which is in beta testing now, you are able to change the template used for your records. It won't be changed in v5, but it will be when v6 is released to the public.

@Albo Thank you for your response in trying to help with a workaround!