Migrate from Jiva to Nutshell

Jiva People records map directly to Nutshell Persons via field name matching across all standard contact attributes including name, email address, phone number, job title, and physical address. Every standard field transfers automatically without transformation logic. Any custom fields defined on Jiva People objects require matching Nutshell Person custom fields to be created in your Nutshell account before the migration execution phase begins. This pre-creation step ensures target fields exist at migration time so values land correctly without truncation or rejection.

Jiva Companies map one-to-one to Nutshell Companies with direct field name matches for company name, domain/website URL, industry classification, employee count, and annual revenue figures. Jiva parent-company hierarchy relationships map to Nutshell's parent-company lookup field when both the parent and child company records land in the same migration batch. If parent records arrive in a different batch sequence, circular reference flags prevent ordering conflicts and ensure the hierarchy resolves correctly once all related records have migrated.

Jiva Deals map to Nutshell Opportunities with direct transfers of deal name, monetary amount, expected close date, assigned owner, and current stage name. The Jiva pipeline name is preserved as a reference field on the Nutshell Opportunity record since Nutshell Foundation and Pro tiers utilize a single pipeline architecture. Teams on Nutshell Business tier or above can create additional pipelines before migration if the Jiva pipeline structure needs to be replicated in the target system.

Jiva Lead records map to Nutshell Leads using field name matches for standard lead attributes including name, associated company, email address, phone number, and lead source. Jiva lead status values are mapped to Nutshell's lead status pick-list values, with unmapped or custom Jiva status values flagged for manual review and pre-migration alignment. This review step ensures no leads land with unknown status values that would require post-migration data cleanup or status reassignment.

Jiva engagement logs including calls, emails, meetings, and notes all map to Nutshell Tasks with original timestamps, assigned owner, and related Person or Opportunity link preserved throughout the transfer. Task type field is set based on the Jiva activity kind (call, email, meeting). Long-form note bodies from Jiva activities are migrated as Nutshell Notes attached to the parent Person record, maintaining the full context of customer interactions in a format that Nutshell users can review inline.

Jiva owner assignments resolve by email address match against existing Nutshell user accounts. If a Jiva owner has no matching Nutshell user during migration, the record lands under the migration admin account and is flagged for owner reassignment in the post-migration review report. Nutshell's API impersonation mode can apply correct ownership after migration if Nutshell users are created retroactively, ensuring historical attribution is preserved without requiring record re-creation.

Jiva engagement scores have no native equivalent in Nutshell's data model. We migrate the numeric score as a custom Number field on the Person record (e.g., Jiva_Engagement_Score__c equivalent). Historical score change events are preserved as a companion custom text field using a pipe-delimited timestamp:score format (e.g., 2024-01-15T10:30:00Z|85) for reporting continuity and audit trail purposes.

Jiva custom objects defined on Enterprise plans are mapped to Nutshell custom fields on the most closely related standard object. If a Jiva custom object has relationships to multiple standard objects, we create a custom field on each parent object and store the Jiva record ID for cross-referencing. Complex Jiva custom objects with nested sub-object structures may require pre-migration consultation to define the optimal Nutshell schema approach.

Jiva file attachments are downloaded from Jiva's storage and re-uploaded to Nutshell Files, then attached to the matching target record (Person, Company, or Opportunity). Nutshell enforces a 25MB per-file limit via its JSON-RPC API; files exceeding this threshold are flagged during the discovery phase and communicated to the customer for manual handling, file splitting, or external hosting before migration runs.

Jiva workflow rules and automation sequences have no equivalent construct in Nutshell and cannot be transferred as executable logic. We export all Jiva workflow definitions as a structured JSON reference document that your team or a Nutshell consultant can use to rebuild equivalent automation using Nutshell's native automation rules (available on Pro+ plans) or third-party integration tools.