Migrate from Jarvis Legal to Pipedrive

Jarvis Client records map directly to Pipedrive Person records. The client name splits into first name and last name on the Person. Primary email, phone, and address fields map directly. If the Jarvis client record includes a company name, a corresponding Pipedrive Organization record is created and linked via the Person-Organization relationship.

Jarvis Client records that represent corporate clients (rather than individual attorneys or contacts) are merged with a Jarvis Company entity (if present) into a Pipedrive Organization record. The Organization stores the firm or company name, domain/website, industry classification, and employee count where available.

Jarvis Matter records are the core migration object. Each matter becomes a Pipedrive Deal. The matter name maps to Deal title. Matter status (Active, Closed, Pending) maps to a Pipedrive custom picklist field. Pipedrive's StageName on the Deal corresponds to the matter workflow stage. A Matter_Type__c custom field preserves the legal matter category (litigation, corporate, family, etc.).

Jarvis practice-area classifications (litigation, real estate, corporate, family law) map to separate Pipedrive Pipelines so each practice area has its own stage set and probability model. Each pipeline is a distinct Sales Process in Pipedrive, enabling separate stage names and forecast-category logic per matter type.

Jarvis time entries (date, duration, billable flag, description) map to Pipedrive Activities with type='Task'. Billable hours and hourly rate are stored as custom numeric fields on the Activity. The Activity is linked to the corresponding Deal (matter). Non-billable entries are stored with the billable flag set to false in a custom field.

Jarvis invoices have no Pipedrive native equivalent. Invoice ID, amount, status (draft, sent, paid), due date, and payment method are stored as custom fields on the corresponding Deal. The invoice PDF is uploaded as a Pipedrive File attached to the Deal. Firms that need recurring billing or trust-accounting should maintain those in a dedicated billing tool.

Jarvis documents stored in matter folders are downloaded and re-uploaded as Pipedrive Files attached to the corresponding Deal (matter). Documents with searchable text content are also written to Pipedrive Notes with the file content preserved for searchability. Pipedrive's 25MB per-file limit applies — large documents are flagged before migration.

Jarvis calendar events — court dates, client meetings, deadlines — map to Pipedrive Activities with type='Meeting'. Start time, end time, location, and attendees are preserved. Pipedrive's Google Calendar and Outlook integration is re-enabled post-migration to maintain sync on new events.

Jarvis tasks associated with matters map to Pipedrive Activities with type='Task'. Due date, priority, assignee (resolved by email to Pipedrive user), and description are preserved. Completed-at timestamp is stored in a custom datetime field if the task was closed before migration.

Jarvis's 2-way Outlook and email sync brings emails into matter threads. These migrate as Pipedrive Activities with type='Email'. The email body is stored in the Activity's note field. Original sender, recipient, cc/bcc fields, subject line, and timestamp are all preserved in standard activity metadata. Attachments on Jarvis emails are downloaded and re-attached to the corresponding Pipedrive Activity record to maintain complete email context within each matter.

Jarvis staff accounts are resolved by email match against Pipedrive users. Active Jarvis attorneys and staff get matched to their Pipedrive user accounts. Unmatched users are flagged before migration so the firm can create Pipedrive accounts or reassign records to a fallback owner.

Jarvis custom fields on clients, matters, or companies — identified by UUID in the Jarvis API — are created as Pipedrive custom fields on the equivalent entity (Person, Deal, Organization). Pipedrive assigns a 40-character hash key per field per account. The field type is matched as closely as possible (text, number, picklist, date, checkbox).

Jarvis's native client-to-matter link (1:N) maps to Pipedrive's Deal-Person association. Each Matter/Deal is linked to its primary Client/Person. Pipedrive supports multiple Person links per Deal, mirroring cases where multiple attorneys, paralegals, or parties are associated with a single matter. Secondary contacts on the Matter are added as additional Person links on the Deal, preserving the full participant roster from Jarvis within each matter's Pipedrive record.

Jarvis trust-account balances and trust transaction history have no Pipedrive equivalent. FlitStack preserves trust balance as a custom currency field on the Deal for reference, but recommends firms maintain dedicated legal accounting software (e.g., CosmoLex, Clio Manage) for trust-account compliance post-migration.

Jarvis task templates, matter-opening workflows, and automated deadline reminders do not migrate. These are exported as a JSON definition file that the firm's Pipedrive admin can use as a reference when building Pipedrive Automations. Jarvis's automation logic is platform-specific and requires manual rebuild in Pipedrive's Automation builder.