Migrate from Real Properties to HighLevel

Direct map. HighLevel Contact records store name, email, phone, address, and custom fields. Owner resolution happens by email match against HighLevel users. Contacts without an email are flagged for manual review before migration commits. We also preserve the original create date and last modified date using HighLevel's dateAdded and dateUpdated fields. Custom fields map to equivalent HighLevel custom fields, and any missing required values flag the record for manual review.

Direct map. HighLevel Companies store business name, domain, address, and custom fields. Companies without a domain are migrated with a placeholder URL for reporting continuity. Multi-contact companies collapse to a primary contact with others linked via relationship fields. We also preserve the original createdAt timestamp using HighLevel's dateAdded field, and any source custom fields such as industry or employee count map to matching custom fields on the Company object.

Real Properties property listings map to a HighLevel custom object named 'Listing'. The custom object requires creation in HighLevel before migration. Property address, price, status, and MLS ID migrate as custom fields on the Listing object. Listing-to-contact relationships use custom lookup fields.

Direct map. Real Properties deals become HighLevel Opportunities inside a pipeline. The deal amount maps to Opportunity value. Deal stage (Active, Pending, Under Contract, Closed Won, Closed Lost) maps to HighLevel pipeline stages via value mapping. We preserve create date and last modified date as datetime fields on the Opportunity record. When a deal links to a property, the listing ID is stored in a lookup field on the Opportunity.

Stage names mapped value-by-value. Real Properties' stage statuses (Active, Pending, Under Contract) translate to corresponding HighLevel pipeline stage names. Stage-entered timestamps are preserved as custom datetime fields on the Opportunity for reporting continuity. If your Real Properties setup uses custom stage labels, we generate a mapping table that your admin reviews and approves before migration. Stage probability and forecast category values are stored as additional custom fields on each Opportunity.

Owner resolved by email match to HighLevel users. Unmatched owners are flagged before migration—your team either invites them to HighLevel first or assigns records to a fallback user. Agent profile fields (license number, bio) migrate as custom fields on the User record.

Lead source (website inquiry, referral, MLS, etc.) migrates as a custom pick-list field on the HighLevel Contact. The pick-list values are preserved exactly as they appear in Real Properties, with unknown values mapped to a default 'Other' option. If the source includes lead source entries per contact, we concatenate them as a string separated by commas. Lead sources are logged for your admin to add to the pick-list in HighLevel.

Property documents and client attachments are downloaded from Real Properties and re-uploaded to HighLevel as files attached to the corresponding Contact or Opportunity record. File size limits apply per HighLevel's storage configuration. Inline images in notes are extracted and rehosted.

Activity logs and notes migrate as HighLevel Notes attached to the Contact or Opportunity. Original timestamps and owner information are preserved. Call and meeting logs map to HighLevel's built-in activity tracking. We preserve createdAt and modifiedAt timestamps on Note records using HighLevel's dateAdded and dateUpdated fields. Images in notes are attached to the note. If a note references a contact or opportunity, we keep the relationship via the ID field.

Tags from Real Properties (buyer type, property interest, lead status) migrate as HighLevel Tags applied to Contact records. Tags are additive—multiple tags per contact are preserved as a tag array. HighLevel's tag system does not support hierarchy, so nested labels collapse to flat tags.

Real Properties custom fields that have no direct HighLevel equivalent (property type, bedrooms, square footage) are created as custom fields on the appropriate object (Listing or Contact). Field type is matched as closely as possible—numeric fields become number fields, text fields become text fields, and pick-lists become choice fields.

HighLevel's sub-account structure is a destination-side configuration, not migrated data. If Real Properties uses multi-office or multi-team segmentation, your team creates the corresponding sub-accounts in HighLevel post-migration, and records are distributed to the appropriate sub-account based on a mapping rule (e.g., office location field).