Migrate from VaultRE to Twenty CRM

VaultRE contacts migrate directly to Twenty People records. The primary company association maps to Twenty's companyId relation. VaultRE contact types (buyer, seller, tenant, landlord) migrate as a custom pick-list field (Contact_Type__c) since Twenty has no native equivalent for multi-type contacts.

VaultRE allows a contact to be simultaneously classified as buyer, seller, tenant, and landlord. We preserve each active type as comma-separated values in a custom Contact_Type__c select field on Twenty People. This is a manual decision point — some teams prefer separate contact records per role.

VaultRE agency and company records map to Twenty Companies, with standard fields like name, phone, website, and address transferring directly. For agencies with a multi-office structure, each VaultRE office can become a separate Company record, or you can use a custom Office_ID__c field to tag offices without creating multiple company entries.

VaultRE property listings require a custom object in Twenty since there is no native property entity. We define Property__c with fields for listing type (sales/rental), status, price, address, and listing agent. The property links to a Company record (agency) and to People records (vendor/landlord contacts) via lookup relations.

Rental listings use the same Property__c custom object with a Listing_Type__c pick-list to distinguish 'Sale' from 'Rental'. Weekly rent is stored in a Number field. Bond amounts and tenancy dates are captured in custom date fields on the Property__c record.

VaultRE deal records (engagement on a listing) map to Twenty Opportunities. Stage names from VaultRE's deal pipeline map to Opportunity Stage values. Amount transfers directly. Close date maps to expectedCloseDate for accurate sales forecasting in Twenty.

VaultRE tasks and activity logs migrate to Twenty Tasks with original due dates and assignees resolved by email matching. Body text is preserved in full. Tasks linked to a Property__c or People record maintain their lookup relationship through the migration.

VaultRE notes attached to contacts, companies, or properties migrate to Twenty Notes with rich-text formatting intact. Original author is resolved by matching their email address against Twenty workspace members to preserve attribution.

VaultRE custom database fields including text, date, checkbox, and drop-down types (up to 30 options) are read from the VaultRE field registry and recreated as matching Twenty custom fields on the appropriate object. Drop-down fields become select fields with values mapped one-to-one.

Property-specific VaultRE custom fields such as building name, property features, and inspection notes migrate to custom fields on Property__c. Field types are preserved exactly as defined in VaultRE. Merge field names are documented for reference mapping during migration.

VaultRE staff records resolve against Twenty workspace members by matching email addresses. Any unmatched staff are flagged before migration begins — your team can invite them to Twenty or assign records to a fallback owner. VaultRE role permissions do not migrate to Twenty's permission system.

VaultRE integrations with PriceFinder and CoreLogic are external service connections that terminate when you exit VaultRE. They cannot be migrated and must be rebuilt in Twenty using the same APIs. We document the integration endpoints from VaultRE for your technical team to re-establish.