Migrate from Leadrat CRM for Real Estate to Salesforce Sales Cloud

Leadrat stores all people as contacts regardless of qualification stage. FlitStack AI inspects each Leadrat contact's deal association and last-activity date to route records: contacts with no associated deal or no follow-up task land as Salesforce Leads; contacts with a completed site visit, booking, or registration milestone land as Salesforce Contacts. The routing rule is configurable per your sales process before the migration runs.

Leadrat companies map directly to Salesforce Accounts. Leadrat's parent-company hierarchy (if configured) maps to Account.ParentId so agency networks with parent firms and branch offices preserve their hierarchy in Salesforce. Multi-contact accounts in Leadrat each get a primary AccountId assignment with Account Contact Relationships for secondary associations.

Each Leadrat deal becomes a Salesforce Opportunity. Leadrat's pipeline field maps to Salesforce RecordTypeId (one record type per Leadrat pipeline), and dealstage maps to Opportunity StageName using a per-record-type value map. Stage probability weights and forecast categories are re-applied based on Salesforce's stage-history model. Original stage-entry timestamps are preserved as custom datetime fields on the Opportunity.

Leadrat's built-in property listing feature has no Salesforce native equivalent. FlitStack AI creates a Property__c custom object before migration, defining fields for property name, type, price, address components, area, bedroom/bathroom counts, status, owner lookup, and a Portal_Assignments__c text field. Leadrat's property-to-deal association becomes a lookup from Opportunity to Property__c.

Leadrat tasks and meeting notes migrate as Salesforce Tasks with original due dates, subjects, and owners preserved. The Leadrat follow-up type (call, site visit, meeting, email) is stored as a custom Activity_Type__c field on the Task so you can filter by the original activity category. Completed site-visit tasks link to the associated Property__c record when a property lookup exists in Leadrat.

Leadrat captures lead source (website, referral, portal inquiry, walk-in). Salesforce's standard LeadSource pick-list is extended to match the full Leadrat value set before migration. Any Leadrat source value not added to the Salesforce pick-list is flagged for the admin to assign post-migration, preventing blank LeadSource values on import.

Leadrat workflows for follow-up sequences, lead auto-assignment, and reminder scheduling do not have a public export format. FlitStack AI cannot transfer them automatically. We provide a Workflow Documentation Export that enumerates each rule's trigger, conditions, and actions from the CSV data so your Salesforce admin can rebuild them in Flow. Portal-sync settings for Bayut, Property Finder, and Dubizzle also require manual reconfiguration.

Leadrat stores task due dates and follow-up alert preferences. Salesforce Tasks use a built-in IsReminderSet flag and ReminderDateTime field. Leadrat's custom reminder timing (e.g., 'alert 2 hours before') maps to a Reminder_Settings__c text field on the Task so your admin can replicate the original schedule logic when rebuilding automations in Salesforce Flow.

Leadrat owner IDs are resolved to Salesforce User records by email match before migration. Unmatched owners are flagged in the pre-migration report so your team can either invite them to Salesforce first or assign their records to a designated fallback owner. No record lands in Salesforce without a valid OwnerId.

Leadrat's native portal connectors for Bayut, Property Finder, Dubizzle, Magic Bricks, 99Acres, and Housing.com do not have a Salesforce equivalent and cannot be migrated. FlitStack AI documents which portals are connected in Leadrat so your team knows what to rebuild in Salesforce or via a third-party integration tool after go-live.