Migrate from Jiva to HubSpot

Jive user profiles map to HubSpot contacts. Display name maps to firstname/lastname, email maps directly, title maps to jobtitle, and department maps to a custom property. Jive profile URL is preserved as a custom text property for traceability. We also store the Jive user ID as a custom field for delta-run de-duplication.

Jive companies map to HubSpot accounts. Company name maps to Account Name and domain maps to Website directly. If Jive stores employee count or industry, those map to standard Account fields. Parent-company hierarchies map via Account.ParentId. The mapping also preserves the original Jive company ID in a custom field for future reference.

Jive users belong to many spaces in a many-to-many relationship. HubSpot contacts have a single primary company. We create a User_Space_Membership__c custom object keyed by contact and space name so no Jive community membership is lost. This custom object also tracks the member's role within each space, preserving permission levels if needed.

Jive projects map to HubSpot deals. Project name maps to dealname, budget amount maps to amount, and project status values (Active, On Hold, Completed) map to HubSpot deal stage via value mapping per pipeline. We also map the project owner email to a HubSpot owner ID, linking the deal to the responsible rep.

Jive blog posts map to HubSpot Notes attached to the author contact. Post title becomes Note title and body becomes Note body. Threaded replies are not preserved as separate objects; they append to the Note body. If a post includes attachments, the file links are stored within the Note body for quick access.

Jive discussion threads map to HubSpot Notes. Thread subject becomes Note title and the original post body becomes Note body. The threaded reply structure is flattened into the body content. We preserve the thread's creation timestamp as a custom property on the Note to retain temporal context.

Jive documents map to HubSpot Notes with the document name as subject and content as body. File attachments are re-uploaded to HubSpot Files with the Note body containing the link. Large files may require HubSpot storage tier review. We verify each file against HubSpot's allowed extensions and size limits before uploading.

Jive reputation scores have no HubSpot equivalent. We create a custom number property Jive_Reputation_Score__c on the Contact object to preserve each user's community standing. This property is updated each time a user's reputation changes in the source system, allowing historical tracking.

Jive profile creation date and last activity date migrate as HubSpot Original_Create_Date__c and Last Modified date fields. System-level timestamps are not overwritten by migration tooling. These timestamps are used in HubSpot reports to filter contacts by their original Jive activity period, aiding in cohort analysis.

Jive tags attached to user profiles migrate to HubSpot contact tags. If the number of tags per contact is large, the list is stored in a custom property with a note about the HubSpot tag character limit. We also note any tag that exceeds HubSpot's 100-character limit for proper handling.

Jive user status values (Active, Inactive, Archived) map to HubSpot lifecycle stage via value mapping. Active maps to Customer or Lead; Inactive and Archived map to Evangelist or a custom status. Inactive and Archived statuses are mapped to custom lifecycle stages you define, ensuring alignment with your sales process.

Each Jive user profile has a unique URL that has no HubSpot equivalent. We create Jive_Profile_URL__c as a custom text property on the Contact so old Jive links remain traceable. This property is indexed for search, allowing you to locate records by their original Jive URL quickly.