Migrate from Jiva to Freshsales

Jiva contacts migrate directly to Freshsales Contacts. Email address is the unique identifier for de-duplication. Contacts without email are flagged for manual review before migration. Primary company association from Jiva maps to the Freshsales Account lookup field. This ensures accurate data continuity.

Jiva contacts with lifecycle_stage values indicating early funnel (Subscriber, Lead, Marketing Qualified) split to Freshsales Leads. Contacts that have progressed to Customer or Evangelist stages route to Freshsales Contacts. The split logic is configurable based on Jiva's actual lifecycle stage values.

Jiva companies map directly to Freshsales Accounts. Domain and industry fields map to Freshsales' website and industry pick-list values. Parent-child company hierarchies in Jiva map to Freshsales' parent Account relationship. We also verify that each company record includes a valid website URL for automatic account creation in Freshsales.

Jiva deals migrate to Freshsales Deals with pipeline stage, amount, close date, and owner preserved. Deal probability values from Jiva map to Freshsales deal stage probabilities. Unmatched deal owners are assigned to a fallback owner flagged in the migration report.

Each Jiva pipeline becomes a Freshsales Deal Pipeline. Pipeline stages map to Freshsales deal stages with value-by-value translation. Multiple Jiva pipelines require Freshsales Pro or Enterprise for more than one pipeline on Growth tier. This mapping preserves stage probabilities and forecast categories across the migration.

Jiva lifecycle stage pick-list values map to Freshsales Contact Lifecycle Stages value-by-value. Stage transition timestamps are preserved in a custom datetime field if Jiva stores history. The Freshsales Pro plan is required to use lifecycle stage automation triggers for your sales team.

Jiva activities map to Freshsales Sales Activities with type classification preserved. Call activities use type 'Call', email activities use 'Email', meetings use 'Meeting', and tasks use 'Task'. Original timestamps, duration, and owning user are migrated. Activity associations to contacts, accounts, or deals are preserved as Freshsales links.

Jiva notes migrate as Freshsales Notes attached to the corresponding Contact, Account, or Deal record. Rich text formatting is preserved where Jiva's data format supports it. Notes without a parent record are attached to the primary contact during the migration process.

Jiva custom objects migrate to Freshsales custom objects if the destination account is on Enterprise tier. N:N relationships in Jiva require Freshsales junction object definitions. If the destination is on a lower tier, custom object data migrates as custom fields on the parent standard object.

Jiva file attachments on records are downloaded and re-uploaded to Freshsales Files. File size limits from Freshsales apply (standard storage quotas per plan). Inline images embedded in notes are extracted, re-hosted, and linked in the migrated note to maintain visual fidelity.

Jiva users are resolved by email match against Freshsales agents. Unmatched users are flagged in the migration report with a fallback owner assignment option. Active Jiva users without Freshsales accounts can be created as agents before migration or assigned to an admin placeholder.

Jiva tags on contacts, companies, and deals migrate as Freshsales Tags. Tag names are preserved exactly. Tags used for segmentation in Jiva should be reviewed post-migration for Freshsales workflow triggers. This ensures that segmentation logic aligns with Freshsales' automation capabilities and avoids unintended tag behavior.