Migrate from Rechat to Zoho CRM

Rechat People map directly to Zoho CRM Contacts. The primary company stored on the Rechat contact migrates as a lookup to the corresponding Zoho Account. Contacts without a primary company receive a default 'Unassigned' Account or are held for owner-resolution review before commit.

Rechat contacts flagged as cold prospects or imported leads route to Zoho CRM Leads. The split is based on a Rechat contact property indicating lead status. All contact fields (name, email, phone, address) map identically to Zoho Lead fields. Lead status values map to Zoho's Lead Status pick‑list, aligning pipeline views with original stages. Leads convert to contacts and accounts via Zoho's conversion workflow, preserving the Rechat ID for reference.

Rechat Company objects map to Zoho CRM Accounts. Company name maps to Account Name; domain/website maps to Account Website. Parent-company relationships in Rechat map to the Zoho Account ParentId lookup field — parent accounts must be migrated first to avoid circular reference failures.

Rechat Deals map to Zoho CRM Deals with deal name, amount, close date, and owner directly transferred. The Rechat pipeline field maps to Zoho's Pipeline field; stage values map value-by-value to Zoho Stage pick-list entries. Amount transfers as a value, applying Zoho's currency settings. Custom currency fields map to Zoho custom fields, and the Rechat deal ID is stored in Source_System_ID__c for reconciliation. Stage‑transition timestamps are stored as datetime fields.

Rechat pipelines migrate to Zoho CRM Pipelines. On Zoho Enterprise and Ultimate plans, multiple pipelines are supported natively. On lower plans, a single pipeline is used and stage names carry the original pipeline name as a prefix to prevent stage collision.

Each Rechat pipeline stage value maps to a corresponding Zoho Deal Stage value. Stage ordering, probability percentages, and forecast category are reapplied in Zoho. Stage-transition timestamps from Rechat are preserved as custom datetime fields on the Deal record. If a Rechat stage does not exist in Zoho, it is created as a pick‑list entry before mapping. Stage colors are set after migration, and automation triggers are noted for Blueprint recreation.

Rechat Listings are a custom object with property-address fields, MLS numbers, status, and associations to contacts and deals. No Zoho native equivalent exists — FlitStack creates a custom Listing module in Zoho CRM, defines the required fields before data lands, and maps all listing records with their contact and deal associations preserved via lookup fields.

Rechat Search records capture buyer criteria (area, price range, bedrooms, property type) and link to contacts. These migrate to a custom Property Search module in Zoho CRM. Criteria fields map as text, number, or pick-list fields based on the source data type. Contact lookup on the search record links to the Zoho Contact.

Rechat Tour records represent scheduled property showings tied to contacts and listings. A custom Tour module is created in Zoho CRM with scheduled date/time, listing lookup, contact lookup, and status fields. Event records in Zoho are optionally created as companion records for calendar visibility.

Rechat call activities migrate as Zoho CRM Tasks with Subject, Status, Related To (linked to Contact or Deal), and original call date preserved. Call disposition and duration from Rechat map to Task description and custom number fields respectively. Call direction (inbound/outbound) is stored in a custom pick‑list field, and call notes are added to the Task description. Task status is set to Completed to indicate the call is logged.

Rechat stores email metadata (subject, teaser, date) only — not the full body. This metadata migrates as Zoho Task records. Full email content cannot be migrated as Rechat does not persist it. Zoho Mail integration must be reconnected post-migration for ongoing email tracking.

Rechat meeting activities map to Zoho CRM Events with Subject, Start DateTime, End DateTime, and related Contact/Deal preserved. Recurring meetings are squashed to a single entry in Zoho's bulk export format per API documentation — recurring-event detail is summarized in the Event description field.

Rechat notes migrate to Zoho CRM Notes attached to the appropriate parent record (Contact, Account, or Deal). Rich-text formatting from Rechat is preserved where possible; plain-text fallback is applied for complex formatting that does not map cleanly to Zoho's note format.

Rechat file attachments are re-uploaded to Zoho CRM as Attachments on the parent record. File size limit in Zoho is 25 MB per file. Inline images embedded in Rechat notes are extracted, rehosted, and the image URL is updated in the Zoho Note body.

Rechat users are matched to Zoho CRM users by email address before migration. Zoho requires Role IDs and Profile IDs when provisioning users — these must be retrieved from Zoho's settings before migration runs. Unmatched owners are flagged; records are assigned to a fallback owner or held for manual resolution.