Migrate from Rechat to HighLevel

Rechat contacts map directly to HighLevel contacts. Email, phone, address, and name fields translate 1:1. Rechat's email metadata (subject, teaser, date) migrates as custom contact fields. Rechat tag assignments migrate as HighLevel tags. Owner resolved by email match to HighLevel users.

Rechat companies map to HighLevel companies with all standard fields translating directly. Company name, domain, address, phone, and custom fields migrate as-is. Parent-child company hierarchies in Rechat map to HighLevel's parent-company relationship field using the parentCompanyId lookup. Companies without contacts receive a placeholder note to flag for manual review.

Rechat deals map to HighLevel opportunities. Deal name, amount, stage, close date, and owner migrate as-is. Custom deal fields translate to custom opportunity fields. Rechat deal pipelines map to HighLevel pipeline stages — each pipeline becomes one set of stage values in HighLevel's pipeline builder.

Rechat pipelines translate as HighLevel pipeline configurations. Each Rechat pipeline stage becomes a stage in HighLevel's Kanban pipeline view. Stage names map value-by-value; stage order and probability percentages re-applied per HighLevel's stage configuration. Multiple Rechat pipelines require multiple HighLevel pipeline builds.

Rechat custom properties on contacts create custom fields in HighLevel. Data type mapping: text → text, number → number, date → date, picklist → picklist (with value mapping if options differ). Multi-select picklists in Rechat map to tag-based segmentation in HighLevel or a custom field with semicolon-delimited values.

Rechat deal custom properties translate to custom opportunity fields in HighLevel. The same data-type mapping rules apply across text, number, date, and picklist fields. Fields marked required in Rechat must be marked required in HighLevel before the migration run to avoid validation failures that could block the data load.

Rechat custom objects map 1:1 to HighLevel custom objects. Custom object field names and types translate per HighLevel's schema requirements. Custom object relationships (one-to-many, many-to-many) require junction objects in HighLevel when the source uses many-to-many associations — FlitStack surfaces these in the pre-migration schema plan.

Rechat notes migrate as HighLevel notes attached to the corresponding contact or opportunity. Note body, created date, and owner preserved during transfer. Notes with attachments — Rechat file attachments re-upload to HighLevel's file storage and linked back to the note record for complete record reconstruction.

Rechat does not store email body content — only subject, teaser, and date. This metadata migrates as a custom contact field (Email_Metadata__c) in HighLevel with a formatted string per email. Teams requiring full email history must rely on the source email system (Google/Outlook) for the actual body content.

Rechat's MLS integration links contacts and deals to listing data. HighLevel has no native MLS association model. Listing references migrate as custom text fields or external URL links for reference. MLS search functionality requires a separate integration rebuild in HighLevel.

Rechat's Lucy AI assistant configuration is real-estate-specific and non-portable. HighLevel's AI agents provide general-purpose conversational capabilities. The rebuild scope depends on Lucy use cases — lead qualification, listing queries, and appointment booking each map to different HighLevel AI agent configurations. Rebuilding requires defining agent prompts, conversation flows, and knowledge bases from scratch.

Rechat Flows do not migrate. The automation logic must be rebuilt in HighLevel's Workflow builder. FlitStack exports Rechat Flow definitions as a reference document with trigger/action documentation for your HighLevel admin to use during rebuild.