Migrate from Jiva to Microsoft Dynamics 365 Sales

Jiva Users map 1:1 to Dynamics 365 Contacts. Email address becomes the Contact.Email field for identity resolution. Jiva display name splits into FirstName and LastName where available; single-string names store in LastName with FirstName blank. Jiva user ID persists as Source_System_ID__c for delta-run deduplication.

Jiva Places represent organizational units or project spaces. They map to Dynamics 365 Accounts where the place functions as a company or external organization. Internal-only places with no external counterpart may become custom Place__c entities or be archived, depending on business requirement. Place creation date migrates as a custom datetime field.

Jiva internal places without an external-organization counterpart require a custom Place__c table in Dynamics 365. We create the custom entity with fields for Place name, description, creation date, and a lookup to the owning Account. Security roles are not migrated and must be rebuilt using Business Unit and Security Role configuration in Dynamics 365.

Jiva Discussion threads map to Dynamics 365 Notes. The top-level Discussion subject becomes Note.Title; the original body HTML converts to Note.Body (rich text). Original author email resolves to a Contact OwnerId. Thread depth (Reply objects) collapses into a single Note with all replies appended in chronological order as a text block.

Jiva Reply objects do not have a direct Dynamics 365 equivalent. We merge all Replies under a Discussion into the parent Note's body as a structured text block: each Reply shows the author name, timestamp, and body text on separate lines. This preserves full conversation history without creating orphan records.

Jiva Documents inside Places map to SharePoint Document Locations in Dynamics 365 tied to the corresponding Account or custom Place record. File binary content re-uploads to the target SharePoint library. We store the original Jiva document URL as a custom External_Doc_Link__c field for reference. File size limits from Dynamics 365 apply (default 10 MB via browser upload, higher via API).

Jiva direct messages between users split based on business value: messages with external recipients or content relevant to the sales record migrate as Email (Activity) on the Contact. Purely internal social messages with no CRM business value are archived to a custom Message_Archive__c entity as reference data rather than active records.

Jiva Bookmarks have no Dynamics 365 equivalent. We create a custom Bookmark__c entity linked to the bookmarking User (Contact) and the target Jiva object (Discussion, Document). Bookmark date migrates as a datetime field. This captures user interest signals without cluttering standard CRM objects.

Jiva engagement metrics such as Like count, View count, and Score are mapped to custom number fields on the target Dynamics 365 entity: Jiva_Likes__c, Jiva_Views__c, and Jiva_Score__c fields are created on the Contact or custom Place record. These fields preserve historical interaction data for reporting but do not trigger any Dynamics 365 workflow or business logic.

Jiva Tags on content objects migrate as a comma-separated text string in a custom Jiva_Tags__c field on the target Dynamics 365 entity. For high-value taxonomy, tags can also generate a custom Tag__c entity with a many-to-many relationship table if the tag library warrants it.

Jiva @mentions inside Discussion bodies and Replies migrate as plain @username text within the Note.Body field. Dynamics 365 does not support @mention notifications on Notes. The original mention text is preserved for context even though the notification behavior does not transfer.

Jiva Analytics Export service data (place activity, user login frequency, content contribution metrics) maps to a custom Analytics__c entity linked to the Place and User. This data supports post-migration reporting continuity but does not drive standard Dynamics 365 Sales workflows.