Migrate from Property Shell to HighLevel

Property Shell contacts map 1:1 to HighLevel Contacts. Name, email, phone, and address fields align directly. Owner resolution uses email matching against HighLevel user accounts — unmatched owners flagged before migration commits.

Property Shell company records map to HighLevel Businesses (the Companies object). Developer name, website, industry, and employee-count fields map to their HighLevel equivalents. Multi-company contacts collapse to one primary Business with additional relationships surfaced as tags.

Property Shell deals map to HighLevel Opportunities. Each deal pipeline in Property Shell becomes a HighLevel Pipeline. The deal stage maps to an Opportunity Stage value within that pipeline. The migration plan enumerates each Property Shell pipeline and assigns it to a corresponding HighLevel Pipeline before data lands.

Stage names in Property Shell (e.g., Enquiry, Contract Sent, Exchange, Settlement) map value-by-value to HighLevel Opportunity Stage names. We preserve the stage-entry timestamp as a custom datetime field (Stage_Entered_Date__c) on each Opportunity for reporting continuity.

Property Shell Listings have no direct HighLevel equivalent — we create a Property_Listing__c custom object with fields for address, lot_number, stock_status, development_name, and price. A lookup relationship links each listing to the Opportunity representing the deal on that property.

Property Shell settlement tracking (inance, exchange, completion, handover) migrates as a custom pick-list field on the Opportunity. The exact settlement-stage values are preserved and mapped to the custom field so reports filter correctly in HighLevel.

Property Shell commission-payment records map to a Commission_Payment__c custom object related to the Opportunity, storing payment_amount, payment_status, and agent_name. Complex multi-tier commission structures may require additional custom fields for splitting.

Property Shell call logs, meeting notes, and general activities map to HighLevel Tasks with original timestamps and owners preserved. High-level notes map to HighLevel Notes. Activity type (call, meeting, email) is stored in the Task Type field.

Property Shell owner IDs are resolved by email match to HighLevel user accounts. If an owner has no HighLevel account, the record is assigned to a migration fallback owner and flagged for the admin to resolve before go-live.

Property Shell's interactive map URLs (displaying lot status on project websites) have no HighLevel native equivalent. We preserve the map URL in a custom text field (Interactive_Map_URL__c) on the Property_Listing__c custom object as a reference link.

Property Shell's lot-allocation and stock-status tracking (available, under-contract, sold, settled) maps to Lot_Number__c and Stock_Status__c custom fields on the Opportunity, with the related Property_Listing__c record holding the authoritative inventory state.

Property Shell automations — lead nurture sequences, settlement-triggered notifications, commission alerts — do not transfer. We export the automation definitions as a structured JSON document so your HighLevel admin can replicate the logic in the Workflow Builder.