Migrate from Property Raptor to HighLevel

Property Raptor's Contact object maps directly to HighLevel's Contact object. Email, phone, address, and owner fields transfer as-is. HighLevel requires contacts to be assigned a primary Company; contacts without a company association are linked to a placeholder Organization record or flagged for manual assignment.

Property Raptor's Account object (representing real estate agencies, brokerages, or property developers) maps to HighLevel's Company object. Company name, domain, industry, employee count, and annual revenue transfer directly. Multi-office hierarchies in Property Raptor are preserved as parent-child Company relationships in HighLevel.

Property Raptor's Opportunity object representing property transactions or listings maps to HighLevel's Opportunity. Deal name, amount, stage, close date, and owner transfer directly. Pipeline stage values map to HighLevel's pipeline stage pick-list on a per-pipeline basis, preserving stage probability and forecast categories. Owner assignment resolves via email match before migration.

Property Raptor's listing object has no direct equivalent in HighLevel. We create a Property custom object in HighLevel and map listing-specific fields: property address, listing status, property type, price, square footage, bedrooms, bathrooms, and listing source portal. Portal source (PropertyFinder, Rightmove, Zoopla) is preserved as a tag for segmentation.

Property Raptor links contacts to properties through a junction object (e.g., Buyer, Viewer, Owner roles). HighLevel has no native many-to-many contact-property relationship. We create a custom field on the Property object that stores the primary contact ID, with secondary associations stored as tags or notes for reference.

Property Raptor's activities (calls, meetings, property viewings, showing appointments) map to HighLevel's Task object. Subject, due date, completion status, owner, and original timestamp transfer directly. Original timestamp becomes dateAdded, while due date uses ActivityDate. Property-specific activities receive a tag containing the related Property custom object ID for immediate context.

Property Raptor notes and file attachments transfer to HighLevel's Notes and Files. Rich-text formatting in notes is preserved. Attached files are re-uploaded to HighLevel's file storage. HighLevel's file size limits (25MB per file) apply; files exceeding this threshold are flagged for chunking or alternative delivery.

Property Raptor owner records are resolved by email match against HighLevel users. Unmatched owners are flagged before migration; your team either creates HighLevel user accounts for them or assigns their records to a fallback owner. Salesforce profile-based permissions in Property Raptor do not transfer — HighLevel role-based access control must be configured post-migration.

Property Raptor custom fields on listings (e.g., property condition, year built, parking spaces, amenities) migrate to custom fields on HighLevel's Property custom object. Field type is preserved where possible: text fields stay text, pick-lists become dropdowns, number fields remain numeric. HighLevel's custom field naming conventions are applied.

Property Raptor's workflows built on Salesforce Flow or Process Builder do not migrate. We export workflow definitions as documentation so your HighLevel admin can reference them when rebuilding in the Workflow Builder. Portal sync rules, lead assignment automations, and AI matching triggers require complete rebuild in HighLevel.

Property Raptor's native portal integrations with PropertyFinder, Bayut, Rightmove, and Zoopla have no direct equivalent in HighLevel. We document the current sync configuration (listing fields, update frequency, attribution rules) so your team can rebuild the integrations via HighLevel's API, Zapier, or a custom middleware solution.