Migrate from matrix to HighLevel

Direct map. Matrix contacts migrate to HighLevel Contacts with all standard fields (name, email, phone, address). The primary company association in Matrix maps to the Contact.CompanyId lookup in HighLevel. Owner resolution happens by email match against HighLevel user accounts before migration commits.

Direct map. Matrix company records map to HighLevel Companies. Company name, domain, industry, employee count, and revenue fields migrate to corresponding HighLevel Company fields. Parent-company hierarchies in Matrix map to HighLevel's parent-company association where applicable. Additional address and social profile fields are also transferred to complete the company profile in HighLevel.

Direct map. Matrix deals migrate to HighLevel Opportunities. Each deal's pipeline assignment determines the target HighLevel pipeline. Deal stage names map value-by-value to HighLevel pipeline stage names, preserving probability and forecast category from the source. Associated activities and notes linked to the deal are also migrated to maintain complete deal history.

Matrix deal pipelines map to HighLevel Pipelines. Each Matrix pipeline becomes one HighLevel pipeline with its own set of stage definitions. Stage order, probability weights, and forecast categories are translated per pipeline. Multi-pipeline setups in Matrix create corresponding multi-pipeline structures in HighLevel.

Stage names are mapped value-by-value from Matrix to HighLevel. The order of stages is preserved. Probability percentages associated with each stage in Matrix are applied to the corresponding HighLevel stage definition during setup. Closed-won and closed-lost stage handling is preserved identically.

Matrix tags serve triple duty: segmentation, lifecycle state, and workflow triggers. FlitStack maps each tag to either a HighLevel Tag (for simple labels) or a HighLevel Custom Field pick-list (for tags that encode state like lifecycle_stage or deal_priority). Which approach applies is decided during the planning phase and documented in the migration map before data moves.

Matrix tasks migrate to HighLevel Tasks linked to the parent Contact or Company record. Original due dates, assignees, and completion status are preserved. Tasks that were completed in Matrix carry their completed timestamp into HighLevel. Task priorities and descriptions are also transferred to ensure full task context is available in the target system.

Matrix notes migrate to HighLevel Notes attached to the relevant Contact or Company. Rich-text formatting in Matrix notes is converted to HighLevel's note format. Timestamps and note authors are preserved as metadata on the HighLevel Note record. Any embedded links or attachments referenced in notes are flagged for manual review if they cannot be automatically transferred.

Matrix custom fields on Contacts, Companies, or Deals require pre-creation in HighLevel before data import. FlitStack generates the custom field definitions (with correct field type — text, number, date, pick-list, checkbox) and applies them to the target HighLevel object before the migration run. Field type mapping is documented in the pre-migration plan.

Matrix custom objects (if present) map to HighLevel Custom Objects using the HighLevel Custom Objects API. Relationships between custom objects and standard objects (Contact, Company, Opportunity) are mapped to corresponding HighLevel relationship definitions. N:N relationships use HighLevel junction-object patterns. Field-level validation rules are preserved to maintain data integrity.

File attachments stored on Matrix records are downloaded and re-uploaded to HighLevel's file storage, then linked back to the appropriate contact, company, or opportunity record. File size limits apply (HighLevel's upload limits). Original filenames and MIME types are preserved. Any files exceeding HighLevel's size limits are flagged in the migration report for alternative handling.

Matrix owner assignments on contacts, companies, and deals are resolved by email match against HighLevel users. If a Matrix owner has no matching HighLevel user (because the person has not been invited yet), records are assigned to a designated fallback HighLevel user and flagged for post-migration owner re-assignment.