Overview
This guide will walk you through connecting your Salesforce or Litify data to Hona and mapping your data fields. The process allows you to customize how your case management data syncs with Hona's platform.
Prerequisites
Administrative access to your Salesforce/Litify instance
Administrative access to your Hona account
Chrome browser installed (for the Hona extension)
Step 1: Configure Object Mapping
In Hona, go to Company Settings → Integrations → Map Fields
Select your primary object (typically "Matter" or "Opportunity")
Add related objects:
Single Objects: One-to-one relationships (e.g., primary client)
Multiple Objects: One-to-many relationships (e.g., team members, tasks, additional clients/contacts)
Step 2: Map Your Fields
Project Details
Under "Project Mapping," match your Salesforce fields to Hona fields:
External ID: [Your Matter/Case ID field]
Project Name: [Your Matter/Case Name field]
Project Type: [Your Practice Area/Matter Type field]
Hona Enabled: [Specifies if the client has access to the Hona portal]
Contact Information
Click "Add Contact Mapping"
Map essential contact fields:
External ID: [Contact/Account ID]
First Name
Last Name
Email (can map multiple fields in priority order)
Phone Numbers (can map multiple fields in priority order)
Role: Set default value to "Main Contact" for primary contacts. If mapping multiple contacts, you will need a field in Salesforce that specifies the roles and setup the roles in Hona
Team Members
Add team member mapping if using team functionality
Map required fields:
Team Member ID
Role (you will need to setup the Hona roles in Team settings)
Hide from Client: Default to false unless specified
Is Primary: Default to false unless specified
Step 3: Preview and Test
Click "Show Preview"
Enter a test Project ID from your Salesforce instance
Review the mapped data to ensure fields are correctly matched
Tips for Success
Start with essential fields and add more as needed
Use the search function when looking for specific fields
Field names may appear differently in Salesforce vs. Hona – look for both the friendly name and backend name
Consider creating a spreadsheet mapping before implementation for complex setups
Need Help?
While this process is designed to be self-service, our team is here to help if you need assistance:
Contact [email protected] for technical issues
Schedule a walkthrough with your account manager for guidance
Visit our help center for additional resources
Common Terms
Single Object: One-to-one relationship (e.g., primary client)
Multiple Objects: One-to-many relationship (e.g., team members)
External ID: Unique identifier used to match records between systems
Child Relationship: Nested or related records (e.g., team roles under team members)