Migrate from Rechat to Freshsales

Rechat People records with contact_type='Contact' map to Freshsales Contact. Standard name, email, phone, address, and job title fields transfer directly. Rechat-specific custom properties (MLS numbers, property listings) create Freshsales custom fields on the Contact object. Original create_date and last_modified timestamps are preserved as Freshsales custom datetime fields since system timestamps are set at migration time.

Rechat agents map to Freshsales Users by email resolution. Agent-specific fields (designation, license_number, team) migrate to Freshsales User custom fields. Agents who also appear as contacts (e.g., broker-agents) get both a Freshsales User record and a Contact record, linked by matching email address.

Rechat Company maps directly to Freshsales Account. Company name, domain, industry, annual_revenue, and number_of_employees transfer to corresponding Freshsales Account fields. Industry values undergo value-mapping against Freshsales's industry pick-list — custom Rechat industry values land as a custom pick-list on Account. Parent-company hierarchy uses Freshsales Parent Account lookup.

Rechat Deal maps to Freshsales Deal — both objects share the same name, simplifying the mapping. Deal name, amount, close_date, owner, and custom properties transfer directly. Rechat pipeline and stage fields map to Freshsales Deal stage pick-list values using value_mapping per stage name. Stage-entered timestamps are preserved as Freshsales custom datetime fields.

Rechat pipelines have named stages (e.g., 'Active', 'Under Contract', 'Closed'). Each pipeline maps to a set of Freshsales Deal stage values. When deals span multiple pipelines, stage values are scoped by pipeline name in the mapping plan so no two pipelines share the same stage label in Freshsales.

Rechat email metadata (subject, date, teaser, sender/recipient) migrates as a Freshsales Task with Type='Email'. The full email body is not available in Rechat — the Freshsales record will contain the metadata and teaser text that Rechat stored. Activity owner resolves to Freshsales User by email match.

Rechat call logs (duration, direction, notes) migrate as Freshsales Tasks with Type='Call'. Call disposition, recording links, and timestamps preserve on the Task. If Rechat stores recording URLs, those migrate as custom URL fields on the Task for agents to access post-migration.

Rechat calendar events with start time, end time, location, and description map to Freshsales Events. Original start and end timestamps, attendee list, and organizer details are preserved on the Freshsales Event record. Events link to the parent Contact or Deal via Freshsales's association model.

Rechat notes (body text, created date, author) migrate as Freshsales Notes. Rich-text formatting in Rechat notes is converted to plain text for Freshsales Note compatibility. Notes attach to the parent Contact, Account, or Deal based on Rechat's association metadata, preserving the contextual relationship.

Rechat file attachments on people, companies, and deals re-upload to Freshsales as file attachments on the corresponding records. File size limits apply — files exceeding Freshsales's attachment size cap are flagged before migration so your team can address them. File original names and upload dates are preserved in the attachment metadata.

Rechat MLS Number custom property has no native Freshsales equivalent. We create a Freshsales custom text field (MLS_Number__c) on Contact or Account, scoped by which record type the property was attached to in Rechat. The exact field label and object assignment are confirmed during the sample migration.

Rechat property listing fields (listing status, property type, price) migrate to Freshsales custom fields on the Deal or Contact object. We create a custom field group matching Rechat's property data structure, with value_mapping for status pick-list values (Active, Pending, Sold) against Freshsales pick-list options.