Migrate from Rechat to Twenty CRM

Real estate custom fields have no native Twenty CRM equivalent and require upfront schema design

Rechat's real estate custom fields — MLS listing number, property type, listing status, transaction type, and brokerage-specific pick-lists — are not matched by any native Twenty CRM field. These must be modeled as Twenty custom fields (Settings > Data Model) before data lands. The mapping is straightforward but requires your Twenty admin to pre-create the fields, decide on field types (text, select, multi-select), and define the stage pipeline so deal stage mapping is consistent. Skipping this step means Rechat custom field data lands as orphaned records or gets dropped during the import validation step. FlitStack delivers a custom-field creation checklist as part of the pre-migration plan so the schema is ready before the first CSV is uploaded.

Twenty's workflow builder has trigger-field specificity limitations that affect how automations can be rebuilt

Rechat's Flows automation engine supports touch reminders, date-triggered follow-ups, and conditional logic scoped to specific events. Twenty's workflow builder uses a trigger/action model where listening to 'any field update' on a record and updating fields on the same record can create a recursive loop — this is a documented Twenty community issue (GitHub PR #17858 addresses a specific version). Teams migrating complex Rechat flows that touch multiple fields on a single record need to review those automations in Twenty's workflow builder before assuming feature parity. We provide a Rechat workflow audit export so your admin has the original logic documented for a faithful rebuild.

Twenty's CSV import caps at 20,000 records per run — larger migrations require API calls

Twenty's CSV import function supports up to 20,000 records per import run (documented in Twenty's Data Migration guide). Rechat migrations with more than 20,000 contacts, companies, or deals require chunked CSV files or the Twenty REST API. The API rate limits are 100 calls per minute on Pro and 200 calls per minute on Organization plan — FlitStack handles chunking and rate-limit-aware API calls automatically, but the migration timeline for large datasets may extend beyond the initial estimate if the source dataset is heavily fragmented. We surface record counts during the pre-migration audit so the chunking strategy is set before the migration runs.

Rechat's email body is not stored on Rechat's servers — only metadata migrates for email activities

Rechat's FAQ explicitly states that email body content is retrieved live from the connected Gmail or Outlook account and never saved on Rechat servers. The migration can only extract Rechat's email activity metadata (subject, sender, recipient, timestamp). Full email content remains in the source email account — if agents disconnect their Gmail/Outlook from Rechat or change employers, the email context in Rechat becomes inaccessible. Twenty's email integration (SMTP or Gmail connector) is separate from Rechat's sync; the migration does not re-establish email connections. Teams that rely on email body content stored in Rechat should export and archive it separately before the migration cutover.

Rechat MLS live-sync and transaction template features do not transfer — MLS integration must be rebuilt

Rechat's MLS integration provides live listing data sync and transaction template automation for real estate workflows. Twenty CRM has no native MLS connector — this feature has no equivalent in Twenty's standard data model. Listing data stored in Rechat as custom fields migrates as static data (the last-synced values), but the live MLS refresh stops when Rechat is decommissioned. If your team relies on MLS-triggered automations (e.g., listing status changes that update deal stage), those sequences must be rebuilt in Twenty's workflow builder or handled via a separate MLS data connector. FlitStack surfaces every MLS-related custom field during the audit so your admin knows exactly what needs a replacement integration.