Skip to main content

Mapping CMS Fields and Contact Types

Oct 7, 2026•Settings & Configuration

Learn how to configure mapping between your CMS fields, case types, and contact types to ensure the right data imports into Quilia.

Law FirmsPortal TutorialAll CMSCMS IntegrationData SyncSettings

When Quilia imports cases from your case management system (CMS), field mapping tells it which of your CMS fields holds which piece of information. A field you map is filled in from your CMS, so your client is not asked for something your firm already has.

There are three places to set mappings. Which ones you see depends on your CMS. All of them are admin-only.

Case fields for each case type

For Clio, Filevine, MyCase, Neos and Salesforce, you map case fields separately for each case type, because each case or project type in your CMS has its own fields.

  1. Go to Settings → Case Types and select a case type.
  2. Open the Integration tab. It only shows when the case type is linked to a case type in your CMS.
  3. In Case fields from [your CMS case type], choose the CMS field that holds each Quilia field. Select Refresh fields if a field you just added in your CMS is missing.
Case fields on a case type's Integration tab, each Quilia field pointed at the Filevine field that holds it.

The Quilia fields you can fill this way are:

  • Description of the incident, Where it happened, Date of injury and Time of injury
  • Police department and Police report number
  • Injuries and Prior injuries and health problems
  • Vehicle type, Vehicle year, Vehicle make, Vehicle model, Vehicle mileage, Vehicle color, VIN, License Plate Number and License Plate State
  • Minor's name (Filevine only). See Importing Minors and Their Parents.

Each field in the card shows a short note on where it appears in Quilia. For Filevine, the card can also suggest mappings for you to accept.

Fields tab (Filevine)

For Filevine, the CMS integration page also has a Fields tab for the mappings that apply to every project type. Go to Settings → Integrations, select Manage next to Filevine, and open Fields.

  • Contact fields: Emergency Contact (who Quilia treats as the client's emergency contact) and Language (the client's preferred language for Quilia messages, which can be read from a field or from hashtags like #spanish on the client).
  • Case fields: Office / Location (a project field linking each case to the office it belongs to) and the Case subtype field.

Select Refresh from Filevine if a field you need is not listed.

The Fields tab on the Filevine integration page.

Contact Types tab (Filevine and Neos)

Your CMS uses its own words for the contacts on a case. On the Contact Types tab of the integration page, you tell Quilia which of your contact types mean what. For each kind of contact Quilia knows about, pick the matching types from your CMS:

  • Treating providers
  • Emergency contacts (Filevine only)
  • Medical facilities
  • Emergency rooms
  • Ambulance services
  • Police departments
  • Employers
  • Insurance companies
  • Towing companies
  • Vehicle storage
  • Body shops
  • Rental companies

Each of your contact types can belong to only one of these.

The Contact Types tab before anything is mapped. Anything you leave unmapped is not imported.
Still need help?

Can't find what you're looking for? Our support team is here to assist you.