Migrate from PropertySimple to Twenty CRM

PropertySimple contact records map directly to Twenty People. Every field — name, email, phone, address — transfers as a standard People field. Owner resolution uses email match against Twenty workspace members; any PropertySimple owner without a Twenty account is flagged before migration commits.

PropertySimple brokerage and company records map to Twenty Companies. The company name, domain/website, industry classification, employee count, and annual revenue transfer as standard fields. Parent-child company hierarchies in PropertySimple map to Twenty's Parent CompanyId relation, preserving organizational structures across both platforms. Any company records without parent relationships import as standalone Twenty Company entries.

PropertySimple deal records map to Twenty Opportunities. Deal name, amount, stage, expected close date, and owner transfer as standard Opportunity fields. Stage names are mapped value-by-value to Twenty's Opportunities stage pick-list, preserving probability percentages and forecast categories for accurate pipeline reporting. Deal notes and custom fields migrate to the Opportunity record's note section and custom fields respectively.

PropertySimple's agent profile has no direct equivalent in Twenty's standard model. We translate the agent to a People record with a custom AgentRelation junction object linking the agent to their contacts and deals — this preserves the agent-centric relationship without forcing every agent into a standard contact role.

PropertySimple listing records have no Twenty standard equivalent. We create a PropertyListing custom object in Twenty via Settings → Data Model before migration. Fields include listing address, price, status, bedrooms/bathrooms, listing date, and a relation to the agent People record via a custom junction.

PropertySimple's ZIP-code marketing exclusivity zones are a billing and marketing construct with no Twenty equivalent. We create a Territory custom object to hold ZIP codes, exclusivity status, and associated campaigns — linked to the agent People record and the PropertyListing records in that zone.

PropertySimple Autopilot ad campaigns and social media posting schedules are a platform-specific billing feature with no data model in Twenty. We export campaign definitions as a reference document for rebuild using Twenty's workflow builder or an external automation tool like Zapier or n8n.

PropertySimple free-form notes and call logs split into Twenty's Notes and Tasks objects. Text notes become Twenty Notes linked to the relevant People, Company, or Opportunity record. Call logs with disposition, duration, and outcome become Tasks with the Task type set to Call and original timestamps preserved.

PropertySimple custom contact properties migrate as custom fields on Twenty's People object. These must be pre-created in Settings → Data Model before the migration run. We capture the property name, type, and pick-list values to configure the correct field type in Twenty.

PropertySimple lead source tracking (referral, website inquiry, ZIP code advertisement, social media, etc.) has no standard equivalent in Twenty People. We create a LeadSource custom select field on the People object via Settings → Data Model and map each PropertySimple source value to the corresponding option. This preserves attribution data for reporting and allows teams to analyze which channels generate the most qualified leads in Twenty's analytics views.

PropertySimple engagement records — emails, calls, meetings, and follow-up tasks — migrate as Twenty Tasks linked to the relevant People record. Each Task preserves the original timestamp, activity type, and owner. Task.type is set to Email, Call, or Meeting based on the source activity kind.

PropertySimple file attachments on contacts, companies, and deals re-upload to Twenty Notes as file attachments. File size limits are enforced at 25MB per file. Inline images in PropertySimple notes are extracted, rehosted as file attachments in Twenty, and linked to the same Note record.