V6 CSV Importing

This is a temporary article to briefly cover the logic for importing CSV data into mSecure 6. A more full-featured article will be created soon. If you are coming from mSecure 5, the new logic is much more flexible, which gives you more control over the data getting imported.

The first thing to mention is your CSV must start with this information in the first line: "mSecure6 CSV export file" (no quotes). If the file doesn't contain that information at the start, the logic below will not work.

The formatting for each row, or record, you add to your CSV file is outlined below:

There are a few things I need to go over. First, the pipes included in the format are part of the actual CSV data structure. They are not there to simply separate words, if that makes sense. The angled brackets, on the other hand, are purely visual and should not be included in the actual CSV data.

Second, much of the data for each row is optional. For example, the "record-ID" after the pipe in the first field should not be used when importing new information. That should only be included if the CSV data was exported from mSecure originally and is only used to make sure duplicate records are not created when importing data into a database that already contains information. In most cases, you should only include the title for the record.

Third, when not including a certain property delimited by a pipe, the pipe character should be left out. For example, again using the first field, you would only include the title, and there would be no pipe added to the field data in the CSV. Pipe characters are only included when you are making use of a property for the field.

Fourth, each field, which are the entries that come after the <note> field, has 3 properties: label, type and data, and all are optional. If only a comma is separating one field from the next, ie. two commas in succession, then an empty field should be created with a default label. This is a very uncommon scenario and simply added to be thorough.

Fifth, multiple tags must be separated by a comma enclosed in one set of quotation marks like this: Title,Login,"tag1,tag2,etc",Some notes...

Now for an example record using the default Login template. Here is what the CSV entry would look like:

Netflix,Login,"entertainment,family,subscriptions",Signed up on 2/15/2017,Website|2|https://www.netflix.com,Username|7|[email protected],Password|8|P@$$w0rd,Custom Field1 Label|0|Custom Field1 Data,Custom Field2 Label|1|Custom Field2 Data

The above row would be translated like this in mSecure:

Title: Netflix

Template: Login

Tags: entertainment, family, subscriptions

Note: Signed up on 2/15/2017

Field 1:

——

Label: Website

Type: URL

Data: https://www.netflix.com

Field 2:

——

Label: Username

Type: Username

Data: [email protected]

Field 3:

——

Label: Password

Type: Password

Data: P@$$w0rd

Custom Field 1:

——

Label: Custom Field1 Label

Type: Text

Data: Custom Field1 Data

Custom Field 2:

——

Label: Custom Field2 Label

Type: Text (no auto-correct)

Data: Custom Field2 Data

Click HERE to download a CSV file that has one field of every type, so you can see the formatting you would use for each of them. For example, the URL field type ID is 2, Username type is 7, Password type is 8, and so on.

Did you find it helpful? Yes No

More articles in Features