Migrate from LeadManaging to Freshsales

LeadManaging lifecycle statuses require value-mapping or custom fields — Freshsales lifecycle stages are a separate construct

LeadManaging tracks lead progress using custom status values (New Inquiry, Touring, Applied, Approved, Leased, Dead) that are not native Freshsales lifecycle stages. Freshsales has its own built-in lifecycle stage values (Subscriber, Lead, MQL, SQL, Opportunity, Customer, Evangelist) that drive CRM behavior. We map each LeadManaging status to the closest Freshsales lifecycle stage and preserve the original status in a custom text field called Original_Status__c so reporting shows the exact leasing workflow stage the record held in LeadManaging. If your team uses more than eight unique status values, we recommend storing them all as a custom pick-list rather than overloading the lifecycle-stage field.

Freshsales Pro ($39/user/mo) is required for Freddy AI and territory management — Growth ($9) has no AI scoring

Freshsales Growth at $9/user/mo includes basic CRM features but omits Freddy AI contact scoring, custom sales activities, territory management, and advanced workflows. LeadManaging lead scores migrate as a custom number field (Lead_Score_LM__c), which works alongside Freddy AI on Pro/Enterprise plans — but teams running Growth cannot use Freddy AI to re-score migrated leads. Before migration, confirm which Freshsales plan your team will run so we scope the custom field plan correctly. If you are moving to Freshsales primarily for AI scoring, the Pro plan is the minimum viable tier for that use case.

Property and unit associations have no Freshsales native equivalent — they become custom fields

LeadManaging is a property-centric tool: every lead is organized by which property they inquired about and which unit they toured. Freshsales has no native property or unit object. We store property name as a custom text field (Property_Name__c) on the linked Account and unit number as Unit_Number__c on the Lead. This preserves the leasing context but requires your team to agree on field naming and placement before migration. If your team manages multiple properties, we recommend one Account per property and a view or report that groups Leads by that custom field.

LeadManaging deal records map to Freshsales Deals — but pipeline and stage configuration must exist first

If LeadManaging tracks lease amounts or deal values, these migrate as Freshsales Deals. However, Freshsales requires a Deal pipeline and stage values to exist before Deals can be created. We create a 'Leasing Pipeline' in Freshsales with stage names that match your LeadManaging lifecycle values before the migration runs. If your team uses multiple Freshsales pipelines for different business units, the deal migration plan needs to route LeadManaging records to the correct pipeline and record type before data lands.

Custom fields in LeadManaging that use leasing-specific formats need Freshsales schema review before mapping

LeadManaging custom fields (referral_source_detail, leasing_agent_assigned, etc.) may use pick-list values, numeric formats, or date conventions specific to the leasing workflow. Freshsales enforces field type constraints — a pick-list in LeadManaging cannot migrate to a text field in Freshsales without a schema change. We audit custom field types during discovery, create the matching Freshsales custom fields first, and then run value-by-value mapping for pick-lists. Multi-select pick-lists in LeadManaging require Freshsales multi-select custom fields which have a 255-value limit per field.