Migrate from Property Raptor to HubSpot

Property Raptor contacts map directly to HubSpot Contacts. The mapping preserves original create and update timestamps in a custom field since HubSpot overwrites CreatedDate at import time. Owner resolution matches the Salesforce user email to a HubSpot user — unmatched owners are flagged before migration commits.

Property Raptor accounts map to HubSpot Companies. Parent-child company hierarchies in Property Raptor (Salesforce Parent Account) are preserved in HubSpot using the Parent Company field. Multi-office agencies with one account per branch map to separate HubSpot company records. Each company record retains its original Salesforce create date for historical reference and audit compliance.

Property Raptor opportunities map to HubSpot Deals 1:1. Each deal carries its amount, close date, owner, and pipeline reference. The pipeline-to-HubSpot-deal-pipeline mapping is configured during scoping so the correct HubSpot pipeline receives each deal. Historical stage-entry timestamps are preserved for accurate deal velocity reporting in HubSpot.

Property Raptor's property and listing objects have no HubSpot native equivalent. We create a HubSpot Custom Object named 'Property Listing' (Enterprise only) and map listing name, price, status, property type, and address fields. If the HubSpot account is on Starter or Professional, these records are stored as custom properties on the Company or Deal object instead.

Property Raptor stores many-to-many relationships between listings and contacts (e.g., buyer linked to three properties). HubSpot has no native N:N association model for Custom Objects. We create a junction Custom Object with Listing ID and Contact ID fields and an association label (e.g., 'Interested Buyer', 'Viewing Attended').

Property Raptor real estate stages (e.g., 'Viewing Booked', 'Offer Made', 'Under Contract', 'Closing') map value-by-value to HubSpot deal stages. We create or select HubSpot stages that match the real estate lifecycle, preserving stage-entry timestamps in a custom datetime field on the Deal for reporting continuity.

Property Raptor leads that have converted in Salesforce map to existing contacts. Unconverted Property Raptor leads with no associated deal route to HubSpot Contacts. If the agency uses a separate pre-contact pipeline in Property Raptor, those records become HubSpot Contacts with a custom 'Lead Source' property rather than a separate object.

HubSpot has a unified activity timeline on each contact and company record. Property Raptor calls, emails, and meetings map to the corresponding HubSpot engagement type, preserving original timestamps, owner assignments, and task subject lines. Notes with attachments are transferred alongside their associated files for complete activity history continuity.

Property Raptor stores attachments as Salesforce Files (ContentDocuments). We download each file and re-upload to HubSpot Files, re-attaching them to the corresponding contact, company, or deal record. File size limits (HubSpot default 25MB per file) are checked and large files flagged before migration.

Property Raptor owner IDs are Salesforce User records. We resolve each Salesforce User's email address against HubSpot users. Matched users receive their records as owner. Unmatched owners (e.g., inactive Salesforce users) are flagged for manual assignment before the migration window opens.

Property Raptor's listing portal sync records (Rightmove, Zoopla, PropertyFinder, Bayut) have no HubSpot equivalent. We preserve the last-synced portal URL as a custom property on the Property Listing custom object. Teams must rebuild portal connectors using HubSpot's integration ecosystem or a middleware tool.

Property Raptor custom fields beyond the standard Salesforce schema (e.g., 'Preferred Location', 'Budget Range', 'Property Type Preference') are mapped to HubSpot custom properties. Pick-list fields use value mapping; numeric and date fields map directly. Text fields over 500 characters are truncated with a flag for admin review.