Migrate from The Real Estate Platform (REP) to HighLevel

REP agents map directly to HighLevel contacts. Agent profile fields (name, email, phone, license number, bio) become contact fields. Agent activity history, including listing associations and transaction history, migrates as activity records attached to the contact. REP's multi-office context becomes the HighLevel sub-account scope for the migration.

REP's native listing entity has no HighLevel equivalent — HighLevel has no built-in property object. We create a Property custom object in the target HighLevel sub-account before migration, with fields for address, price, property type, bedrooms, bathrooms, square footage, MLS number, status, and listing agent. All REP listing fields map into Property custom fields.

REP listings can associate with multiple agents — listing agent, co-listing agent, and buyer's agent. HighLevel's contact-object model does not natively support N:N listing associations. We create a ListingAgent junction custom object linking Property and Contact records, preserving every agent role from REP.

REP transactions map to HighLevel opportunities. Transaction value maps to opportunity amount; stage (active, under contract, closed, cancelled) maps to HighLevel pipeline stage values. Commission split percentages and agent payout status migrate as opportunity-level custom fields because HighLevel does not have a native commission structure object.

REP's region-office hierarchy becomes HighLevel sub-accounts. Each REP office or region maps to a dedicated HighLevel sub-account so agent and listing data remain scoped to the correct business unit. If a single sub-account is preferred, region and office are stored as contact custom fields for reporting.

Brokerage and partner company records in REP map directly to HighLevel companies using standard field alignment for name, website, address, and industry classification. Company-agent associations migrate as HighLevel company-contact relationships, preserving the organizational structure between brokerages and their associated agents in the target system.

Unconverted leads and prospect records in REP migrate as HighLevel contacts. Source attribution data from the REP lead source field maps to a HighLevel contact custom field since HighLevel does not have a native lead-status concept separate from contact records, requiring custom field handling for lead provenance tracking.

REP call logs, emails, meeting records, and notes attach to agents and listings. These map to HighLevel tasks and notes with original timestamps and owner preserved. Meeting records become HighLevel calendar events containing start/end times, subject, location details, and the associated contact for complete activity history transfer.

REP's automated buyer follow-up, drip campaigns, and lead nurturing sequences do not migrate. Each automation must be rebuilt in HighLevel's Workflow builder using the exported REP automation definitions as a rebuild reference. The migration carries the data; the logic is recreated manually.

Listing photos, property documents, and agent profile files attached to REP records are downloaded during the extraction phase and re-uploaded to HighLevel Files, associated with the corresponding Property custom object or contact record to preserve all media attachments from the source system.