Migrate from Jarvis CRM to Freshsales

Jarvis Contact records map directly to Freshsales Contact. We extract via FileMaker export or direct table access, preserving the primary key and any foreign key links to Company or Project records. Custom contact fields identified during schema audit map to Freshsales custom fields of the appropriate type (text, number, date, picklist). Email address is used as the dedupe key on import. Owner assignment from FileMaker ACL maps to Freshsales Sales Owner by email match.

Jarvis Company records map to Freshsales Account. Company name is the dedupe key. Any custom company fields (industry classification, billing address fields, custom properties) migrate to Freshsales custom Account fields. We create Account records before Contact import so that the Account-Contact relationship is satisfied at the moment of Contact insert.

Jarvis Opportunity records map to Freshsales Deal. Deal name, value, stage, and owner migrate directly. Pipeline stage names from Jarvis map to Freshsales deal stages; we configure the Freshsales pipeline stages before migration so that stage mapping is explicit rather than inferred. Closed-won and closed-lost reasons from Jarvis become Freshsales custom deal fields.

Jarvis Project records (from the project management module) have no direct Freshsales equivalent because Freshsales is a sales CRM without native project management. We evaluate each customer's active Projects and map them to Freshsales Notes attached to the related Account or Deal, or document them as a custom object requiring Freshsales Pro or Enterprise schema creation. Gantt layout and task dependencies are preserved as note metadata; they cannot render as structured tasks in Freshsales.

Jarvis time tracking entries (billable and non-billable hours linked to projects or contacts) have no native Freshsales equivalent. We extract time entry records with linked project and contact IDs, then map them to Freshsales Notes on the associated Contact or Deal record, or to a custom field on the Deal. The customer decides during scoping whether time data is operationally relevant in the new CRM or should be archived as a reference note.

Jarvis vendor records (from the ERP module) map to Freshsales Account records with the Account Type field set to Vendor. We export the vendor table with vendor name, contact, payment terms, and PO data, then create Freshsales Accounts of type Vendor that are separate from customer Accounts. QuickBooks Online integration data from Jarvis may also hold live vendor records; we align the import with the customer's QuickBooks sync plan.

Jarvis is built on FileMaker Pro and is fully customizable, meaning every deployment has custom contact fields, company fields, and opportunity fields that do not exist in a standard schema. We identify all custom properties during the mandatory schema audit and create matching Freshsales custom fields before any data import. Fields with no Freshsales equivalent are flagged in the scoping document and the customer decides whether to drop, map to a text field, or defer to a post-migration Freshsales admin task.

Jarvis user records and owner assignments on Contacts, Companies, and Deals are extracted from the FileMaker ACL and record-level ownership fields. We match Jarvis owners to Freshsales Users by email address during migration. Any Jarvis owner without a matching Freshsales User is placed in a reconciliation queue for the customer's admin to provision before record import continues.