Back to Help Center

Contact Import and Export Formats

Supported CSV and VCF formats for contact import/export, including field mappings and de-duplication rules.

Use Settings → Contacts for contact-level import/export.

  • Import: .csv or .vcf
  • Export: .csv or .vcf

This article explains which contact file formats work best and how PracticeRunner reads them.

Contact Import (CSV)

Supported CSV layouts

  • Split-name format (for example: First Name, Middle Name, Last Name)
  • Full-name format (for example: Client or Full Name)
  • SimplePractice Client Details Report format

At minimum, each row needs either:

  • First Name + Last Name, or
  • Client / Full Name

CSV field mapping

CSV column (accepted names)Imported to
First Name, Firstname, Given NameClient.firstName
Middle Name, MiddlenameClient.middleName
Last Name, Lastname, Surname, Family NameClient.lastName
Client, Name, Full Name, Client NameSplit into firstName, middleName, lastName
EmailMain client email (ClientEmail.address)
PhoneClient.phone and main ClientPhone.number
Date of Birth, DOBClient.dob
Address, StreetClient.street
CityClient.city
StateClient.state
Zip, PostalClient.zip
CountryClient.country
NotesClient.notes
Date AddedClient.dateFirstSeen
Status (Active, Archived, Prospect)Client.status (normalized to ACTIVE, ARCHIVED, PROSPECT)
Primary Clinician, ClinicianMatched to the clinician by full name. If no match is found, the importing user is assigned
Primary Insurance, Insurance, PayerClientInsurance.payer
Insurance ID, Member IDClientInsurance.memberId

Notes:

  • New contacts default to ACTIVE unless the file says otherwise.
  • Insurance details are only created when the file includes insurance information.

Contact Import (VCF)

Supported VCF expectations

  • Standard vCard 3.0 cards
  • Individual cards
  • Couple cards with &/ in name fields (split into two individual contacts)

VCF field mapping

VCF fieldImported to
N: family/given/additionallastName, firstName, middleName
FN:Used when separate name fields are missing and to normalize full names
EMAILMain client email (ClientEmail.address)
TELClient.phone and main ClientPhone.number
BDAYClient.dob
ADRstreet, city, state, zip, country
NOTEClient.notes

Additional VCF behaviors:

  • Middle initials/names are normalized into middleName.
  • If the middle name is missing in the card fields, PracticeRunner can use the filename when it includes the missing name.
  • Couple records are split and imported as individual contacts.

De-duplication and Merge Behavior

When importing, PracticeRunner tries to match an existing contact in this order:

  1. Same first+last name and same email
  2. Same first+last name and same phone
  3. Unique first+last match (only when no email/phone provided)
  4. Unique email match when name matching is not enough
  5. Unique phone match when name and email matching are not enough

If PracticeRunner finds a match, it updates the existing contact. If not, it creates a new one.

Contact Export (CSV and VCF)

Exports include active clients from your organization.

CSV export columns

CSV columnSource
First NameClient.firstName
Last NameClient.lastName
EmailMain ClientEmail.address
PhoneClient.phone
Date of BirthClient.dob
StreetClient.street
CityClient.city
StateClient.state
ZipClient.zip
CountryClient.country
NotesClient.notes

VCF export fields

VCF fieldSource
N:last;first;middle;;Client.lastName, Client.firstName, Client.middleName
FN:first middle lastName display field
EMAIL;TYPE=INTERNETMain ClientEmail.address
TEL;TYPE=CELLClient.phone

© 2026 PracticeRunner™. All rights reserved.