Prerequisites
Access to Hona with integration configuration permissions
List of project types that need to be mapped
Setting Up Mappings
Sync Configuration
Navigate to Company Settings > Integrations > Map Fields
Select "Add Project Type"
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: Map the field that enables Hona in Filevine. This field would have been set up at the time of onboarding. A default of yes can be set if field does not exist
Optional field available:
Followers
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.
Main Contact
External ID: Map to contact/person ID
Role: Usually left as default for main contact.
First Name
Last Name
Phones
Emails
Additional Contacts (via Parties or Form Fields)
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
Common Issues
Unmapped enum values
Missing required fields
Incorrect field type matches
Multiple target mappings
If you cannot find a report in the source, try syncing static data from the integration page
Project types can only be used in one mapping
If a project is included in multiple mapped reports, it will not be imported into Hona
When testing, verify that both contact information and roles/types are pulling correctly
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
Temporarily filter the report in Filevine to only include test projects