Migrate from Rechat to Microsoft Dynamics 365 Sales

Rechat People map directly to Dynamics 365 Sales Contacts. The primary company association in Rechat becomes the AccountId lookup on the Contact. Rechat contact custom properties migrate to custom fields on the Contact table. Original create dates preserved as Source_Create_Date__c for reporting continuity.

Rechat People records that have not been converted to active clients route to Dynamics 365 Sales Lead entity. Rechat lead-stage values (New, Contacted, Qualified) map to Lead Status pick-list values. People records with a closed deal in Rechat route to Contact instead.

Rechat Companies map to Dynamics 365 Sales Accounts. Company industry codes, employee counts, and annual revenue map to corresponding Account fields. Parent-company hierarchies in Rechat map to Account.ParentId in Dynamics 365 Sales. Website and address fields transfer directly. Any custom properties defined on Rechat Companies become custom fields on the Account record and are populated during migration.

Rechat N:N contact-to-company associations with role labels (Agent, Broker, Buyer, Seller) map to Dynamics 365 Sales Account Contact Relationships. The role label on each Rechat association becomes the Account Contact Relationship Role field. Primary company selection preserved as the Contact.AccountId lookup.

Rechat Deals map to Dynamics 365 Sales Opportunities. Deal name becomes Opportunity Name, amount transfers to Amount, and close date maps to CloseDate. Rechat deal stage names map to Opportunity StageName values via value-by-value mapping. The associated Contact or Lead link becomes the Opportunity CustomerId (Contact) or the Opportunity."Account".Id lookup.

Rechat Deal-level custom properties (listing reference, property type, commission split) require custom fields on the Opportunity table in Dynamics 365 Sales. We create these as text, number, or pick-list fields based on Rechat's field type definitions before migration. Field metadata preserved in Source_Property_Mapping__c for reconciliation.

Rechat Listings are a real-estate-specific object without a native Dynamics 365 Sales equivalent. We create a custom Listing table in Dataverse with fields for MLS ID, property address, listing status, and price. Each Listing links to the associated Contact (agent) and Account (brokerage) via lookup fields. If Listings should roll up under Opportunities, we create Opportunity.ListingId__c as a custom lookup.

Rechat activities synced from Google/Outlook map to corresponding Dynamics 365 Sales activity entities. Emails become Email (activitypointer) records. Calls become PhoneCall records. Meetings become Appointment records. Original timestamps, subject, and duration preserved. Owner attribution resolved by email match to Dynamics 365 Sales users.

Rechat Notes on People, Deals, and Companies migrate as Dynamics 365 Sales Annotations. Rich-text formatting preserved where supported. Note attachments download and re-upload to SharePoint or Dataverse file storage with original filenames. Parent record links (Regarding) map to the corresponding Contact, Account, or Opportunity.

Rechat marketing assets (email templates, social posts, flyers) have no Dynamics 365 Sales equivalent. We create a MarketingAsset custom table to store asset name, type, and a URL reference to the file in destination SharePoint. Full asset rebuilding in Dynamics 365 Customer Insights or Power Automate is a separate workstream.

Rechat agents matched to Dynamics 365 Sales users by email address. Unmatched agents flagged before migration for team invitation or fallback owner assignment. User roles and security profiles in Dynamics 365 Sales must be configured by the customer's admin—those are destination-side configuration, not migratable data.

Rechat workflows, automation rules, and sequences do not migrate. They must be rebuilt in Dynamics 365 Sales using Power Automate flows or Dynamics 365 Sales automation features. We export Rechat workflow definitions as JSON documentation for the rebuild reference. This JSON package serves as the technical specification for your Power Automate or model-driven app rebuild, capturing trigger conditions, action sequences, and filter criteria from Rechat.