Migrate from Realvolve to Twenty CRM

Realvolve's contact records map directly to Twenty's People object. Every contact field — name, email, phone, address, job title — translates to the equivalent Twenty field. Contacts without a primary company land in Twenty with no companyId and are flagged for manual linking.

Realvolve company records map to Twenty's Companies object. Company name, domain, industry, employee count, and address fields translate directly. Parent-child company relationships in Realvolve map to Twenty's Parent CompanyId field where supported.

Realvolve Transactions become Twenty Opportunities. The transaction's deal value maps to opportunity amount, close date maps to the expected close date, and stage names map to Twenty's pipeline stage values. Transaction-specific fields (MLS number, listing status) migrate as custom fields on the Opportunity.

Realvolve's Property object has no direct equivalent in Twenty. We create a Property custom object in Twenty with fields for address, MLS number, listing status, property type, and association to the seller/buyer People record. Property links to the Transaction Opportunity maintain the relationship chain.

Realvolve's contact grading system (A/B/C/D categories) has no Twenty equivalent. We migrate the category as a custom select field (Contact_Category__c) on the People object with the same A/B/C/D values preserved.

Realvolve tasks map to Twenty Tasks with task title, body, due date, and assigned user preserved. Completed status and completion timestamps carry over. Tasks linked to specific contacts or transactions maintain their record associations in Twenty.

Realvolve notes migrate to Twenty Notes. Note body text, author, and create timestamp are preserved. Notes attached to contacts or transactions link to the corresponding People or Opportunity record via Twenty's relation system.

Realvolve workflow definitions are not exported via API in a portable format. FlitStack exports the workflow rule list and trigger/action definitions as a JSON reference file. Your Twenty admin rebuilds the automation logic in Twenty's workflow builder using this reference.

Realvolve file attachments on contacts, companies, or transactions are re-uploaded to Twenty. We attach them to the corresponding Note record or link via Twenty's attachment model. File size limits apply; files over 25MB are flagged for compression or external hosting.

Realvolve user accounts are resolved by email match against Twenty Workspace Members. Unmatched owners (e.g., inactive Realvolve users) are assigned to a fallback Twenty user. Role and permission sets differ between platforms and require manual reassignment in Twenty.

Realvolve transaction stages (Active Listing, Under Contract, Pending, Closed) map to Twenty opportunity stage values. We create a custom stage pipeline in Twenty matching Realvolve's lifecycle order. Stage probabilities are set per stage name based on your specified rules.

Realvolve links contacts to transactions as buyer or seller. These roles migrate as Opportunity Contact Roles in Twenty. Multiple contacts on one transaction maintain their role assignments as multiple Opportunity Contact Role records.