Migrate from The Real Estate CRM to HighLevel

The Real Estate CRM contacts migrate directly to HighLevel contacts. All standard fields (name, email, phone, address) map 1:1. HighLevel's contact record supports custom fields for any The Real Estate CRM custom properties stored on the contact. The original create date is preserved as date_added, and the owner maps via email match to a HighLevel user. Tags from The Real Estate CRM import as HighLevel tags for segmentation.

Company records migrate to HighLevel companies with all standard fields preserved (name, website, phone, address, industry). If The Real Estate CRM stores a parent-company relationship, this maps to HighLevel's parent-company field. Companies without contacts receive a placeholder association pending contact migration. The migration sequence runs companies before contacts to ensure the company-contact relationship resolves correctly.

The Real Estate CRM supports linking a contact to one or more companies. HighLevel links a contact to a primary company via the Company ID field and supports additional company associations. For contacts linked to multiple companies in the source, we set the most recently modified company as the primary in HighLevel and store the full list of associated companies in a custom field for reference.

Deals from The Real Estate CRM map to HighLevel Opportunities. Each deal's stage maps to a corresponding HighLevel pipeline stage using the stage mapping configuration table. Deal value, close date, and owner transfer directly. HighLevel Opportunities attach to the migrated contact and company records via the lookups established during those migration phases. Stage-transition history is preserved as custom datetime fields if the source stores it.

Each unique pipeline in The Real Estate CRM becomes a separate HighLevel pipeline. Within each pipeline, stage names map value-by-value to HighLevel stage definitions. Stage probability percentages and forecast categories are re-applied based on historical data from The Real Estate CRM. The pipeline and stage setup must be completed in HighLevel before the deal migration phase runs so the stage mapping table can resolve correctly.

Tasks and reminders from The Real Estate CRM migrate to HighLevel tasks attached to their parent contact or company record. Task subject, due date, status (complete/incomplete), priority, and assigned user all transfer. HighLevel tasks support reminders, recurring patterns, and integration with the calendar — these capabilities are available post-migration without additional setup.

Notes and comments associated with contacts, companies, or deals migrate to HighLevel notes attached to the corresponding records. Note content, author, and create timestamp are preserved. HighLevel notes support rich text and can include mentions of other records. We preserve the original note body exactly; formatting is simplified to HighLevel's supported subset.

Email history linked to contacts transfers as HighLevel email message records with subject, body, direction (sent/received), timestamp, and sender/recipient details. Email threads attach to the contact record's activity feed. HighLevel's email tracking (opens, clicks) is a post-migration configuration setting that applies to new emails going forward; historical tracking data does not exist in the source.

Call logs attached to contacts migrate with duration, outcome (answered, voicemail, missed), timestamp, and notes. If the source stores call recordings as files, those files attach to the call record in HighLevel. Call disposition data from the source maps to a custom field in HighLevel since HighLevel's native call outcome options may differ from the source's picklist.

Meetings and appointments migrate to HighLevel appointments attached to the contact record. We preserve title, start/end datetime, location, attendees, and outcome notes. HighLevel's calendar integration syncs appointments with Google Calendar and Outlook — this integration must be configured post-migration as it is destination-side schema.

Every custom field in The Real Estate CRM requires a corresponding custom field to be created in HighLevel before migration runs. We map field types to their closest HighLevel equivalents: text to text, number to number, date to date, picklist to dropdown, and boolean to checkbox. Multi-select picklists map to multi-select custom fields. Fields with no HighLevel equivalent store as text with a reference note.

File attachments linked to contacts, companies, or deals migrate to HighLevel's file storage and attach to the corresponding record. Files download from the source, upload to HighLevel, and link to the parent record. HighLevel's file size limit is 100MB per file. We flag any files exceeding this limit before migration so you can decide whether to split them or exclude them.

Automation logic — triggers, conditions, time delays, and action sequences — cannot migrate between The Real Estate CRM and HighLevel due to fundamental differences in their automation engines. We deliver an automation audit document listing every workflow, its trigger, conditions, and actions in plain English so your team can rebuild them in HighLevel's workflow builder. HighLevel's workflow canvas supports over 40 action types including email, SMS, task creation, tag application, and pipeline stage updates.