Migrate from Rechat to Salesforce Sales Cloud

Rechat People map directly to Salesforce Contacts. Name, email, phone, address, and job title fields align in purpose and structure. Rechat agent-specific fields (license_number, agent_type) migrate as custom fields on Contact (License_Number__c, Agent_Type__c). The primary company association links via AccountId lookup. Multiple brokerage associations beyond the primary are handled through AccountContactRelation junction records.

Rechat contacts marked as 'Prospect' or those without a closed deal route to Salesforce Lead rather than Contact. Lead Status pick-list values map to Salesforce's standard Lead Status field. When a Lead converts to a Contact after entering a deal, the existing Lead record is archived and a new Contact is created with the appropriate AccountId and Opportunity linkage.

Rechat Companies map directly to Salesforce Accounts. Company name, domain/website, industry, and employee count fields translate to their Salesforce counterparts. Parent-company hierarchies use Salesforce's ParentId field for multi-level organizational structures. Multi-brokerage agent affiliations are handled via AccountContactRelation junction records, preserving the many-to-many relationship in Salesforce.

Rechat Deals map to Salesforce Opportunities. Real estate transaction stages (Active, Under Contract, Closed Won/Lost) require mapping to Salesforce StageName pick-list values configured per RecordType. Each Rechat deal pipeline becomes one Salesforce Sales Process, with stage names and probabilities re-created for each pipeline. Stage-entered timestamps preserve as custom datetime fields for reporting continuity.

Rechat pipelines (Buy side, Sell side, Rental) map to Salesforce Record Types with custom Sales Processes. Stage names and probability percentages are re-created per Record Type to match Rechat's workflow. Stage-entered timestamps migrate as custom datetime fields (Stage_Entered_Date__c) so historical stage durations can be reported on in Salesforce dashboards.

Rechat's listing associations have no direct Salesforce equivalent, so FlitStack creates a Listing__c custom object. Fields include MLS_ID__c, Address__c, List_Price__c, Status__c, and Property_Type__c. The Opportunity-Listing relationship uses a junction object (Opportunity_Listing__c) for many-to-many linking, allowing one deal to associate with multiple listings and vice versa.

Rechat email metadata (subject, date, direction) migrates as Salesforce Tasks with Type='Email'. Rechat does not store email body content—only teaser and metadata—so Salesforce Tasks capture what is available. Email body requires re-sync from Gmail or Outlook integration post-migration to restore full conversation history.

Rechat calendar events map to Salesforce Events with original start/end times, subject, and attendee list preserved. Owner is resolved by email match to Salesforce Users. Two-way Google/Outlook sync must be reconfigured in Salesforce setup post-migration, as the OAuth connections are platform-specific and do not transfer between systems.

Rechat file attachments (PDFs, images, documents) are downloaded and re-uploaded as Salesforce Files (ContentVersion + ContentDocumentLink). Files are associated to the parent record—Contact, Account, or Opportunity—via ContentDocumentLink. Salesforce's default file size limit is 25MB per file; larger files are flagged for manual handling or chunked upload.

Rechat automations (auto-follow-ups, stage triggers, reminder sequences) do not have a direct Salesforce equivalent and cannot migrate automatically. They must be rebuilt in Salesforce Flow. FlitStack exports Rechat automation definitions as a JSON reference file so your Salesforce admin can recreate the logic manually with clear trigger events, conditions, and actions documented.

Rechat Lucy AI assistant configurations, automated response templates, and meeting summarization rules have no direct Salesforce equivalent. Salesforce Einstein AI (available on Unlimited and Agentforce 1 tiers) provides separate lead scoring and opportunity insights, but these require fresh configuration after migration with new data sets and business rules.

Rechat marketing campaigns map to Salesforce Campaigns with campaign name, status, start date, and end date preserved. Contact enrollment maps to Campaign Member records with Status field reflecting enrollment state. Campaign performance metrics such as open rates and click-through rates stored in Rechat cannot transfer and must be tracked independently in Salesforce Marketing Cloud post-migration.