Migrate from Higher Logic Thrive to Microsoft Dynamics 365 Sales

Higher Logic Thrive Contact/Member records map to Dynamics 365 Contact. If the member belongs to a Community Group that functions as an organizational unit, we create a Dynamics 365 Account record for the group and link the Contact via the AccountId lookup, preserving the member-to-organization relationship. Member demographics and custom fields migrate as custom contact fields. We flag records with privacy-sensitive fields before export per the Directory export gotcha and deliver a sanitized export for customer review before loading.

Community Groups in Higher Logic Thrive that represent organizations rather than interest-based cohorts map to Dynamics 365 Account records. We use the Group Name as Account Name and the Group's primary contact as the primary Contact lookup. Group Manager email lists built around Community Group membership translate to Dynamics 365 Marketing Lists or Campaign Member lists that the customer's admin rebuilds from the exported group-to-member mapping spreadsheet.

Higher Logic Thrive Security Groups control access permissions within the community. We map Security Group assignments to Dynamics 365 Team membership. Each Security Group becomes a Dynamics Team, and we link the original Higher Logic Key and Legacy Key in custom fields on the Team record for audit traceability. The mapping preserves which members belong to which security tiers.

Higher Logic Thrive Discussion threads map to Dynamics 365 Notes attached to the Contact record of the thread author. The post body, @mentions, and #hashtags migrate as rich-text Note body with @mentions preserved as plain-text references. Long threads are chunked to avoid Note body truncation. The original thread post timestamp migrates as the Note CreatedDate for timeline ordering. We do not migrate the hierarchical reply structure as a nested object; each post becomes a standalone Note.

Higher Logic Thrive Events with registrations map to Dynamics 365 Campaign records. Event name becomes Campaign Name, event description becomes Campaign Description, and start/end dates map to Campaign StartDate and EndDate. Registered attendees become CampaignMember records linked to the Campaign and to the Contact record. Attendance tracking data migrates as Campaign Member Status values. We map event export CSV files as structured Campaign datasets.

Higher Logic Thrive marketing campaigns and email message content migrate as Dynamics 365 Campaign records with Campaign Type set to Email or Newsletter. The campaign name and message content migrate; trigger conditions, automation logic, and engagement workflows require rebuild in Dynamics 365 Power Automate or a marketing automation tool. We deliver a campaign inventory spreadsheet listing every active campaign with its trigger criteria and recommended replacement approach.

Higher Logic Thrive's 30 Custom Field slots per account map to custom fields on the Dynamics 365 Contact entity. We audit the full Custom Field inventory during scoping, identify any orphaned or deprecated fields that should be dropped, and recreate active Custom Fields as typed Dataverse fields (text, number, date, picklist) on the Contact entity before migration. Custom Field values resolve dynamically at send-time in Thrive; they become static field values in Dynamics after migration.

Higher Logic Thrive Resource Library files attach to communities. We export the file directory with full paths and map files to their parent Contact or Account records as Notes with file attachments. Dynamics 365 does not have a native resource library object; the recommended path is SharePoint Online document management linked via the native SharePoint integration. We flag this for the customer's admin to configure post-migration and deliver the file inventory as a structured dataset.

Higher Logic Thrive User Lists and Group Manager segments export as list definitions and criteria. Dynamics 365 Marketing Lists store the resulting membership but not the criteria logic. We export list membership as Contact ID sets and deliver a marketing list import file. List criteria must be rebuilt from the exported definition spreadsheet; the customer's admin recreates the dynamic list logic in Dynamics 365.

Files attached to discussion posts, library items, and user profiles migrate as Dynamics 365 Notes with the isAttachment flag set to true and the binary file stored in the Note's Document body. We require a file directory with full paths per object and verify path integrity before import. Re-parenting to the correct Contact, Account, or Campaign record happens during the mapping phase.