Migrate your Rechat data
AI-powered real estate Super App merging CRM, marketing, listing tools, and transactions into one platform for brokers and agents across the US and Canada.
In its favor
Why people choose Rechat
The signal that keeps Rechat on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Agents praised how the Marketing Center, Listing Tools, and CRM work together in one place, eliminating the need to switch between separate platforms for daily tasks.
Real-time two-way sync with Google and Outlook keeps contacts, calendar, and email metadata current across the platform without manual re-entry.
Deep MLS integration allows agents to pull listing data directly into marketing and communicate with clients using verified MLS information.
Rechat's Lucy AI assistant handles routine tasks and automations, allowing agents to focus on closings rather than administrative overhead.
Brokerages with 125+ agent licenses report low churn, citing compliance tools and admin oversight that give back-office teams visibility across the entire team.
Agents without Google or Outlook accounts report being unable to access full automation features, making Rechat feel incomplete as a standalone CRM.
A June 2025 Heroku/Salesforce outage knocked Rechat offline for an extended period, raising concerns about infrastructure dependency on a third-party cloud provider.
Users moving to platforms with published API documentation find Rechat's undocumented endpoints limiting when attempting programmatic data exports.
Rechat's AI assistant Lucy is tightly integrated, making workflows harder to replicate when agents switch to platforms with different automation paradigms.
Brokers seeking simpler per-seat pricing without tier-gated features find Rechat's enterprise-focused model harder to justify for small teams.
Reasons to switch
Why people leave Rechat
The recurring reasons buyers give for replacing Rechat. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Rechat fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Rechat pricing overview
Rechat does not publish pricing on its website. Plans appear to be tiered by brokerage size and agent count, with an Enterprise tier for large brokerages with compliance and admin needs. Prospects must contact Rechat directly for a quote.
Starter / Professional
Tier 1 of 3
Not publicly published
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Rechat's schedule — see our quote-based pricing →
What gets migrated
Rechat object support
Object-by-object support for Rechat migrations. Per-pair details surface during scoping.
Contacts
Fully supportedContacts are the core People object in Rechat. We migrate all standard contact fields plus phone_confirmed status, designation, social links (Instagram, LinkedIn, TikTok, etc.), and any custom properties. Contact export to Excel is natively supported, which we use as a verification baseline alongside the API.
Companies
Mapping requiredCompanies exist as associated entities on Contacts. We map the company relationship and pull company-level fields where present. Companies do not have a standalone full export endpoint, so we derive company records from the contact association.
Deals
Fully supportedDeals is a first-class object with a dedicated feature flag on user records. We migrate deal records including stage, value, associated contacts, and pipeline assignments. Deals are available on all tiers and have a stable schema.
Listings
Mapping requiredListings are tightly coupled to MLS integration. We preserve listing records, addresses, statuses, and agent associations, but MLS-derived images and listing history may require re-syndication on the destination side. Listing-to-contact associations are migrated as custom link objects.
Searches
Mapping requiredSaved Searches represent saved MLS criteria that agents use for client matching. We migrate search criteria and parameters, though automated search-match notifications are Rechat-native and will need manual re-enrollment in the destination system.
Tours
Mapping requiredTours represent scheduled property visits linked to Listings and Contacts. We migrate tour records with date, time, listing reference, and attendee information. Tour status and scheduling sync with Google/Outlook calendar.
Users
Fully supportedUser records include timezone, user_type (Admin, Agent, etc.), features array, email_quota, and online_state. We migrate active users with their role and permissions. Shadow users and soft-deleted accounts are flagged separately.
Flows (Automations)
Not in this platformRechat Flows are internal automation objects (touch reminders, birthday celebrations, drip sequences). These are not exportable via API. We document what automations exist so customers can manually rebuild them in the destination platform.
Email Metadata
Mapping requiredRechat does not store email body content — only title, teaser, and date. We migrate the metadata and reconstruct the association to contacts, but the actual email body will need to remain in the connected Google/Outlook account and be re-linked if needed.
Calendar Events
Mapping requiredCalendar events sync bidirectionally with Google and Outlook. We migrate event metadata (title, time, attendees) but the sync relationship must be re-established manually on the destination platform.
Marketing Campaigns
Mapping requiredCampaigns are created in the Marketing Center with MLS integration. We migrate campaign records, audience lists, and open/click stats. Actual send history and email templates may require re-upload in the destination ESP.
Documents (PDF Forms)
Mapping requiredRechat supports HTML-to-PDF form mapping for compliance documents. We migrate document records and form field data, but the PDF rendering is Rechat-specific and may need re-creation in the destination platform.
Tags / Favorites / Alerts
Mapping requiredContact-level tags, favorites, and alerts are stored per-user. We migrate these as custom contact properties so they land in the destination CRM with the associated contact record.
Lucy AI Assistant Interactions
Not in this platformLucy AI conversation history and task completions are not exposed via API. We do not migrate AI interaction history. We document what Lucy automations were configured so customers can reconfigure on new platforms.
| Object | Support | Notes |
|---|---|---|
| Contacts | Fully supported | Contacts are the core People object in Rechat. We migrate all standard contact fields plus phone_confirmed status, designation, social links (Instagram, LinkedIn, TikTok, etc.), and any custom properties. Contact export to Excel is natively supported, which we use as a verification baseline alongside the API. |
| Companies | Mapping required | Companies exist as associated entities on Contacts. We map the company relationship and pull company-level fields where present. Companies do not have a standalone full export endpoint, so we derive company records from the contact association. |
| Deals | Fully supported | Deals is a first-class object with a dedicated feature flag on user records. We migrate deal records including stage, value, associated contacts, and pipeline assignments. Deals are available on all tiers and have a stable schema. |
| Listings | Mapping required | Listings are tightly coupled to MLS integration. We preserve listing records, addresses, statuses, and agent associations, but MLS-derived images and listing history may require re-syndication on the destination side. Listing-to-contact associations are migrated as custom link objects. |
| Searches | Mapping required | Saved Searches represent saved MLS criteria that agents use for client matching. We migrate search criteria and parameters, though automated search-match notifications are Rechat-native and will need manual re-enrollment in the destination system. |
| Tours | Mapping required | Tours represent scheduled property visits linked to Listings and Contacts. We migrate tour records with date, time, listing reference, and attendee information. Tour status and scheduling sync with Google/Outlook calendar. |
| Users | Fully supported | User records include timezone, user_type (Admin, Agent, etc.), features array, email_quota, and online_state. We migrate active users with their role and permissions. Shadow users and soft-deleted accounts are flagged separately. |
| Flows (Automations) | Not in this platform | Rechat Flows are internal automation objects (touch reminders, birthday celebrations, drip sequences). These are not exportable via API. We document what automations exist so customers can manually rebuild them in the destination platform. |
| Email Metadata | Mapping required | Rechat does not store email body content — only title, teaser, and date. We migrate the metadata and reconstruct the association to contacts, but the actual email body will need to remain in the connected Google/Outlook account and be re-linked if needed. |
| Calendar Events | Mapping required | Calendar events sync bidirectionally with Google and Outlook. We migrate event metadata (title, time, attendees) but the sync relationship must be re-established manually on the destination platform. |
| Marketing Campaigns | Mapping required | Campaigns are created in the Marketing Center with MLS integration. We migrate campaign records, audience lists, and open/click stats. Actual send history and email templates may require re-upload in the destination ESP. |
| Documents (PDF Forms) | Mapping required | Rechat supports HTML-to-PDF form mapping for compliance documents. We migrate document records and form field data, but the PDF rendering is Rechat-specific and may need re-creation in the destination platform. |
| Tags / Favorites / Alerts | Mapping required | Contact-level tags, favorites, and alerts are stored per-user. We migrate these as custom contact properties so they land in the destination CRM with the associated contact record. |
| Lucy AI Assistant Interactions | Not in this platform | Lucy AI conversation history and task completions are not exposed via API. We do not migrate AI interaction history. We document what Lucy automations were configured so customers can reconfigure on new platforms. |
Gotchas
What to watch for in Rechat migrations
Issues we've hit on past Rechat migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Heroku/Salesforce outage risk impacts migration timing
Email bodies are never stored in Rechat
Flows automations are not exportable via API
Lucy AI assistant history is not accessible
Contact export produces flat Excel, not relational data
| Severity | Issue |
|---|---|
| High | Heroku/Salesforce outage risk impacts migration timing |
| High | Email bodies are never stored in Rechat |
| Medium | Flows automations are not exportable via API |
| Medium | Lucy AI assistant history is not accessible |
| Low | Contact export produces flat Excel, not relational data |
Leaving Rechat?
Where Rechat customers move next
12 destinations Rechat can migrate to.
How a Rechat migration works
Four steps, Rechat-specific
Connect
Not publicly documented into Rechat. Scopes limited to read-only on the data we move.
Map
We translate Rechat-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Rechat quirks before production.
Migrate
Full migration with Rechat rate-limit handling. Rollback available throughout.
FAQ
Rechat migration FAQ
Answers to the questions buyers ask most during Rechat migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Rechat migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Rechat.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Rechat setup and destination — written quote back within a business day.