Migrate from CRM for real estate to Freshsales

CRM for Real Estate typically stores all people as 'contacts' or 'clients' without a lead/contact distinction. FlitStack splits records during migration: unqualified prospects with no associated transaction go to Freshsales Lead; active clients with completed or in-progress transactions go to Freshsales Contact. The split is based on transaction history in the source CRM — records with a linked deal or listing in 'active' stage route to Contact.

Source CRM brokerage and company records map directly to Freshsales Account. Parent-child brokerage hierarchies (brokerage office -> branch office) map to Freshsales Parent Account lookup. Multi-location brokerages with multiple branch records require Account hierarchy setup before migration so ParentId resolves correctly on child accounts.

Property listings have no native equivalent in Freshsales. Migration creates a custom module named 'Property_Listing' with fields matching source attributes: address, city, state, zip, price, square_footage, beds, baths, listing_status, MLS_ID, and listing_agent (lookup to Contact). The custom module must be created in Freshsales Settings before migration writes data. Association to Contact records uses Freshsales' built-in module association model or a junction custom field.

Real estate transactions map to Freshsales Opportunity. Source fields — transaction amount, stage (Lead -> Showing -> Offer -> Contract -> Closing -> Closed Won/Lost), expected close date, assigned agent — map to Freshsales Opportunity fields. Transaction stage names map value-by-value to Freshsales deal stages, which must be pre-created in Freshsales Settings under the applicable pipeline.

Source CRM deal pipelines map to Freshsales Sales Pipelines. Freshsales supports multiple pipelines — each pipeline has its own set of stages scoped to that pipeline. If the source CRM has separate pipelines for buying vs. selling transactions, two Freshsales pipelines are created. Pipeline setup happens in Freshsales Settings before migration data is written to ensure stage pick-lists resolve.

Showing records and appointment records in the source CRM map to Freshsales Tasks (for to-do items like 'confirm showing') and Freshsales Events (for scheduled appointments with start/end times and attendees). Original showing date/time, property linked, attending contacts, and showing notes are preserved as task/event fields. If the source stores showing outcomes (attended, no-show, feedback), this data maps to a custom field on the associated Task.

Email logs, call records, and SMS history linked to contacts or transactions in the source CRM migrate as Freshsales Sales Activities. Each activity is associated to the relevant Contact or Account record. Timestamps, subject, body, and direction (sent/received) are preserved. Freshsales Growth plan includes built-in email and phone tools; activity data migrates as historical reference.

Lead source attribution (portal, website, referral, open house,Sphere) migrates as a custom pick-list field on both Freshsales Lead and Contact objects. Value mapping ensures source names match Freshsales pick-list values — if Freshsales does not have the source value pre-created, it is added before migration runs.

Commission splits and agent payout records in the source CRM have no native Freshsales equivalent. Migration creates a custom decimal or currency field (e.g., Commission_Split__c) on the Opportunity object and writes the source split value. Commission calculation rules (percentage-based, tiered, flat fee) must be rebuilt as Freshsales workflow formulas post-migration.

Documents attached to listings, transactions, or contacts (PDFs, contracts, disclosures, photos) are downloaded from the source CRM and re-uploaded to Freshsales Files, associated to the relevant record. Freshsales file storage limits vary by plan — Growth includes limited storage; Enterprise offers 100GB/user. File size limits and supported formats follow Freshsales import specifications.

Source CRM users and agents resolve by email match against Freshsales User records. Unmatched agents are flagged before migration — the team either creates Freshsales user accounts first or assigns records to a fallback user. Owner fields on migrated records (Contact, Account, Opportunity) use the resolved Freshsales User ID.

Automated rules, lead routing logic, auto-responders, and drip sequences built in the source CRM do not migrate. FlitStack exports workflow definitions as a reference document for rebuilding in Freshsales. Freshsales workflows (available on Growth plan, with advanced features on Pro/Enterprise) must be manually reconstructed by the admin post-migration.