Hi Geoff,

Thank you for contacting us. The CSV import feature is different in v6, and actually much improved. Unfortunately, we don't have support article to help with the changes just yet, but I do have information to help.

First, when you import a CSV, the data is merged in with your current data. Your current information is not overwritten. That being said, please do make new backup before importing the CSV just in case something happens that I'm not able to foresee. That way, you can always restore from the backup if something goes wrong. Probably a silly thing to have to mention, but I always like to just in case.

<title|record-ID>,<template-name>,<tags>,<note>, <field-labe1|field-type1|field-data1>,<field-label2|field-type2|field-data2>

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 duplicates are not created. In your situation, you would 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, those 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 so only 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:

In the above row, here's how it would be translated by mSecure:

Title: Netflix

Template: Login

Tags: entertainment, family, subscriptions

Note: Signed up on 2/15/2017

Field 1:

1. Label: Website
2. Type: URL
3. Data: https://www.netflix.com

Field 2:

1. Label: Username
2. Type: Username
3. Data: mike@gmail.com

Field 3:

1. Label: Password
2. Type: Password
3. Data: P@$$w0rd

Custom Field 1:

1. Label: Custom Field1 Label
2. Type: Text
3. Data: Custom Field1 Data

Custom Field 2:

1. Label: Custom Field2 Label
2. Type: Text (no auto-correct)
3. Data: Custom Field2 Data

I'm attaching a CSV file with one field of every type, so you can see the code 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. You'll see all of the codes in the attached CSV file.