Migrate from Jiva to Salesforce Sales Cloud

Jiva user profiles map directly to Salesforce Contacts. Name, email, phone, and title carry over as standard fields. Jiva user type (employee, customer, partner) has no Salesforce equivalent — it migrates as a custom pick-list field (Jiva_User_Type__c) on Contact. Jive user GUID is stored as Source_Jiva_ID__c for de-duplication and delta-run traceability.

Jiva places (groups, spaces, communities) have no Salesforce equivalent — Accounts are the closest CRM analogue. Place name and description map to Account Name and Description. Nested place hierarchies are flattened: the top-level place becomes the Account, and each child place is stored as a custom text field (Parent_Place__c) containing the parent place name. Teams should rebuild group hierarchies using Salesforce sharing rules or custom junction objects post-migration.

Jiva allows a user to belong to many places (N:1 user-place). Salesforce Contacts have a single primary Account. Jiva membership records are merged into a custom junction object (Jiva_Place_Membership__c) with Contact__c and Place_Name__c fields, preserving the full list of places each user belonged to in Jiva.

Jiva discussions with an action or resolution expectation map to Salesforce Tasks (subject, status, priority, due date). Discussions that represent knowledge-base content (how-to threads, policy discussions) map to Salesforce Notes. The original Jiva author, creation date, reply count, and view count are stored as custom fields on the target record so engagement history is not lost.

Jiva documents with title, author, and body text map to Salesforce Notes for the text content. The actual file attachment is re-uploaded as a Salesforce File (ContentDocument / ContentVersion) and linked to the relevant Contact or Account. The original Jiva blob storage URL is preserved as Jiva_Document_URL__c custom text for reference.

Files attached to Jiva documents are re-uploaded to Salesforce Files. Salesforce Files carry a 25MB per-file size limit; files exceeding this threshold are flagged for chunked upload. The original Jiva attachment URL is stored as Jiva_Attachment_URL__c on the Salesforce File record for traceability.

Jiva polls (question, options, vote counts) have no Salesforce standard equivalent. FlitStack creates a Jiva_Poll__c custom object with fields for the poll question, each option, and vote tallies. Poll participation records migrate as entries in this custom object linked to the relevant Contact or Account via a lookup field.

Jiva direct messages and inbox threads are action-oriented and map to Salesforce Tasks with the message subject as Task Subject, the body as Description, and the sender as Task Owner. Archived or historical messages stored as Tasks with Status = 'Completed' so they appear in Salesforce records without cluttering open work queues.

Jiva call, email, and task activities carry over as Salesforce Tasks. Task Type distinguishes activity kind (Call, Email). Original Jiva activity timestamps are preserved as custom datetime fields since Salesforce CreatedDate reflects migration time rather than the original activity date.

Jiva bookmarks are a social feature with no Salesforce CRM analogue. Bookmark counts per user-content pair are stored as a custom numeric field on the Contact (Jiva_Bookmark_Count__c). The bookmarked content reference is stored in a custom text field (Jiva_Bookmarked_Content__c) for audit purposes only — bookmarks do not become functional Salesforce records.

Jiva supports extended user profile fields beyond name and email (department, location, manager, hire date, follower count). Each extended field requires a corresponding custom field on the Salesforce Contact object. Pick-list fields in Jiva become pick-list fields in Salesforce; text fields become text fields. Follower count and reputation score migrate as Number fields.

Jiva content objects support custom properties (content extended fields). Each custom property needs a corresponding custom field on the Salesforce Note or Task object that receives the content. Pick-list values in Jiva require explicit value-by-value mapping to Salesforce pick-list values if the target field is a pick-list; otherwise they migrate as text.