Migrate from Higher Logic Thrive to Salesforce Sales Cloud

Higher Logic Thrive Contacts and Members map to Salesforce Contact records. The Member Refresh cycle syncs AMS-managed demographics asynchronously, so we extract at a point-in-time snapshot during the export phase and preserve all demographic fields including custom demographics. Email, phone, address, and name fields map directly to standard Contact fields. The original Higher Logic Key is stored in a custom field higherlogic_key__c for audit and cross-reference.

Higher Logic Community Groups drive membership and feature access for Discussions, Libraries, and Microsites. Each group has unique membership that we map 1:1 during migration. We offer two destination strategies: map to Salesforce Account hierarchy if the groups represent organization-level entities, or map to a custom CommunityGroup__c object with a junction CommunityGroupMember__c object if group membership semantics differ from Account hierarchy. The customer selects the strategy during scoping based on their reporting and segmentation needs.

Higher Logic Security Groups control access permissions and visibility within the community, exporting with Higher Logic Key, Legacy Key, and Security Group affiliations. We preserve group assignments by mapping to a ThriveSecurityGroup__c custom object and linking members via a junction object. If the customer uses Salesforce Permission Sets for access control in Experience Cloud, we provide a mapping table from each Thrive Security Group to the corresponding Permission Set for the admin to apply post-migration.

Higher Logic Discussion threads (post body, author, timestamps, @mentions, #hashtags) require a destination decision before migration. If the customer licenses Experience Cloud, we map to Chatter FeedItem and FeedComment records preserving inline images, @mentions, and #hashtags. If Experience Cloud is not in scope, we map to a custom DiscussionPost__c object with a parent DiscussionThread__c, storing the post body as a rich text field and author @mentions as text references. Large threads are chunked to avoid truncation during export.

Higher Logic Resource Libraries contain document and media files attached to communities. We require a file directory with full paths per object and map files to ContentDocument records with the parent ResourceLibraryItem__c record linking to the appropriate Community Group. Path integrity is verified during import scoping; broken file references are flagged in the reconciliation report before delivery.

Higher Logic Events include registrations, attendance tracking, and CSV exports. We migrate Event records with StartDateTime, EndDateTime, Location, and Description to Salesforce Event, and attendee associations to EventRelation records linked to the registered Contact. Attendance status (registered, attended, no-show) maps to a custom field on EventRelation.

Higher Logic marketing automation campaigns with message content and send history map to Salesforce Campaign records. The campaign structure (name, type, status, dates) migrates directly. Email message content maps to Salesforce EmailTemplate or a custom EmailMessage__c object for body and subject. Trigger conditions and automation workflow logic do not migrate; we deliver a written inventory of every active campaign trigger, condition, and delay with a recommended Salesforce Flow or Marketing Cloud Account Engagement equivalent for the admin to rebuild.

Higher Logic Landing Pages with Form Field zones that accept Custom Fields do not have a direct Salesforce equivalent in Sales Cloud. The Nimble AMS integration explicitly does not support Landing Pages, which also signals that native integrations are limited. We export Landing Page content and form field definitions to a ThriveLandingPage__c custom object and recommend Salesforce Web-to-Lead or Experience Cloud forms as the replacement, with a form-field mapping table delivered in the handoff document.

Higher Logic Thrive limits each account to 30 Custom Fields used as personalization tokens in messages and landing page forms. We audit the full Custom Field inventory during scoping, identify any orphaned or deprecated fields, and map active Custom Fields to Salesforce custom fields on Contact (or a custom ThriveCustomData__c object if the 500-field limit per object is a concern). Field type mapping (text, number, date, checkbox) is defined during schema design, and token replacement logic must be rebuilt in Salesforce using merge fields or Flow.

Higher Logic List Builder criteria and Group Manager email lists are exported as segmentation definitions. The list membership criteria do not have a native Salesforce equivalent because Salesforce segments by Campaign membership or dynamic Report filters. We export list definitions with their criteria logic and recommend rebuilding segmented lists in Salesforce as Campaign Groups or saved Reports with filter criteria documented in the handoff.

Higher Logic pre-built reports with configurable columns export only currently visible columns. We capture the report export as-is, including all visible data, but the report definition (column configuration, filters, grouping, chart settings) must be manually recreated in Salesforce Reports. We deliver a written mapping of every source report to its closest Salesforce report type, including any custom fields that need to be added to the report layout.

Higher Logic Attachments on discussion posts, library items, and user profiles require a file directory with full paths per object. We verify path integrity, upload files as ContentVersion records, and link to the parent record (Contact, DiscussionPost__c, or ResourceLibraryItem__c) via ContentDocumentLink. Attachments without a resolvable parent are flagged in the reconciliation report.