Migrate from Realvolve to Zoho CRM

Realvolve Person records map to Zoho Lead by default. If the Realvolve Person has a closed transaction associated, we route that record as a Zoho Contact linked to the mapped Account. The split is determined by the presence of a Realvolve Transaction with status 'Closed' — any person with a closed transaction becomes a Contact; all others become Leads.

Realvolve Company maps directly to Zoho Account. Company name populates Account Name. Domain/website maps to the Account Website field. Industry pick-list values are mapped value-by-value to Zoho's industry pick-list; unmapped values are preserved as a custom Industry_Text field. Employee count and annual revenue transfer as-is.

Realvolve stores parent-company links via the parent_company_id field. Zoho Account has a native Parent Account lookup. We resolve the parent reference during migration so that the parent Account is created first and the child Account's Parent Account field is populated with the correct Account ID.

Realvolve Deal records map to Zoho Deals module. Deal name maps to Deal Name, deal price maps to Amount (as currency field), deal stage maps to Stage Name via value mapping, and close date maps to Close Date. The Realvolve transaction type (Buy, Sell, Lease, etc.) is stored as a custom pick-list field on the Zoho Deal since Zoho Deals have no native transaction-type attribute.

Realvolve pipelines map 1:1 to Zoho CRM Pipelines. Each Realvolve pipeline becomes a named Zoho Pipeline within the Deals module. Stage values are mapped value-by-value to Zoho stage names. Probability weights and forecast categories are applied per stage in Zoho after migration.

Realvolve's unified Activity log is split into separate Zoho objects: tasks (general to-dos), Events (calendar meetings), and Calls (logged calls). The activity type field in Realvolve determines the target Zoho module. Original timestamps, owners, and related person/company links are preserved. Note-type activities migrate as Zoho Notes attached to the relevant Lead or Contact.

Realvolve Workflow Packages (Tenant Suite, Premium Suite, etc.) are purchasable add-ons that store workflow definitions in Realvolve's proprietary format. These do not export as standard data. FlitStack documents each active workflow as a structured JSON file describing triggers, conditions, and actions — this becomes the rebuild specification for Zoho Blueprint and workflow rules.

Realvolve file attachments associated with People, Companies, or Deals are downloaded and re-uploaded as Zoho Attachments on the corresponding Zoho record. Inline images in Realvolve notes are extracted, rehosted, and relinked in Zoho. Zoho's 25 GB total storage limit per organization applies; large file batches may require pre-migration storage review.

Realvolve user records (name, email, role) are matched against Zoho CRM users by email address. Unmatched users are flagged before migration — your team either creates the Zoho user first or assigns records to a fallback Zoho user. Realvolve team-member roles map to Zoho profiles and roles where parity exists.

Realvolve custom fields (MLS Number, Property Address, Listing Status, Commission Split, etc.) are replicated as Zoho custom fields on the corresponding module. Field data types are preserved: pick-lists become Zoho pick-lists, date fields become Zoho date fields, numeric fields become Zoho number fields. Zoho allows a maximum of 50 fields created during migration via the Data Migration wizard; additional fields are created via the Fields API before or after the migration run.

Realvolve tags on People, Companies, or Deals migrate to Zoho Tags on the corresponding record. Zoho tags support up to 25 characters; longer Realvolve tags are truncated at migration time. Tags with more than 10 values on a single record in Realvolve are truncated to the first 10 in Zoho.

The original Realvolve record ID is stored as a custom text field (Realvolve_ID__c) on each Zoho record for traceability, duplicate detection in future delta runs, and audit purposes. This field is indexed and used in the delta-pickup window to identify records modified in Realvolve after the initial migration cut.