Migrate from AscendixRE to Twenty CRM

Direct 1:1 map. Twenty's Companies object stores organization records with fields for name, domain, industry, and employee count. Salesforce AccountId references in contacts and opportunities resolve to the migrated Company record by name or domain matching. For duplicate account names we apply a disambiguation rule using the website domain, and we preserve the original Salesforce Account ID in a source_system_id field for audit trail.

Direct 1:1 map. Twenty's People object replaces Salesforce Contact. Email, phone, job title, and address fields map directly. The companyId relation links each person to its parent Company record. Owner resolution happens by email match against Twenty workspace members; if an email matches multiple members, the first match is used and a warning is logged. We store the original Salesforce Contact ID in a source_system_id field for traceability.

Direct map for standard deal fields: deal name, amount, expected close date, and stage. Stage values require pick-list mapping because Twenty uses a Select field rather than Salesforce's StageName picklist with probability weights. We preserve original stage-entered timestamps as custom datetime fields in Twenty.

Salesforce Tasks map to Twenty Tasks. Subject, due date, status, and assigned user transfer directly. Status values are mapped: Not Started becomes Open, In Progress stays In Progress, Completed stays Completed. Tasks linked to Contact, Account, or Opportunity retain their parent record link via Twenty's relation field system; tasks without a parent are imported as standalone records. Completed tasks preserve their original completion timestamps, and we store the original Salesforce Task ID in a source_system_id field for audit trail.

Salesforce Notes migrate to Twenty Notes. Body content, title, and parent record links transfer. Rich-text formatting in Salesforce notes is converted to plain text in Twenty's note body field; HTML tags are stripped, preserving basic line breaks. Inline images in notes require separate download and rehosting, and we store the original Salesforce Note ID in a source_system_id field for traceability.

AscendixRE's Property__c object has no direct Twenty equivalent. We create a Property custom object in Twenty's data model, map property name, address, type, square footage, and year built fields, and preserve the original Salesforce Property ID in a source_system_id field for traceability. The custom object must be created in Twenty before migration runs.

Listing__c tracks active listings in AscendixRE. We recreate this as a Listing custom object in Twenty, mapping listing status, asking rent, available square footage, and lease type fields. The Listing-to-Property lookup becomes a Twenty relation field once both custom objects exist in the workspace.

Lease__c stores lease records with tenant name, lease start and end dates, rent amounts, and property links. We create a Lease custom object in Twenty and map these fields directly where field types align. Multi-tenant lease structures requiring junction records are surfaced in the migration plan for admin review.

Capital_Source__c tracks capital providers in AscendixRE. We create a CapitalSource custom object in Twenty with fields for source name, type (equity/debt), target investment range, and contact associations. The migration plan includes the relationship mapping for linking capital sources to deal Opportunities.

Availability__c represents available spaces within a property. We create an Availability custom object in Twenty with fields for space type, floor number, available square footage, and asking rent per square foot. The Availability-to-Property relation maps via Twenty's relation field type.

Salesforce Attachments store file binary data with a ParentId link. Twenty lacks a native binary attachment object, so attachments migrate as Note records with a link to the original file stored externally. The migration plan specifies file size limits and whether files should be rehosted to Twenty's storage or a linked external service.

Salesforce User records owning opportunities and contacts resolve to Twenty Workspace Members. Owner resolution uses email address as the matching key. Unmatched owners are flagged before migration so the team can either invite them to the Twenty workspace or reassign records to a fallback owner before data lands.