Migrate from Higher Logic Thrive to Twenty CRM

Higher Logic Contact and Member records map directly to Twenty Person. We preserve the full contact profile including name, email, phone, address, and demographics. The AMS-sourced demographic fields that sync via the Higher Logic Push API are included in the export and mapped to typed Twenty Custom Fields. Privacy-sensitive fields (email addresses in Directory exports that ignore privacy settings) are flagged before import so the customer can review and sanitize the dataset.

Higher Logic Community Groups control membership and feature access for Discussions and Libraries. We map each Community Group to a Twenty Tag on the Person record, preserving group membership as tag associations. If the customer requires group-level access controls in Twenty, we document the group-to-permission mapping for rebuild in Twenty's Roles and Permissions or as a Custom Object tracking group affiliations.

Higher Logic Security Groups control access permissions and visibility. We export the Security Group affiliations for each member and document the mapping in the automation inventory deliverable. Twenty does not have a direct Security Group equivalent, so access control requirements are translated into a recommendation for Twenty Roles and Permissions configuration or a Custom Object tracking permission tiers.

Higher Logic Discussion threads (posts with replies) map to Twenty Note records attached to the Person of the original author. Each post body migrates as a Note with the thread hierarchy preserved by nesting Notes under a parent or by adding a custom thread_id field. @mentions and #hashtags are preserved as plain text links. Large threads are chunked to avoid truncation; we flag any thread exceeding 32,000 characters for manual review.

Higher Logic Resource Libraries contain documents and media attached to communities. We map each library entry to a File in Twenty linked to the relevant Person or Company record. The export must include full file paths per object; we verify path integrity during import scoping and re-link files to their parent Person or Company record. If the export omits file paths, we flag the gap and request a corrected dataset before migration begins.

Higher Logic Events with registrations and attendance tracking map to Twenty Activity records with a custom event-type indicator. Event date, time, location, and description migrate directly. Registrant associations map to Person lookups on the Activity. Attendance status (registered, attended, no-show) migrates as a custom Activity field.

Higher Logic Marketing Campaigns and message content map to a Campaign Custom Object in Twenty. We export campaign structure and message content including subject, body, send history, and trigger conditions. Automation triggers and workflow logic require rebuild in Twenty Workflows; we document every campaign trigger and condition in the automation inventory deliverable. The customer or a Twenty partner rebuilds triggers post-migration.

Higher Logic Custom Fields (up to 30 per account) and Enhanced Personalization Fields (separate, UTF-8, 250-character limit) both migrate to Twenty Custom Fields. We deduplicate any field name collisions, remap text and date field types to equivalent Twenty field types, and validate UTF-8 encoding during the sample dataset review. Fields exceeding 250 characters are flagged for truncation review before migration.

Higher Logic User Lists and Group Manager segments are exported with their criteria definitions. Twenty does not have a native segment builder equivalent; we document each list's criteria (filters, conditions, membership rules) in the automation inventory for the customer's admin to rebuild as a static Custom Object or as a manual list in Twenty's table view.

Higher Logic Landing Pages with Form Field zones cannot be migrated as functional pages in Twenty. We export Landing Page content as structured HTML or CSV files for the customer to review. Form field definitions (which accept Custom Fields) are documented separately so the customer can recreate form fields in Twenty's native form builder or a third-party form tool. This is explicitly out of scope for migration as code.

Higher Logic pre-built reports with configurable column exports do not migrate. We capture report exports as-is (limited to currently visible columns) as reference files during the sample dataset review. The customer's admin rebuilds reports as Twenty dashboards with the Table, Kanban, or Calendar view types that match their analytical needs. Custom segmentation and metric requirements are documented in the automation inventory.

Files attached to discussion posts, library items, and user profiles migrate as Files in Twenty linked to the parent Person, Company, or Activity record. We require a file directory with full paths per object during scoping and verify path integrity before import. Attachments without resolvable paths are flagged for manual path resolution before the production migration begins.