Migrate from Real Intelligence to HighLevel

Real Intelligence Contact records map directly to HighLevel Contacts. Email, phone, name, address, and custom contact properties migrate to corresponding HighLevel contact fields. Owner resolution matches by email against HighLevel user accounts — unmatched owners flag for admin assignment before the full run.

Real Intelligence Company records map to HighLevel Companies. Company name, domain, industry, employee count, and revenue fields migrate directly. Parent-child company hierarchies in Real Intelligence map to HighLevel's parent company relationship. Multi-company associations on contacts collapse to a primary HighLevel Company plus secondary relationships.

Real Intelligence Deal records migrate to HighLevel Opportunities. Deal name becomes Opportunity name, amount maps to monetary value, close date maps to Close Date. Pipeline assignment and stage status translate to HighLevel Pipeline and Stage — each Real Intelligence pipeline becomes one HighLevel Pipeline with its stage set.

Each Real Intelligence pipeline creates a new HighLevel Pipeline in the destination. Pipeline-level settings (if any) such as probability rules or stage categories need HighLevel admin configuration. The migration plan documents which Real Intelligence pipeline maps to which HighLevel pipeline by name match or admin specification.

Stage names map value-by-value from Real Intelligence into HighLevel Stages. Each stage's probability percentage and category (Open, Won, Lost) are re-applied in HighLevel's stage configuration. Stage-entered timestamps are preserved as custom datetime fields on the Opportunity if Real Intelligence tracks stage history.

Real Intelligence call logs, email logs, and meeting records map to HighLevel Tasks with the Type field set to Call, Email, or Meeting respectively. Original activity timestamps and assigned owner migrate with each record. Notes in Real Intelligence become HighLevel Notes attached to the parent contact, company, or opportunity.

Real Intelligence custom objects migrate to HighLevel Custom Objects via the Custom Objects API. Each custom object in Real Intelligence creates a corresponding custom object type in HighLevel, and its fields map to HighLevel custom fields on that object. Relationships between custom objects need junction objects in HighLevel if the source uses many-to-many associations.

Real Intelligence owner records resolve to HighLevel users by email address match. Active HighLevel users in the destination account are enumerated before migration, and Real Intelligence owners without a match are assigned to a fallback owner or held for admin decision. This prevents records landing without an owner assignment.

Real Intelligence tags on contacts and companies migrate to HighLevel Tags. Tags are preserved as text labels attached to the same records in HighLevel. Note that HighLevel tags operate on contacts, companies, and opportunities — tag-based segmentation works the same way in both platforms.

Real Intelligence workflow definitions cannot be transferred to HighLevel. HighLevel Workflow Builder uses its own trigger-action architecture. FlitStack exports your Real Intelligence automation definitions (triggers, conditions, actions) as a structured document your HighLevel admin uses to rebuild them. This is not data — it is configuration that requires manual recreation.

File attachments on Real Intelligence records are downloaded and re-uploaded to HighLevel's file storage. File size limits apply — HighLevel handles files up to the plan limit, and oversized files are flagged for manual handling. Inline images embedded in notes are extracted from the source, rehosted on HighLevel's file servers, and re-embedded in HighLevel Notes to preserve visual context.