Migrate from Property Shell to Twenty CRM

Property Shell Lead records map 1:1 to Twenty People. Standard fields including first name, last name, email address, phone number, and source campaign migrate as their direct Twenty equivalents. Mobile numbers map to the phone field if no separate mobile field exists. Owner assignment resolves by email match against Twenty workspace members — the owner email on each Property Shell Lead is matched to a confirmed Twenty user account, and unmatched owners are flagged before migration so no record lands without an assignee.

Property Shell Projects — representing a development site or property project — map to Twenty Companies. The project name becomes the Company displayName, address fields map to the address compound, and the development type maps as a custom select field on the Company record.

Property Shell Unit records — representing an individual apartment, lot, or villa within a development — map to Twenty Opportunities with unit-specific properties (unit number, floor, bedrooms, car spaces) stored as custom fields on the Opportunity. The linked Project becomes the Opportunity's CompanyId. If Units are numerous (>500 per project), a dedicated custom object is recommended instead.

Property Shell contract records — including variation tracking and settlement status — have no native equivalent in Twenty. We create a Contract custom object in Twenty with fields for contract number, exchange date, settlement date, purchaser name (linked to People), and related Opportunity. This must be configured in Settings → Data Model before migration runs.

Property Shell engagement logs — calls, meetings, and notes — map to Twenty Tasks and Notes respectively. Call logs and meeting notes from Property Shell become Twenty Task or Note records on the linked People record. Original timestamps, owner assignments, and any attached file references are preserved during migration. The Task Type field on each Task is set to 'Call' or 'Meeting' based on the source activity kind detected in the Property Shell export.

Property Shell tracks deposit amounts, payment milestones, and receipt status as part of its contract management. These have no Twenty equivalent — we create a PaymentRecord custom object with fields for amount, currency, milestone type, status, and linked Opportunity/Contract. Payment status must be rebuilt in Twenty as a custom select field.

Property Shell settlement stages map to Twenty Opportunity stage values. Each stage maps value-by-value: 'Off-the-plan' → 'Prospecting', 'Under Construction' → 'Qualification', 'Completed' → 'Proposal Sent', 'Settled' → 'Closed Won'. Stage transition timestamps are preserved as custom datetime fields for reporting continuity.

Property Shell users and agent assignments resolve by email match against Twenty workspace members. User records are extracted from Property Shell ownership and assignment fields, then matched by email address to existing Twenty workspace members. Users without a matching Twenty account must be invited via Settings → Members and accept the invitation before migration runs, ensuring all owner lookups resolve correctly on import.

Property Shell files attached to Leads, Projects, or Units are downloaded and re-uploaded as linked files in Twenty. File size limits depend on the hosting configuration — self-hosted Twenty has no platform-level size cap; Twenty Cloud has a 25MB per-file limit.

Property Shell tracks lead source campaigns (portal listings, display suite visits, referral programs). These store as a custom select field on Twenty People. Campaign-level performance data does not migrate — source attribution is preserved but campaign analytics must be rebuilt in Twenty's reporting module.

Property Shell automated nurture journeys and email sequences do not have a structural equivalent in Twenty CRM. The sequence definitions (triggers, delays, email content) are exported as a JSON reference document for manual rebuild in Twenty's workflow engine or an external email tool.

Property Shell allows multiple agents assigned to a single lead or unit. In Twenty, the primary agent maps to Opportunity assignee; secondary agents are added via a multi-select relation field on the Opportunity or a custom junction object if the relationship is many-to-many.

Property Shell development property types map as custom select fields in Twenty. The pick-list values are mapped one-by-one: 'Residential' → 'Residential', 'Commercial' → 'Commercial', 'Industrial' → 'Industrial', 'Land' → 'Land'. These can live on the Company record (for project-level typing) or on the Opportunity (for unit-level typing).