Migrate from The Real Estate Platform (REP) to Freshsales

Direct map. REP buyers and sellers become Freshsales Contacts. The primary company association migrates as AccountId lookup — if the contact has no associated company, a default 'Individual' account is created in Freshsales. Email, phone, address, and custom fields migrate directly.

Direct map. REP's company object translates to Freshsales Account. Regional hierarchy representing parent and child offices maps to Freshsales Parent Account field. Multi-location brokerages use the parent account to represent the holding company, with child accounts created for each individual office location.

Direct map for REP leads not yet associated with a deal. If the REP lead has already been converted to a contact plus deal, the contact maps to Freshsales Contact and the deal maps to Freshsales Deal. Lead status values require value-by-value mapping against Freshsales' picklist.

REP Agent records map to Freshsales User objects by email match. Agent productivity data such as listings sold and close rate migrates as custom fields on the User record. If an REP agent email does not match a Freshsales user, the record is flagged before migration — either invite the user to Freshsales first or assign their records to a fallback owner.

REP Listing is a hybrid object containing both property details and deal-state information. The transaction data (price, stage, close date, agent owner) migrates as a Freshsales Deal. The property details (address, sq ft, mls_id, property_type, bedrooms, bathrooms) migrate as a Freshsales Custom Module 'Property' linked to the Deal via lookup.

REP listing stages (Active, Under Contract, Pending, Sold, Cancelled) map to Freshsales Deal Stage values per Sales Pipeline. Each REP pipeline maps to a separate Freshsales Sales Pipeline. Probability values and forecast categories are re-applied based on Freshsales stage configuration.

REP calls map to Freshsales Tasks with Type set to 'Call'. Emails map to Tasks with Type set to 'Email'. Meetings map to Freshsales Events preserving original start and end times. Notes map directly to Freshsales Notes. All activity records preserve original timestamps, owners, and parent-record links to either contact or deal.

REP agent-level custom fields such as license_number, territory_code, and team_id require Freshsales Custom Fields on the User object. Not all user custom fields appear in Freshsales reporting by default — your admin may need to build custom reports to surface agent-level metrics.

REP listing custom fields map to either Deal custom fields for transactional properties like listing_source, or Property Custom Module fields for physical properties like hoa_fees. FlitStack surfaces the complete mapping plan before migration so you can decide which module should hold each field.

REP file attachments on listings, contacts, or deals are downloaded and re-uploaded to Freshsales Files. The file is associated with the corresponding record in Freshsales. File size limits apply with Freshsales supporting attachments up to 25MB per file.

REP's region-office-agent hierarchy requires a two-part mapping: the office-level entities become Parent Account hierarchy in Freshsales (regional holding company as top-level account, with office accounts as children). Agent-to-office assignment migrates as a custom Territory field on the User record, or as Freshsales Territory Management on Pro+ plans.

REP workflows do not migrate. They must be rebuilt in Freshsales Workflows (Admin > Workflows). FlitStack exports your REP workflow definitions as a reference document so your Freshsales admin can reconstruct the logic. Marketing sequences require Freshsales Sales Sequences (Pro+).