Migrate from Rechat to Pipedrive

Rechat Person maps 1:1 to Pipedrive Person — name, email, phone, job title, address, and owner all transfer directly. Phone numbers, including mobile phone, map to Pipedrive's phone and mobile fields respectively. Rechat does not store email body content; email metadata (subject, teaser, date, sender/recipient) migrates to Pipedrive Activity records linked to the Person.

Rechat Organizations (brokerages, MLS entities, companies) map to Pipedrive Organization. Address, industry, phone, website, and owner fields transfer directly. The organization's domain (website URL) is stored in Pipedrive's website field. Parent-child hierarchies in Rechat map to Pipedrive's parent Organization relationship, preserving the organizational structure.

Rechat Deal maps to Pipedrive Deal with stage name, amount, expected close date, owner, and associated Person and Organization. The deal's title and value transfer directly. Each Rechat deal pipeline becomes a Pipedrive pipeline; stage values migrate per pipeline with probability mapping, ensuring deal forecasting accuracy is maintained in Pipedrive.

Rechat stores email metadata (subject, teaser, date, sender/recipient) only — no email body. This metadata migrates as Pipedrive Activity records of type 'email' linked to the Person. The full email body remains in the connected Google/Outlook account and must be accessed there post-migration.

Rechat call logs, scheduled meetings, and tasks map to Pipedrive Activity records with original timestamps, duration, owner, and linked Person or Organization preserved. Activity type (call, meeting, task) is mapped by activity_subtype. Due dates and due times transfer to Pipedrive's due_date and due_time fields respectively, maintaining the original scheduling information.

Rechat Campaigns (real estate email marketing, listing blasts, drip sequences) have no Pipedrive equivalent. Campaign membership and campaign-level engagement metrics (opens, clicks) do not migrate. Email automation logic must be rebuilt in a dedicated marketing platform or Pipedrive Automations (Advanced+).

Rechat Flows are automation rules scoped to contacts, deals, and campaigns. Pipedrive Automations are triggered by field changes or deal stage transitions. Flows do not export as executable logic — FlitStack exports the Flow definitions as a JSON reference document for your Pipedrive admin to rebuild manually.

Rechat custom Properties on People (e.g., license number, lead source, buyer/seller flag) require Pipedrive custom Person fields to be created first using the exact property name as the field label. Pipedrive's API assigns a hash key per custom field per account — we store this mapping and reference it during migration.

Rechat Deal properties (transaction ID, property address, MLS number, listing price, commission split, property type) need Pipedrive custom Deal fields created in advance. Real estate domain values (MLS IDs, property types) may need value-mapping if pick-list constraints are applied in Pipedrive. The migration stores the Rechat property name as the Pipedrive field label and preserves the original data type (text, number, currency, picklist).

Rechat Organization properties (brokerage name, MLS association ID, office address type, brokerage description) migrate to Pipedrive Organization custom fields. Long text fields (e.g., brokerage description) migrate as Pipedrive text fields with full content preserved. The migration uses the exact Rechat property name as the Pipedrive field label and matches the data type to ensure data integrity during transfer.

Rechat user accounts map to Pipedrive users by email address match. The migration validates each owner match before processing and generates a resolution report. Unmatched owners (e.g., deactivated Rechat agents) are flagged before migration — their records must be assigned to a fallback Pipedrive user or a dedicated 'Migrated Owner' placeholder to ensure all migrated records have a valid owner.

Rechat Notes attached to People, Organizations, or Deals migrate to Pipedrive Notes with original text, author, and timestamp preserved. The note content transfers in full, including any formatting or embedded links. Notes are linked to the target record by ID after IDs are assigned in Pipedrive, ensuring proper association with the migrated parent record.