Migrate from Jarvis Legal to Salesforce Sales Cloud

Jarvis 'Client' is the primary person record — maps directly to Salesforce Contact. Salesforce requires AccountId for most use; if the client is an individual with no firm, they link to a default 'Individual Client' Account record. The Contact's email and phone are used for owner resolution and duplicate detection.

Jarvis secondary contacts (associates, counterparties, court contacts) map directly to Salesforce Contact. If they are not clients but are involved in matters, they land as Contacts without Account linking, or get linked to a 'External Party' Account based on firm naming conventions.

Jarvis companies map to Salesforce Account — the firm (as a client organization) and opposing or related parties all use Account. Account.Phone, Account.Industry, Account.Website, and Account.BillingAddress map directly. Parent-company hierarchies use Account.ParentId. For multi-office firms, each office location can be a separate Account record linked to a parent Account representing the overall organization.

Jarvis matter is the legal engagement record — maps to Salesforce Case. Case.Subject carries the matter title, Case.Description carries matter notes, Case.Status maps from Jarvis matter status (Open, Closed, Pending), Case.Type carries matter type (Litigation, Transaction, Advisory), and Case.AccountId links to the client Account. Case.OwnerId resolves the responsible attorney by email match to a Salesforce User.

Firms that distinguish between support cases and billable legal matters create a custom Matter__c object in Salesforce. Matter__c links to Case (for activity tracking) and to Account (the client firm). Fields include Matter_Number__c, Practice_Area__c, Responsible_Attorney__c, Conflict_Status__c, Statute_of_Limitations__c, and Billing_Status__c — all mapped from Jarvis matter custom fields.

Jarvis time entries (attorney hours logged against a matter) map to a custom TimeEntry__c object linked to the Salesforce Case (the migrated matter). Fields include Date__c, Hours__c, Description__c, Rate__c, and OwnerId (attorney). If Salesforce Classic Time Tracking or a third-party billing app is in use, time entries may alternatively feed into that tool's API.

Jarvis invoices (draft, sent, paid, overdue) have no direct Salesforce equivalent. FlitStack creates a custom Invoice__c object with Invoice_Number__c, Invoice_Date__c, Amount__c, Status__c, and Account__c (lookup to the client Account). If Salesforce Orders is enabled, the invoice also creates an Order record with OrderItems for line-item fidelity.

Jarvis document blobs (PDFs, Word files, correspondence) export as binary files with file name, matter association, and upload timestamp. Each file re-uploads as a Salesforce ContentVersion linked to the corresponding Salesforce Case or Contact via ContentDocumentLink. File size limit in Salesforce is 25MB per file by default; files larger than this are flagged for chunked upload or alternative storage URL.

Jarvis custom fields are referenced by UUID in the API (e.g., cdccbea3-debd-453d-8a30-691f48c5a9e5). Each custom field has a data type — text, number, date, pick-list, or boolean. FlitStack reads the field metadata, maps it to the corresponding Salesforce custom field with a clean API name, and pre-creates the field definition in Salesforce before the migration run. Pick-list values are preserved value-by-value.

Jarvis calendar events and deadlines map to Salesforce Event (for meetings/hearings) and Task (for action items and reminders). The Salesforce record's WhatId links to the corresponding Case (mattery) and WhoId links to the Contact. Original event timestamps, attendees, and status are preserved.

Jarvis workflow rules (matter-opening triggers, document-generation templates, conflict-check automations, email notifications) do not have a Salesforce equivalent that can be auto-migrated. FlitStack exports the full workflow definition from Jarvis as a structured JSON + human-readable PDF so your Salesforce admin has an implementation reference to rebuild in Flow.

Jarvis user accounts (attorneys, paralegals, admins) resolve to Salesforce Users by email address match. Unmatched users are flagged before migration — the firm either invites them to Salesforce first or assigns their matters to a fallback owner. Inactive Jarvis users map to Salesforce Users with IsActive=false for historical record integrity.