Migrate from Jarvis CRM to Nutshell

Jarvis Contact records map to Nutshell Person. We extract the FileMaker Contacts table including all standard fields (name, email, phone, address) and every custom contact property identified during the schema audit. The FileMaker ContactID is preserved as an external_id field in Nutshell to support relationship reconstruction during the Company and Deal association phases. Nutshell's Person object uses a combined first-name/last-name structure; we split the name field accordingly from FileMaker.

Jarvis Company records map to Nutshell Account. We extract the full Companies table before any Person import so that the Account record exists at the moment of Person insert, satisfying the Nutshell account lookup. Custom company fields migrate to Nutshell custom fields on Account, created during the schema preparation phase. The FileMaker CompanyID is preserved as external_id to resolve Person-to-Account links during the association import.

Jarvis Opportunity records map to Nutshell Deal. We extract deal values, stage names, close dates, owner assignment, and associated contacts. Stage names vary per FileMaker deployment and are mapped to Nutshell's pipeline stage values during transformation. We create the Nutshell pipeline and stage configuration before migration to ensure stage values are valid at import time. Closed-won and closed-lost reasons from custom properties migrate to the Deal's notes field as a structured text block.

Jarvis pipeline stages (custom per deployment) are mapped to Nutshell pipeline stages. We create the Nutshell pipeline structure first during schema preparation, configuring stage names, probabilities, and ordering to match the source deployment as closely as possible. The number of pipelines in Jarvis (typically one per sales process) maps to a single Nutshell pipeline unless the customer requests multiple pipelines for different business units.

Jarvis task and activity records map to Nutshell Activity. We extract activity type, timestamp, owner assignment, and linked contact or deal references. The FileMaker foreign key linking an activity to a Contact or Opportunity is resolved at migration time using the preserved external_id values. Activity records without a resolvable parent record are imported as standalone activities with the original subject and timestamp preserved.

Jarvis user records are extracted from the FileMaker ACL and record-level ownership fields. We map Jarvis users to Nutshell users by email match. Any Jarvis user without a matching Nutshell account is held in a reconciliation queue; the customer provisions the Nutshell user before the migration resumes. Active/inactive status is preserved from the source FileMaker deployment.

Jarvis Project records and Gantt metadata do not have a standard equivalent in Nutshell's CRM data model. We extract the full Projects table including task structures, assignees, and Gantt layout metadata as structured CSV for customer archive. Projects that represent a sales-related milestone are documented in the Deal notes as a text reference with the original project identifier. This ensures audit continuity without forcing a fit into a data model where it does not belong.

Jarvis time tracking entries (billable and non-billable hours linked to projects, contacts, or vendors) do not map to any standard Nutshell object. We extract time entries with original IDs, linked entity references, billable status, and duration, and deliver them as a structured CSV for archiving or loading into a separate time-tracking system. The decision to archive or re-enter time data is made during scoping based on the customer's reporting needs.

Vendor records, purchase orders, and payment histories from Jarvis's ERP module have no Nutshell CRM equivalent. We extract the full Vendors and Purchase Orders tables as structured CSV exports. QuickBooks Online integration may hold live vendor data that supersedes the FileMaker export; we coordinate with the customer's accounting team during scoping to determine the authoritative source for vendor records.

Every Jarvis deployment has custom fields on Contact identified during the schema audit. We create equivalent Nutshell custom fields on Person before migration begins, matching field types (text, number, date, picklist). Custom picklist values in FileMaker are replicated as Nutshell picklist options. Any custom field with no reasonable Nutshell equivalent is flagged in the mapping document with a customer-facing decision on whether to map it to a text field or drop it from migration.

Custom company properties migrate to Nutshell Account custom fields. We create each custom field in Nutshell during schema preparation, preserving the original field label as the Nutshell field name for familiarity. Multi-select picklist values from FileMaker map to Nutshell multi-select custom fields where supported.

Jarvis campaign and contact group records are basic metadata without native marketing automation capability. We extract campaign names, descriptions, creation dates, and group memberships as structured CSV. Because Nutshell does not include a marketing automation engine and Jarvis campaign data is typically foundational rather than automated, we archive this data and provide the mapping document for the customer's marketing team to recreate segments in their chosen marketing platform post-migration.