Migrate from Leadrat CRM for Real Estate to Freshsales

Property module has no Freshsales native equivalent — requires custom object setup

Leadrat's property management module is a core built-in object with fields for type, size, price, bedrooms, bathrooms, and listing status. Freshsales has no native property entity. We migrate property records as a Freshsales custom object, which requires an Enterprise plan subscription ($59/user/mo) or a marketplace app that defines the Property object schema. If your team uses the Growth or Pro plan, property records land in Freshsales as custom fields on the Contact or Account — less structured but queryable. We clarify which plan you are on and configure the custom object accordingly before the migration plan is finalized. The custom object approach also means property-to-lead associations must be rebuilt using Freshsales's object linkage or a junction object.

Leadrat has no documented public REST API — migration relies on CSV export and direct access

Unlike HubSpot, Salesforce, or Freshsales itself, Leadrat does not publish a public REST API for third-party data access. The Leadrat API documentation site (apidocs.leadrat.com) focuses on integration guidance rather than bulk export endpoints. This means we cannot run live delta syncs via API during the migration window. We extract data using Leadrat's built-in CSV export functionality and, where available, direct database read access through an authenticated connection. The implication is that the delta-pickup window at cutover captures records modified between the export timestamp and the final cutover run — but there is a small gap compared to API-based migrations. We disclose this gap upfront and recommend scheduling the final export as close to the cutover time as possible to minimize the delta window.

Freshsales lead-to-contact conversion loses Leadrat association context

Leadrat associates leads directly with property records and deals at the lead stage. When a lead converts to a contact in Freshsales, the standard conversion process creates a contact and optionally an account and deal — but it does not automatically preserve Leadrat's lead-to-property association as a Freshsales contact-to-custom-object link. We handle this by pre-creating the property custom object records and then re-establishing the contact-to-property linkage using Freshsales's object associations or a custom junction object. The mapping plan identifies every lead with an associated property before conversion runs so no association is silently dropped.

Leadrat WhatsApp integration history does not transfer to Freshsales chat records

Leadrat's WhatsApp integration captures inbound and outbound messages linked to leads and contacts. Freshsales has a built-in chat capability via Freshchat (separate product) and supports WhatsApp Business via third-party integrations, but Leadrat's WhatsApp message history does not export in a format compatible with Freshsales chat records. We migrate the WhatsApp message text as notes on the contact record with a 'WhatsApp History' prefix, preserving the content but not the native chat UX. Your team should evaluate whether Freshchat or a WhatsApp Business integration is needed to continue the messaging channel post-migration.

Freshsales Growth plan lacks custom objects — property migration requires upgrade

If your Freshsales account is on the Growth plan ($9/user/mo), the custom object feature is not available. Leadrat property records cannot be stored as structured objects — they must be migrated as custom fields on the Contact or Account record. This limits the number of property fields that can migrate cleanly (Freshsales has a per-field limit on rich-text and multi-select fields) and prevents property-specific reporting in Freshsales without an upgrade. We verify your Freshsales plan tier before the migration plan is finalized and flag the property storage approach as a plan-dependent decision point. Upgrading to Enterprise unlocks custom objects; staying on Growth requires a flattened property schema.