Migrate from Property Raptor to Freshsales

Direct 1:1 map. Property Raptor contact records transfer to Freshsales Contacts preserving name, email, phone, job title, and address fields. Owner assignment resolves via email match to Freshsales users — unmatched owners flagged for manual assignment before the full migration run commits.

Property Raptor lead records migrate to Freshsales Leads. Status values (New, Contacted, Qualified, Converted) map to Freshsales Lead Status pick-list. If Property Raptor tracks lead scoring, the score migrates as a custom number field on the Lead record since Freshsales scoring is computed by Freddy AI.

Property Raptor company records map to Freshsales Accounts. Company name, domain/website, industry, employee count, and annual revenue transfer directly. Parent-child company hierarchies in Property Raptor map to Freshsales Account hierarchy using the Parent Account field — circular references flagged during validation.

Freshsales has no native real estate property object. We migrate Property Raptor property records as a Freshsales Custom Object named 'Property' with fields for address, property type, listing status, price, and square footage. Property associations to contacts transfer as Freshsales Account Contact Relationships or as a custom junction object — your admin chooses the model before migration runs.

Property Raptor deal records map directly to Freshsales Deals. Deal name, amount, close date, stage, and owner transfer with stage values mapped per pipeline. Multi-pipeline setups in Property Raptor map to Freshsales multiple sales pipelines — each pipeline's stage values map individually to the corresponding Freshsales pipeline stage.

Property Raptor deal pipelines transfer as Freshsales Sales Pipelines. Pipeline names, stage order, and stage probabilities preserve for reporting continuity. Stage-to-pipeline assignment is 1:1 — if Property Raptor uses a single pipeline, Freshsales creates one pipeline; multiple pipelines create multiple Freshsales pipelines.

Property Raptor tasks and to-dos migrate as Freshsales Tasks. Subject, description, due date, status, and owner transfer with original timestamps preserved. Completed status maps to Freshsales 'Completed' task status. Tasks linked to specific contacts, accounts, or deals retain their parent record associations in Freshsales.

Property Raptor notes migrate as Freshsales Notes. Rich text formatting is preserved where the source format is compatible. Notes attached to contacts, accounts, or deals carry their parent record links. If Property Raptor notes include file attachments, those re-upload to Freshsales Files and attach to the corresponding record.

Property Raptor user records resolve by email match against Freshsales users. Active users with matching emails map directly; unmatched users are flagged as 'orphan owners' with their Property Raptor records assigned to a designated fallback Freshsales user for manual re-assignment before go-live.

Property Raptor's customizable data attributes per regional market practice migrate as Freshsales custom fields. Field types (text, number, date, pick-list, checkbox) are preserved during mapping. Multi-select pick-list values in Property Raptor map to Freshsales multi-select custom fields. We create the custom field in Freshsales first, then populate during migration.

Property Raptor file attachments on contacts, properties, or deals re-upload to Freshsales Files. File name, content type, and storage location are preserved. Files larger than Freshsales per-file limits are flagged for split handling. Inline images embedded in notes are extracted, downloaded, and re-hosted as Freshsales file attachments.

Property Raptor portal sync data (PropertyFinder, Bayut, Rightmove, Zoopla listing IDs and sync status) has no Freshsales equivalent. We preserve the portal metadata as structured text in a custom field on the Property custom object and as a migration reference note so your team can re-establish portal integrations manually in Freshsales.