Migrate your Property Raptor data

Contacts in Property Raptor follow the standard Salesforce Contact schema with additional real-estate attributes such as budget range and preference flags. We migrate Contact records 1:1 with all standard fields intact.

Leads are the primary acquisition object for Property Raptor, capturing prospect information before conversion. We preserve Lead records including all source tracking and custom properties.

Property records contain rich data specific to real estate listings — addresses, property types, pricing, and status. We map these to your destination's equivalent object, flagging any custom property fields that require reconfiguration.

Listings are the published representation of Properties on portals like Rightmove, Zoopla, PropertyFinder, and Bayut. We migrate listing metadata including portal associations and visibility flags, noting that portal-specific IDs do not transfer.

Opportunities represent active deals or transactions in the pipeline. We preserve stage history, amounts, expected close dates, and owner assignments using Salesforce standard fields.

Property Raptor supports custom objects and relation data, allowing complex structures such as linking one profile to many properties with individual attributes. We migrate these on a case-by-case basis after mapping the relationship schema.

Activities and tasks track client interactions and follow-ups. We migrate completed and open activities, though some activity metadata may require field-level mapping depending on the destination system.

Documents attached to Properties, Contacts, or Opportunities can be exported, but attachment handling depends on whether they are stored in Salesforce Files or as external URLs. We review the storage type during scoping.

Workflow configurations and automation rules are not directly portable across CRM platforms. We document existing workflows during discovery and provide recommendations for rebuilding them on the destination platform.

Property Raptor's data attributes and picklist values are customizable to match regional market practices. We map custom fields and flag any picklist values that may not exist in the destination schema.

User records and team member assignments on Deals and Properties migrate as User references, though login credentials and permission sets do not transfer and must be reconfigured separately.

Tagging structures for categorizing Leads, Properties, and Listings vary by implementation. We extract and map tag data as custom text fields or labels in the destination system.