Migrate from Higher Logic Thrive to HubSpot

Thrive members map directly to HubSpot contacts. Email is the required unique identifier — Thrive members without an email address are flagged and assigned a placeholder or merged with an existing HubSpot contact by name + company match before migration.

Thrive organizations map to HubSpot companies. Parent-child organizational hierarchies in Thrive map to HubSpot's Parent Company field. Members linked to multiple Thrive organizations get their primary org as the HubSpot CompanyId lookup; secondary orgs surface as additional company associations on the contact.

Thrive discussion threads become HubSpot Notes attached to the originating contact. The note body contains the thread summary; metadata tags encode the thread type (Discussion), reply count, like count, and original post date. Full thread replies are appended to the note body to preserve context.

Thrive community events map directly to HubSpot Events with event name, description, start and end datetimes, and venue location preserved. Registration status and attendance counts transfer as custom fields on the HubSpot event record since HubSpot tracks event registrations as separate contact associations rather than fields on the event itself. Per-member attendance status from Thrive maps to a custom picklist property on the contact record.

Thrive file attachments (on discussions, library entries, blog posts) are downloaded and re-uploaded to HubSpot's File Manager, then linked to the appropriate contact or company record by ID. Inline images in discussion posts are extracted and hosted as HubSpot files with the note referencing the file URL.

Thrive security groups govern site access and permissions. These map to HubSpot static lists for segmentation purposes, but the access-control semantics do not transfer — HubSpot lists are marketing and routing constructs, not permission gates. Security configuration must be rebuilt in HubSpot's privacy and access settings.

Thrive custom fields and demographic attributes — expertise tags, volunteer history, certification status, mentor relationships — have no native HubSpot equivalent. Each custom field requires a corresponding HubSpot custom property created before the migration run. Multi-select Thrive fields (e.g., expertise tags) become comma-separated text fields or multi-checkbox properties in HubSpot.

Thrive blog posts authored by members migrate as Notes on the author contact, with the post title, publication date, view count, and slug stored as metadata in the note body. The full post content is included for reference. HubSpot's blog tool is a separate CMS function not relevant to member-relationship data.

Thrive ideas and Q&A posts become Notes with type labels (Idea or Q&A) and status metadata (e.g., Submitted, Under Review, Answered). The idea status field from Thrive maps to a custom picklist property on the note to preserve the workflow state at migration time.

Thrive community groups — subgroups, committees, chapters — map to HubSpot static lists for each group. Contact membership in multiple groups results in multiple list assignments. The group name and join date are preserved as list metadata and as a custom text property on the contact record.

Thrive announcements are broadcast messages that can be linked to member recipients. Each announcement becomes a Note on the recipient contact with the announcement title, send date, and content. The link between announcement and member is preserved via the note association.