Migrate from Property Raptor to Zoho CRM

Property Raptor contact records map to Zoho Leads for new enquiries and Contacts for established client relationships. We preserve the original create date, last-modified timestamp, and owner assignment by email match. Unmatched owners default to a specified Zoho user or remain unassigned for manual routing.

Property Raptor company records map to Zoho Accounts. Company hierarchies (parent/child relationships) transfer via Zoho's Parent Account lookup. Multi-contact accounts collapse to primary AccountId with additional contacts linked through Account Contact Relations in Zoho. Any branch or subsidiary designations associated with company records in Property Raptor transfer as additional text fields on the Zoho Account for reference during sales operations.

Property Raptor deals (enquiries, viewing requests, offers) map to Zoho Deals. Deal stage names from Property Raptor map to Zoho Deal Stage values via value-by-value mapping. Amount, closing date, and owner transfer directly. We create the Zoho Deal fields first during schema setup so the mapping runs cleanly.

Property Raptor's property listings have no Zoho native equivalent. We create a 'Properties' custom module with custom fields for address, property type, bedrooms, bathrooms, price, area (sq ft/m2), listing status, and portal sync status. Property photos and documents attach via Zoho Attachments linked to each Property record.

Buyer and tenant preference data from Property Raptor — budget range, location requirements, bedroom count, property type — migrates as custom fields on Zoho Lead and Contact records. This preserves the preference data that drives Zoho's workflow routing and Zia lead scoring.

Property Raptor web portal tracking data (pages viewed, properties searched, session duration) consolidates into custom fields on the Zoho Contact record. Where Property Raptor stores individual page-view events, we summarize into aggregated metrics (total views, last viewed date, preferred property type) for Zoho workflow triggers.

Property Raptor tasks (viewing confirmations, follow-up calls, document requests) map to Zoho Tasks. Meetings and site visits map to Zoho Events. Original timestamps, due dates, owners, and related-record links (contact, deal, property) all preserve during migration. Any task priority flags or viewing urgency markers from Property Raptor transfer as additional fields on Zoho Tasks to maintain the original workflow context.

Email threads from Property Raptor's Gmail and Outlook integrations migrate as Zoho Tasks with Type='Email'. WhatsApp conversation summaries transfer as Zoho Notes attached to the relevant Contact or Deal, preserving the original message timestamp and contact name. Full WhatsApp message history requires Zoho's Conversations module on supported plans.

Property Raptor file attachments (PDF contracts, property brochures, identity documents) migrate to Zoho Attachments linked to the corresponding Contact, Account, Deal, or Property record. Zoho's 25MB per-file limit applies; files exceeding this threshold are flagged before migration so your team can split or compress before the full run.

Property Raptor users and agent owners resolve to Zoho Users by email address match. We flag any Property Raptor owner with no matching Zoho user before migration so your team can either invite them to Zoho or reassign their records. This prevents records landing without an owner assignment in Zoho.

Any Property Raptor custom objects built on top of the Salesforce data model map to Zoho Custom Modules. We read the custom object schema from Property Raptor's API export, then create matching Zoho custom modules with corresponding custom fields before data migration begins.

Property Raptor's AI-matching score (how closely a lead matches available properties) transfers to a Zoho custom numeric field on Lead and Contact. This preserves historical lead quality data for reporting continuity even though Zoho's Zia scoring will run independently on the Zoho platform.