Migrate from Jarvis CRM to Pipedrive

Jarvis Contact records map directly to Pipedrive Person. We extract all standard fields (name, email, phone, address) via FileMaker export or direct table access, and map any custom contact fields to Pipedrive custom fields on the Person object. Email address serves as the primary dedupe key. Owner assignment extracts from the FileMaker ACL owner field and maps to a Pipedrive User by email match.

Jarvis Company records map to Pipedrive Organization. The organization's domain_name or website field becomes the Organization's Website field and is used as a secondary dedupe key alongside the organization name. We export the full company table including any custom company fields and map them to Pipedrive custom fields on Organization. Organization is created before Person import so that the Person-Organization link is satisfied at insert time.

Jarvis Opportunities map to Pipedrive Deals. Deal value (amount), stage, owner, expected close date, and associated contact/organization links migrate. Pipeline stage names from Jarvis are mapped to Pipedrive stage values in the destination pipeline, with stage probabilities adjusted to the nearest Pipedrive-allowed integer. The Person-Organization association on the deal migrates using the primary key links extracted from the FileMaker relational schema.

Each Jarvis Opportunity pipeline becomes a Pipedrive Pipeline with its own stage values. We configure the pipeline and stages in Pipedrive before migration so that stage names map correctly and deal probability percentages transfer. If the Jarvis deployment uses custom pipeline stages beyond the standard, we map them explicitly to Pipedrive stage equivalents during scoping.

Jarvis Projects do not have a direct Pipedrive equivalent. We assess the project structure during schema audit and typically map project records to Pipedrive Deals with project metadata in custom fields, and project task structures to Activity records linked to the parent Deal. If the project contains significant time-tracking data, billable hours migrate as custom fields on the Deal. Gantt layout data migrates as a JSON-formatted Note attachment. This is a disposition decision made during scoping based on the customer's use of the project module.

Jarvis time entries (billable and non-billable hours linked to projects or contacts) migrate as Pipedrive Activities with a custom field for hours logged and another for billable/non-billable status. Time entry timestamps preserve the original recorded date for audit purposes. If the customer uses time entries primarily for billing rather than sales activity tracking, we document this as a separate reporting consideration and do not create activity timeline entries for non-billable internal time.

Jarvis Vendor records map to Pipedrive Organizations with a custom field vendor_type__c set to Vendor. Purchase order and bill data associated with vendors migrate as Activity notes or as custom fields on the Organization record depending on volume and complexity. We flag any vendor-specific fields with no Pipedrive equivalent during schema audit for customer disposition.

Every Jarvis deployment has custom fields unique to that FileMaker instance. We conduct a mandatory schema audit before migration to identify every custom field on every object. Custom fields from Jarvis map to Pipedrive custom fields on the equivalent object (Person, Organization, Deal, Activity). Pipedrive supports custom fields of types including text, number, date, dropdown, checkbox, and address. Fields with types not supported in Pipedrive (e.g., multi-value relational fields from FileMaker) require a disposition decision: flatten to text, drop, or replace with a custom note.

Jarvis Campaign and Contact Group records migrate as Pipedrive Person tags or as a multi-select custom field on Person, depending on which approach provides better usability for the customer's sales workflow. Campaign metadata (name, status, start date) migrates as a custom field or as an Organization tag if the campaign was account-based. This is a scoping decision based on how the customer uses campaign data in Jarvis.

Jarvis Product and Service catalog records map to Pipedrive Products. Item names, descriptions, unit prices, and product codes migrate. Product-to-deal associations migrate as Deal-Product links using the product ID key extracted from the FileMaker product table and resolved at migration time. If Jarvis uses custom pricing tiers per product, these migrate as custom fields on the Pipedrive Product.

File attachments stored within the FileMaker instance can be exported, but attachment storage format and location vary by deployment. We identify attachment storage paths during scoping and include them in the migration scope if the files are accessible via FileMaker export or direct file access. Attachments migrate as Pipedrive file attachments linked to the parent record, or as Notes with file content if the attachment is text-based. Binary attachments (PDFs, images) are extracted and linked individually.

User records and owner assignments on Jarvis records extract from the FileMaker ACL and record-level ownership fields. We map Jarvis users to corresponding Pipedrive users by email match. Any Jarvis owner without a matching Pipedrive user goes to a reconciliation queue for the customer's admin to provision the user before record import resumes. Owner assignment on deals, contacts, and organizations migrates by resolving the FileMaker owner key to the Pipedrive User record.