Migrate from Rent Manager to Freshsales

Freshsales has no native property or lease object — custom module required

Rent Manager's entire data model is built around Properties, Units, and Leases. Freshsales standard objects (Account, Contact, Deal) are insufficient to represent the property hierarchy and lease terms natively. We create a custom Property__c module with a lookup to the owner Account, and lease-specific fields (start date, end date, rent amount, security deposit) become custom fields on the Deal object. This means your Salesforce admin or FlitStack consultant must design and create the Property module schema before data migration begins — a step that typically adds 2–3 days to the planning phase. Once created, the custom module supports the full Rent Manager property-owner-tenant relationship structure and enables Freshsales reports filtered by property type, unit count, or lease expiration.

Rent Manager's double-entry accounting has no Freshsales equivalent

Rent Manager tracks charges, payments, deposits, and AP invoices with full GL account detail. Freshsales has no native accounting module — the Amount field on a Deal represents only a monetary value for pipeline forecasting, not a ledger entry. Payment history, AR aging, and owner statement data cannot migrate as financial records. We preserve payment and charge history as notes attached to the corresponding Deal, recording date, amount, and type (rent, late fee, deposit refund). If your team needs to retain financial history for owner reporting or audit purposes, that data must be extracted from Rent Manager as a separate financial export and stored in a document repository linked to the Freshsales Deal or Account record.

Owner and vendor records require type tagging to avoid confusion

Rent Manager maintains separate Owner and Vendor tables. When both migrate to Freshsales Accounts, there is no built-in mechanism to distinguish an owner from a vendor within the standard Account object. We resolve this by creating two custom pick-list fields — owner_type__c on Account with values 'Property Owner' and 'Vendor' — and tagging every migrated record at migration time. If your team has both owners and vendors with the same company name, additional disambiguation rules (by tax ID, email domain, or property association) must be defined before migration to prevent duplicate Account records.

Freshsales contact lifecycle stages and tenant status need explicit value mapping

Rent Manager uses tenant_status (Active, Past, Prospect) to classify tenants. Freshsales Contact lifecycle stages (Subscriber, Lead, MQL, SQL, Customer, Evangelist) serve a similar role but use different semantics and are primarily designed for marketing-sourced contacts. We map Rent Manager Active tenants to Freshsales Customer stage and Past tenants to Lead stage, but the mapping requires your team to decide whether property management contacts should follow the same lifecycle logic as sales leads. This decision affects how Freshsales reports segment your contact base and how Freddy AI scoring applies to tenant records.

Rent Manager workflows and Wizards do not migrate and must be rebuilt in Freshsales

Rent Manager automation rules — such as automated rent reminders, late fee application, lease renewal alerts, and owner statement generation — are configured within Rent Manager's workflow engine and Wizard system. Freshsales has its own Workflows automation builder that handles task assignment, field updates, email alerts, and CRM event triggers. There is no automated migration path between the two automation systems. We export your Rent Manager workflow definitions as a structured reference document so your Freshsales admin can rebuild equivalent automation logic in Freshsales Workflows. The rebuild typically takes 4–8 hours per workflow depending on complexity.