Migrate from Insider to HighLevel

Insider user profiles map directly to GoHighLevel Contacts. Standard profile attributes (email, phone, first_name, last_name, device identifiers) migrate via GoHighLevel's Contact API upsert. We use email as the dedupe key. Custom user attributes from Insider become GoHighLevel Custom Fields scoped to Contact; we pre-create the field schema in GoHighLevel before import and preserve the original attribute key as a label for admin reference.

Insider behavioral events (page views, purchases, cart actions, custom events) do not have a native GoHighLevel equivalent as discrete records. We migrate significant events as GoHighLevel Tasks with TaskSubtype=Task and a custom body containing event_name, event_parameters, and timestamp. High-frequency tracking events (scroll depth, passive page views) are scoped to exclude from migration to keep the Contact timeline usable; the customer selects the event types to preserve during discovery.

Insider segments are defined by attribute rules and event conditions. We export the member list (user IDs in segment) and the segment rule definition as metadata. Member list migrates as GoHighLevel Tags assigned to the corresponding Contacts. The rule logic itself is documented in the journey inventory deliverable; GoHighLevel Smart Lists are the closest equivalent for dynamic membership based on attribute conditions, but the customer must rebuild the logic visually in GoHighLevel's segmentation UI.

Insider Journeys (multi-step event-triggered workflows) have no export endpoint. We deliver a written audit of every active Journey documenting its entry trigger, conditional gates, channel steps, delay actions, and exit conditions. The customer's GoHighLevel admin rebuilds each Journey as a Workflow using GoHighLevel's Trigger-Action canvas. We do not migrate automation logic as code because the platform models are structurally incompatible.

User tags export as an array per Insider profile. Tags migrate to GoHighLevel as Contact Tags via the Tags API. Each distinct Insider tag string becomes a GoHighLevel tag. Tags used for behavioral classification are preserved; the customer decides during scoping whether tags map to GoHighLevel Tags, Custom Fields, or a combination based on how tags drive reporting in GoHighLevel.

Insider product catalog data (sku, name, price, category, images, custom attributes) maps to GoHighLevel Products. SKU maps to SKU field; name maps to Name; price maps to Price; category maps to a custom field Category__c. Product images migrate as URLs stored in a custom field ProductImageUrl__c because GoHighLevel Products do not natively store image attachments.

Insider transaction records (order_id, total, items, currency, timestamps) map to GoHighLevel Opportunities with a custom Opportunity type Order. The transaction items array is stored as a JSON string in a custom field TransactionItems__c because GoHighLevel Opportunities do not natively support line item arrays without the Salesforce integration. We set Opportunity Stage to Closed Won at migration time to reflect completed transactions.

Insider static Lists are user collections with manual membership. We export list membership (user ID + list ID) and recreate membership as GoHighLevel Tags. Each Insider list name becomes a GoHighLevel tag prefixed with List_ for disambiguation from behavioral tags. Dynamic segments requiring ongoing membership updates are documented as Smart List candidates for GoHighLevel rebuild.