Migrate from Intrix CRM to HighLevel

Intrix Client records map directly to GoHighLevel Location. The 360° overview data (industry, contact info, overview notes) transfers as Location fields and custom properties. GoHighLevel's Location object serves as the account-level record equivalent. We use the Intrix Client ID stored in a custom property for reconciliation if the customer ever references back to the source data.

Intrix Contact records map to GoHighLevel Contact, preserving the parent-Client relationship through a custom custom_intrix_client_id field that references the imported Location. GoHighLevel's contact-centric model means every Contact belongs to a Location; we resolve the LocationId at migration time using the stored Client ID. Duplicate detection runs on email address as the primary key.

Intrix Opportunities map to GoHighLevel Deals with stage, value, expected close date, and owner assignment preserved. Custom stage names from Intrix require field-value mapping to GoHighLevel pipeline stage values defined in the destination's pipeline JSON. We extract the active pipeline stage configuration during scoping and configure the corresponding GoHighLevel pipeline before Deals import.

Intrix's configurable pipeline stages are customer-specific. We extract the customer's active stage configuration during audit, create the corresponding pipeline and stage definitions in GoHighLevel using the pipeline settings JSON, and map stage probability values if present in Intrix. Custom stage colors and ordering replicate where the destination supports these attributes.

Intrix Activities (calls, emails, meetings, tasks) map to GoHighLevel Activities with timestamps, owners, and descriptions preserved. Activity type is stored as a tag or custom field in GoHighLevel. We resolve the owner by email match to a GoHighLevel user before inserting, and link activities to the correct Contact or Deal using the relationship fields populated during the Contact and Deal import phases.

GoHighLevel has no native project management module. We map each Intrix Project to a GoHighLevel Deal with a custom field storing the original project name, project type designation, and project manager. Task dependencies from the Intrix dependency graph are flattened and sequenced: tasks with no predecessors become GoHighLevel Tasks under the Deal, and tasks with dependencies are imported after their predecessors using the original completion logic preserved as a custom ordering field.

Intrix Tasks inherit project context and deadline automation. We import tasks as GoHighLevel Tasks linked to the parent Deal (from the project mapping). For standalone tasks not tied to a project, we create unparented Tasks. Dependency sequencing is enforced by importing tasks in the order dictated by the extracted dependency graph so that GoHighLevel does not flag a predecessor requirement against a task not yet present.

WHR is available only on Intrix Advanced and Unlimited tiers. We confirm active module access during scoping. Since GoHighLevel Standard plan lacks native time tracking, WHR maps to a custom Time Entry object we create in GoHighLevel before import, with fields for employee, date, hours, project reference, and notes. Basic tier accounts will have no WHR data to migrate; we flag this during scoping to avoid flagging absent data as a migration failure.

Support Tickets are an add-on module on Intrix Advanced and Unlimited tiers. GoHighLevel's native inbox is not a full ticketing system with status workflows and assignee tracking. We create a custom Ticket object in GoHighLevel with status, assignee, priority, and description fields, and migrate ticket thread history as comments linked to the Ticket record. Email thread flattening (converting threaded email to flat comment entries) is handled during transformation.

Intrix custom fields on each object map to GoHighLevel custom properties of equivalent type where supported. GoHighLevel's custom property types do not cover every Intrix field type; we flag any unsupported types during scoping with a recommended alternative (such as using a text field as a fallback for unsupported field types). Custom field schema per object is extracted in full before any data transform begins.

Intrix stores attachments per Client, Contact, or Project record. We download files individually from Intrix's attachment storage and re-upload to the corresponding GoHighLevel record (Location, Contact, or Deal). The file-per-record structure creates bulk import overhead for records with multiple attachments. We batch attachments by object, download all files before import begins, and re-upload in sequence during the corresponding object phase.

Intrix User records including access levels and role assignments map to GoHighLevel Users. We match users by email address. Inactive Intrix users require explicit reassignment of their records to an active GoHighLevel user before migration; records owned by inactive users are reassigned to the customer's designated admin or team lead during the migration window.

Intrix integrations with MailChimp, Google Calendar, and AccountingBox store connection credentials and sync state that cannot be exported. We document all active integrations during the audit phase and provide reconfiguration instructions for each platform. We advise exporting any email conversation history directly from the integrated email platform rather than relying on Intrix's activity log as the sole record of those communications.