Skip to main content

Filevine Data Mapping Guide

Use this article to configure field mapping between Filevine and Hona, including project types, phases, and contact fields. Applies to both initial setup and fixing incorrect mappings.

s

What this article helps with: Mapping Filevine fields to Hona so that the right data pulls into the right places — including project types, phases, and contact fields. Use this for both initial setup and fixing incorrect mappings.

Who this is for: Firm admins or Hona onboarding contacts with integration configuration access.

When not to use this article: If Filevine is not connected yet, start with Filevine Integration Setup. If data was mapped correctly before but has stopped syncing, see Integrations: What is Syncing?.


How data flows between Filevine and Hona

What Hona pulls from Filevine: Case/project name, project type, phase, client contact details (name, phone, email), team member assignments, and any custom mapped fields.

What Hona pushes back to Filevine: texts, notification activity and form submissions, logged as notes on the project; AI Receptionist call summaries, logged as phone call notes; and documents from texts, forms and e-signatures, uploaded to the project. See Filevine: Where Hona Logs Texts, Notes and Documents.

Important — Filevine is the source of truth. Hona reads data from Filevine, not the other way around for case records. If a contact's phone number or case detail differs between Hona and Filevine after a sync, the Filevine value will overwrite the Hona value on the next sync. Always update contact and case data in Filevine, not Hona.


Prerequisites

  • Access to Hona with integration configuration permissions

  • List of project types that need to be mapped

Setting Up Mappings

Sync Configuration

  1. Navigate to Company Settings > Integrations > Map Fields

  2. Select "Add Project Type"

  3. Configure the following sections:

Project Mapping

  • Name: Select the project name field (Usually Project> Project or Client Name)

  • Project Type Name: Map to your Hona project type identifier

  • Phase: Map to your phase trigger field

  • Hona Enabled: the Filevine field that decides whether a project syncs. In the setup flow, Hona asks for this field on each project type you choose. If you don't have one, create it in Filevine: Advanced > Customs Editor, choose the project type, pick a regular section (not a collection), add a Yes/No field named Hona Enabled, and consider making it required. Back in Hona, click Refresh fields, pick the field, and mark which values sync. A project comes into Hona only when its value is one you marked as syncing. Blank and unmarked values keep it out.

  • Optional field available:

    • Followers

Syncing stays paused until your Hona project types and phases are set up. Then turn on syncing for each mapping.

Contact Mapping

There are multiple ways you can set up the contact mappings. If you use the form fields, you will need to set up one mapping per unique form field. However, if you use a collection section, only two mappings will be required.

  1. Main Contact

    • External ID: Map to contact/person ID

    • Role: Usually left as default for main contact.

    • First Name

    • Last Name

    • Phones

    • Emails

  2. Additional Contacts (via Parties or Form Fields)

    • Click "Add Mapping for Contacts"

    • Configure similar fields as main contact

    • Include Contact Role mapping

    • Consider adding opt-out field mapping (e.g., "Is Deceased" field)

Validation and Testing

Preview Project Syncs

  • Preview some projects using the preview tool to verify data maps correctly

Common Setup Notes

  • One mapping required in Hona per project type in Filevine

  • Contact mappings can use both party-based and form-based approaches simultaneously

  • Default values can be used when specific fields aren't available

Best Practices

Project Type Setup

  • Consider using one Filevine project type mapped to multiple Hona project types

  • Use field values to differentiate between Hona project types

  • Example: One "Personal Injury" Filevine type can map to multiple specific Hona types

Contact Configuration

  • Use party-based mapping for variable numbers of contacts

  • Use form-based mapping for fixed contact relationships

  • Always map opt-out fields to prevent inappropriate communications

  • Consider using "Is Deceased" or similar fields for auto-update opt-outs

Field Mapping Tips

  • Start with contact mappings to reduce dropdown options

  • Use consistent naming for better tracking

  • Set appropriate default values for optional fields

  • Configure enum mappings properly (Yes/No, True/False)

Troubleshooting

Use this section to diagnose specific mapping problems. For general sync issues (data not pulling at all, integration inactive), see Integrations: What is Syncing?.

  • Client phone or email not updating in Hona — Check contact mapping. Confirm field names match exactly (field names are case-sensitive in Filevine).

  • Project not appearing in Hona at all: check that its Hona Enabled value is one you marked as syncing, that its project type is mapped, and that syncing is turned on for that mapping.

  • Wrong phase triggering in Hona — Check phase trigger mapping. Confirm the Filevine phase names match exactly what is configured in Hona.

  • Project appearing under the wrong project type — Review the project type mapping values and confirm they match the Filevine project type names.

  • Unmapped enum values — If a field uses Yes/No or True/False values, make sure enum mappings are configured for all possible values.

  • A Filevine project type is missing from the list: click Refresh on the project type list. If Hona can't load from Filevine, give it a moment and refresh again. Project types that already have a mapping show as Already mapped; manage those in the object mapper.

  • Contact roles or types pulling incorrectly — When testing, verify both contact information and roles/types are pulling correctly via the preview tool.

Validation Steps

  • Check for warning messages in the interface

  • Verify field mappings match expected data types

  • Confirm all required fields are mapped

  • Test sync with sample projects before full implementation

  • Test with a few projects first: set Hona Enabled to a syncing value on those projects only, and sync each one by hand from its Actions menu in Hona. While the integration is inactive, nothing syncs on its own and no updates go to clients.


Related articles

Did this answer your question?