Migrate from Resulticks to HighLevel

Resulticks Contacts migrate to GoHighLevel Contacts as the primary record. Standard fields (first name, last name, email, phone, address) map directly. Custom Contact properties from Resulticks require schema inspection during scoping; we create GoHighLevel Contact custom fields of equivalent type (text, number, date, multi-select picklist) before migration. Contact owner assignment migrates by email lookup against GoHighLevel Users.

Resulticks audience definitions are behavioral event conditions applied against Contact attributes. Because GoHighLevel does not support event-condition-based dynamic segments (it uses Smart List filters on Contact field values), we translate Resulticks segments into GoHighLevel Smart Lists where the equivalent filter logic exists, or into Tags applied at the Contact level for segments that rely on behavioral event data not stored as Contact fields. The customer chooses the strategy during scoping.

Contact-level Tags migrate directly to GoHighLevel Tags. Tag distribution and counts are preserved at the Contact record level. Tags used for audience classification are migrated alongside segment translation so that the customer's segmentation logic remains operational post-migration.

Resulticks Campaign metadata (name, status, channel assignment, scheduling) migrates to GoHighLevel Campaign records. Campaign body content, copy, images, and offer codes are platform-stored assets that we flag for separate export from Resulticks' media library. Campaign performance metrics (open rates, click rates) are not migratable as analytics and are noted for manual re-entry or reference retention.

Resulticks Journey flows with branching logic, wait conditions, AI decision nodes, and multi-channel step sequences do not export. We photograph and document the full Journey map during discovery so the customer has a reference architecture for rebuilding in GoHighLevel's Workflow builder. Content assets within Journey nodes require separate extraction from the Resulticks platform.

Resulticks platform users migrate as GoHighLevel Users with role and permission assignments preserved. Owner assignment on Contacts and Campaigns is resolved via email lookup in the destination. Users without a matching GoHighLevel account are held in a reconciliation queue for the customer's admin to provision before migration resumes.

Custom fields vary by Resulticks account configuration and may include legacy field types, multi-select values, or date-derived computed fields. We inspect the field schema during scoping, create GoHighLevel Contact custom fields of compatible types, and apply type-transformation logic where Resulticks field types do not map directly to GoHighLevel field types.

Resulticks event history (page views, email opens, purchase events, custom track events) can be extensive. Due to schema variability and volume, we migrate a configurable event window (typically 12-24 months) and normalize behavioral events into GoHighLevel Activity records (Call, Email, Meeting, Note) attached to the Contact. Events without an equivalent GoHighLevel Activity type are summarized as Note records with the event type and timestamp preserved.