Migrate from RedEye to HighLevel

RedEye Contacts migrate to GoHighLevel Contacts with all standard properties (name, email, phone, address) and custom fields preserved. RedEye's behavioural enrichment signals (engagement scores, lifecycle stage values) migrate as custom fields on the GoHighLevel Contact record. We deduplicate by email address during import and flag any contacts exceeding the pre-flight record count for customer review before import begins.

RedEye's lighter-weight company associations migrate to GoHighLevel Accounts. Since RedEye's B2C model treats Contacts as the primary record, company linkage migrates as a custom property on the GoHighLevel Contact and a corresponding Account record created for each distinct company domain. The Account-Contact relationship is established during the import phase after Account records are inserted.

RedEye Deals migrate to GoHighLevel Opportunities with the pipeline configured in GoHighLevel before migration. We create a GoHighLevel pipeline matching the RedEye deal stages, map stage values, and configure the Opportunity record type. Deal value, close date, and owner migrate directly. Any custom deal properties become custom fields on the GoHighLevel Opportunity.

RedEye Campaigns migrate as GoHighLevel Workflows with channel assignments and timing rules preserved. Campaign metadata (name, description, status, start and end dates) migrates directly. Channel assignments (email, SMS, etc.) require reconfiguration in GoHighLevel because RedEye's channel format is not directly portable. We document the channel assignments in the scoping deliverable for manual configuration.

RedEye Customer Journeys are visual workflow definitions with branching logic tied to contact behaviours and lifecycle stages stored in a proprietary format that cannot be directly exported. We extract the journey tree structure as a structured rule document during the scoping phase and rebuild it in GoHighLevel using equivalent triggers, conditions, and branches in the Automation builder. The rebuild requires a mapping session with the customer to confirm behavioural trigger equivalence between platforms.

RedEye behavioural events (website actions, email opens, purchase triggers, custom events) migrate as GoHighLevel Tasks in the contact activity timeline. Event type, timestamp, and associated contact identifier are preserved. GoHighLevel's activity timeline supports custom Task types, so we create type-labelled task records matching the RedEye event taxonomy.

RedEye Product records (SKU, name, pricing, category) migrate as GoHighLevel Products. Unlimited product records are supported on both platforms, so no tier constraint applies. Product catalogue hierarchies from RedEye migrate as GoHighLevel product categories.

RedEye contact and campaign tags migrate as GoHighLevel Tags on the corresponding record. Tag names are mapped exactly. Any tag characters unsupported by GoHighLevel's schema are flagged during scoping for customer review and renaming before import.

RedEye Segments (dynamic contact groups based on behavioural rules and demographic criteria) migrate as GoHighLevel Smart Lists with filter criteria rebuilt using GoHighLevel's equivalent conditional logic. We export segment definitions as rule sets and document them in the scoping deliverable for reconstruction in GoHighLevel's Smart List builder.

RedEye's up-to-nine channel configurations at the campaign level migrate as a configuration inventory. GoHighLevel supports built-in Email, SMS (via Twilio or LC Email), and Voice channels natively. Any RedEye channels not natively supported in GoHighLevel are flagged during scoping for manual configuration after migration.