CRM migration
Field-level mapping, validation, and rollback between LeadSimple and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
LeadSimple
Source
Freshsales
Destination
Compatibility
11 of 12
objects map 1:1 between LeadSimple and Freshsales.
Complexity
CModerate
Timeline
48–72 hours
Overview
LeadSimple organizes property management around Properties, Units, and Processes — a structure designed for landlords and PM firms. Freshsales uses a standard CRM object model: Leads, Contacts, Accounts, and Deals. The migration requires translating LeadSimple's property-centric data into Freshsales's account-centric model, which is the central challenge of every LeadSimple-to-Freshsales migration we run. We extract LeadSimple data via their bulk CSV export, mapping Properties to Freshsales Accounts, Leads (per property workflow) to Freshsales Leads or Contacts depending on lifecycle status, and Unit-level details to custom fields on the Account or as linked records. Pipeline stages from LeadSimple become Freshsales Deal stages within one or more Freshsales pipelines. Custom fields built on properties and units transfer to Freshsales as custom fields on the Account object. The limitation that requires explicit planning: LeadSimple's notes and activity history (calls, emails, texts) do not appear in the standard CSV export — we surface this gap in the migration plan and handle it via API-based activity extraction where available. Workflows and Process automation logic are not migratable data; we export the workflow definitions as JSON for your team to rebuild in Freshsales's automation builder.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a LeadSimple object lands in Freshsales, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
LeadSimple
Property
Freshsales
Account
1:1LeadSimple Properties map directly to Freshsales Accounts. The property name becomes the Account Name, property address maps to the billing address fields on the Account, and property type (single-family, multi-family, commercial) is stored as a custom pick-list field on the Account. Parent property relationships map to the Parent Account field in Freshsales if the hierarchy exists in LeadSimple.
LeadSimple
Contact (Person on a Property)
Freshsales
Contact
1:1LeadSimple contacts who are active tenants, owners, or decision-makers on a property become Freshsales Contacts. The contact's primary property in LeadSimple populates the Contact's AccountId lookup in Freshsales. If a LeadSimple contact has multiple associated properties, we link the primary property as AccountId and surface additional properties as a custom field for reference.
LeadSimple
Contact (Lead Status)
Freshsales
Lead
1:manyLeadSimple contacts flagged as early-stage prospects or inquiry-level records split into Freshsales Leads. We use a configurable routing rule based on LeadSimple's contact tag list or process status — records without a closed-won deal become Leads; records attached to a completed lease or sale process become Contacts. Your team sets the threshold before migration runs.
LeadSimple
Unit
Freshsales
Account Custom Field / Product
1:1LeadSimple Units are linked to a parent Property and hold unit-level data (rent amount, occupancy status, lease dates). We map units to a custom field on the Account (storing unit count and type as JSON) for quick reference, or to Freshsales Products if you want each unit tracked as a sellable/rentable item in Freshsales's product catalog linked to deals.
LeadSimple
Lead (Pipeline Stage)
Freshsales
Deal
1:1LeadSimple leads with active pipeline stages map to Freshsales Deals. The pipeline name in LeadSimple becomes the Freshsales Deal's Pipeline. The Stage Name maps to the corresponding stage in that pipeline. Deal amount (Annual Contract Value in LeadSimple) maps directly to the Freshsales Deal Amount field. We preserve the original Created At and Closed At timestamps as custom datetime fields since Freshsales CreatedDate reflects migration time.
LeadSimple
Process
Freshsales
Custom Object / Workflow
1:1LeadSimple Processes are workflow templates that drive stage progression for leasing, renewal, or maintenance. Freshsales has no direct equivalent object — Processes must be rebuilt as Freshsales Workflows or as custom objects. We export the Process definitions as JSON and deliver a rebuild reference document. Process history (which stage a property was in at a given date) is preserved as custom datetime fields on the linked Account or Deal.
LeadSimple
Owner / Assigned To
Freshsales
User / OwnerId
1:1LeadSimple owner assignments (Assigned To on leads, properties, contacts) resolve by email match to Freshsales users. If a LeadSimple owner email has no corresponding Freshsales user, the record lands under a fallback owner your admin designates. We surface the unmatched owner list before migration commits so your team can provision Freshsales users or set assignment rules proactively.
LeadSimple
Custom Field (Property-level)
Freshsales
Account Custom Field
1:1LeadSimple custom fields on Properties (e.g., property condition rating, inspection date, renewal date) create as Freshsales custom fields on the Account object. Field type parity is maintained — date fields stay date, pick-list stays pick-list, number stays number. If the same field name exists on multiple property types, we create one Account-level field and surface the variance in the mapping plan.
LeadSimple
Custom Field (Unit-level)
Freshsales
Account Custom Field / Product Field
1:1Unit-specific custom fields (e.g., unit number, square footage, rent amount) either become fields on the parent Account or, if unit-level detail needs to be individually tracked, we create Freshsales Products linked to the Account and map unit fields to Product custom fields. Your team chooses the structure before migration runs.
LeadSimple
Tag List
Freshsales
Tag
1:1LeadSimple tag lists on leads and contacts transfer as Freshsales Tags on the corresponding record. Tags are a flat list in both systems, so the mapping is direct. We normalize tag casing and remove duplicates that arise from multi-property tagging on a single contact.
LeadSimple
Annual Contract Value
Freshsales
Deal Amount
1:1LeadSimple's Annual Contract Value (ACV) on leads maps to the Freshsales Deal Amount field. This is the primary revenue figure for pipeline reporting. If a lead has no ACV (e.g., a prospect without a quote), we leave Amount blank and flag the record for your team to populate post-migration.
LeadSimple
Tracked Phone Number
Freshsales
Contact Phone / Lead Phone
1:1LeadSimple's Tracked Phone Number, which records inbound and outbound calls for a contact, maps directly to the standard Phone field on the Freshsales Contact or Lead record. This ensures that call logs, recordings, and related activity are attached to the correct record when Freshcaller is enabled. Any additional phone numbers (e.g., mobile or work) remain in separate custom fields, preserving full contact detail while keeping the primary call‑logging number consistent.
| LeadSimple | Freshsales | Compatibility | |
|---|---|---|---|
| Property | Account1:1 | Fully supported | |
| Contact (Person on a Property) | Contact1:1 | Fully supported | |
| Contact (Lead Status) | Lead1:many | Fully supported | |
| Unit | Account Custom Field / Product1:1 | Fully supported | |
| Lead (Pipeline Stage) | Deal1:1 | Fully supported | |
| Process | Custom Object / Workflow1:1 | Fully supported | |
| Owner / Assigned To | User / OwnerId1:1 | Fully supported | |
| Custom Field (Property-level) | Account Custom Field1:1 | Fully supported | |
| Custom Field (Unit-level) | Account Custom Field / Product Field1:1 | Fully supported | |
| Tag List | Tag1:1 | Fully supported | |
| Annual Contract Value | Deal Amount1:1 | Fully supported | |
| Tracked Phone Number | Contact Phone / Lead Phone1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
LeadSimple gotchas
Notes and Activities excluded from bulk CSV export
No public API — migration requires workaround
Contact-level custom fields can vary per owner on the same property
Per-door pricing on Operations layer is a billing artifact not migratable
Workflow automation must be manually rebuilt on the destination
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
Extract LeadSimple data via bulk CSV export
We trigger LeadSimple's bulk CSV export for Leads, Contacts, Properties, and Units from the admin settings panel. The export produces separate spreadsheets for each object. We validate field counts and record volumes against what your LeadSimple instance reports. If any object exceeds 25,000 records, we request off-peak import scheduling with Freshsales. We also audit the export for missing fields — particularly checking whether notes and activity history appear (they typically do not), and flag this for API-based extraction or acknowledgment.
Audit custom fields and build field mapping plan
We pull the full list of custom fields from LeadSimple across Properties, Units, and Contacts. Each field is typed (text, number, pick-list, date, currency) and assigned to its target object in Freshsales (Account, Contact, Deal, or Product). We surface the per-owner contact field limitation and ask your team to confirm the precedence rule before mapping commits. The field mapping plan goes to your Freshsales admin to create the corresponding custom fields in the target account before we run validation.
Resolve owners and provision Freshsales users
LeadSimple owner emails are matched against Freshsales user emails. We produce a matched list (owner exists in Freshsales) and an unmatched list (no Freshsales user found). Your team provisions Freshsales users for matched-but-uninvited owners, or designates a fallback owner for records with no match. No data migrates to a record without a resolved owner — this prevents orphaned records in Freshsales and ensures the Activity log has an owner attribution from day one.
Run sample migration with field-level diff
A representative slice — typically 100–500 records across leads, contacts, properties, units, and deals — migrates first. We generate a field-level diff between the LeadSimple source values and the Freshsales destination values for every mapped field. You verify lifecycle stage routing, pipeline-to-Deal mapping, owner resolution, and custom field population. Sample results are shared within 4–8 hours of receiving valid credentials. The sample run must be approved before the full migration begins.
Execute full migration with delta-pickup window
The full dataset migrates in dependency order: Properties → Accounts, then Contacts and Leads, then Deals with pipeline and stage mapping. A delta-pickup window of 24–48 hours runs concurrently, capturing any records modified in LeadSimple during the migration window. All operations are logged in an audit trail. If reconciliation fails — record count mismatch, duplicate detection, or field validation error — one-click rollback reverts the Freshsales instance to its pre-migration state. We do not overwrite existing Freshsales records without your explicit instruction; records are created fresh unless de-duplication rules specify otherwise.
Platform deep dives
LeadSimple
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 1 of 8 objects need a manual workaround.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across LeadSimple and Freshsales.
Object compatibility
1 of 8 objects need a manual workaround.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
LeadSimple: Not publicly documented.
Data volume sensitivity
LeadSimple doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during LeadSimple to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your LeadSimple to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave LeadSimple
Other ways to arrive at Freshsales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.