Migrate from Property Raptor to Salesforce Sales Cloud

Direct map. Property Raptor contacts migrate to Salesforce Contacts. Salesforce requires AccountId for most contact records — Property Raptor contacts without a primary company get attached to a default 'Unassigned Accounts' record or routed to Salesforce Leads based on lifecycle role.

Direct map. Property Raptor company records map to Salesforce Accounts using direct field-to-field mapping. Company hierarchies representing parent companies and branch offices are preserved using Salesforce's Parent Account field for organizational structure. Multi-office contacts in Property Raptor are normalized to one primary AccountId plus Account Contact Relations for managing secondary office affiliations.

Property Raptor's native Property object has no Salesforce standard equivalent. We create a Property__c custom object in Salesforce with fields for address, property type, status, square footage, bedrooms, bathrooms, and listing agent. Property records link to Accounts (as the property owner or landlord entity) via lookup fields.

Each Property Raptor listing representing various statuses (active, pending, sold, withdrawn) becomes a separate Listing__c record in Salesforce. Listing__c establishes a lookup relationship to Property__c for property association and links to the responsible Contact or agent via OwnerId for accountability. Listing status values map to a configurable Salesforce pick-list on Listing__c.

Property Raptor leads map directly to Salesforce Leads preserving all standard lead fields. Lead source, status, and rating migrate as standard Lead fields for immediate use in Salesforce lead management. Property interest captured in Property Raptor becomes a custom pick-list field (Property_Interest__c) on Salesforce Lead for tracking buyer preferences.

Property Raptor deal pipeline maps to Salesforce Opportunities preserving deal information across the sales cycle. Each deal stage in Property Raptor maps to an Opportunity StageName value for consistent pipeline visualization. If Property Raptor uses multiple pipelines, each pipeline becomes a separate Salesforce Sales Process keyed by RecordTypeId for specialized handling.

Property Raptor activities including viewing appointments, call logs, and email logs migrate to Salesforce Tasks and Events respectively. Original timestamps, owners, and parent-record links are fully preserved during migration. Viewing appointments containing specific start and end times become Salesforce Events for calendar integration.

Property Raptor attachments including floor plans, legal documents, and property images are re-uploaded to Salesforce Files with full metadata preservation. File size limits apply — Salesforce default maximum is 25MB per file. Inline images embedded in property descriptions are downloaded and rehosted as Salesforce Files linked to the corresponding property record.

Property Raptor agent records resolve to Salesforce Users by performing email match against the User object for identity alignment. Unmatched agents are flagged before migration with specific error details — your team either creates Salesforce users first or assigns their records to a designated fallback user during the migration process.

Property Raptor WhatsApp Business templates and notification logic have no direct Salesforce equivalent for automated migration. We export the template names, trigger conditions, and message bodies as a detailed reference document for your Salesforce admin to rebuild using Salesforce Flow and Salesforce Email Templates post-migration.

Property Raptor's native listing portal sync with Rightmove, Zoopla, PropertyFinder, and Bayut does not automatically migrate to Salesforce. We document the current portal credentials and listing IDs as a detailed reference so your team can configure Salesforce AppExchange listing apps or custom API integrations after migration completes.

Property Raptor's AI property-matching scores and algorithm outputs are preserved as custom fields (AI_Match_Score__c, Matched_Property_IDs__c) on both Contact and Property__c objects. This maintains the complete matching history for future reference even though the live algorithm itself cannot run in Salesforce without Einstein configuration being set up.