Migrate from Propertybase to Twenty CRM

Propertybase Individual Contacts (SystemIsIndividual=TRUE) map directly to Twenty People. The ghost Account record that Salesforce requires for all contacts is discarded — Twenty People records have no mandatory AccountId requirement. Original create dates are preserved as a custom field since Twenty's CreatedAt is set at import time.

Propertybase Company Contacts (SystemIsIndividual=FALSE) split into a Twenty People record (the contact person) and a Twenty Company record (the agency or brokerage they work for). The Person is linked to the Company via the companyId field. This separates the individual from the firm they represent.

Propertybase Accounts map directly to Twenty Companies. Company name, domain, industry, employee count, and annual revenue translate field-for-field. Parent-account hierarchies (if used) map to the Twenty Companies' own companyId for self-referential parent linking. Multi-company contact links are preserved as Twenty People-Company associations.

Propertybase deals stored as Salesforce Opportunities migrate to Twenty Opportunities. Deal name, amount, close date, stage, and probability translate with value-mapping on stage names. The Opportunity is linked to the primary Company and the primary associated People record via Twenty's companyId and peopleId fields.

Propertybase Listings are a custom Salesforce object tracking property-level data. Since Twenty has no native Listing object, FlitStack creates a Listing custom object in Twenty under Settings → Data Model before import. Property fields (address, price, bedrooms, bathrooms, sqft, listing status) are recreated as Twenty fields of the appropriate type.

Propertybase Offer/Contract records track purchase offers linked to Listings and Contact purchasers. These migrate as a second Twenty custom object (Offer) with lookup relations to the Listing and People custom objects. Offer amount, status, and terms fields map to identically named fields in Twenty. The Offer → Listing link uses Twenty's relation field type pointing to the Listing custom object.

Propertybase logged calls, emails, and meetings stored as Salesforce Tasks and Events migrate to Twenty Tasks. The Subject field carries the activity type (Call, Email, Meeting), and description fields preserve body text. Original timestamps and assigned owners are carried over. Recurring tasks and calendar Events are simplified to individual Task records in Twenty.

Propertybase Leads that have not been converted to Contacts are imported as Twenty People records tagged with a Lead_Source__c custom field to preserve origin. If a Lead has a corresponding Account or Opportunity in Propertybase, those relationships are preserved by matching on the source record's ID stored in a Source_System_ID__c field on the Twenty People record.

Propertybase owner assignments (Salesforce User IDs on Contacts, Accounts, Opportunities) are resolved by email. FlitStack matches the owner email on each Propertybase record to a Twenty workspace Member invited before migration. Unmatched owners are flagged in a pre-migration audit report; your team either invites those users to Twenty first or designates a fallback owner for assignment.

Propertybase file attachments on Listings, Offers, or Contacts are downloaded from Salesforce Files and re-uploaded to Twenty, attached to the corresponding record as a Note with a file link. Salesforce's 25MB per-file limit applies during extraction; files larger than this are flagged for manual handling.

Propertybase custom fields added to Listings — such as property type, HOA fees, MLS number, or days-on-market — are created as Twenty fields on the Listing custom object before the data load. Field types are matched (text, number, select, date) based on Propertybase field metadata. Fields marked required in Propertybase are set required in Twenty's Data Model.

Propertybase Workflow Rules govern offer-stage changes, listing-status updates, and contact assignment automation. These are platform-configured Salesforce workflows with no Twenty equivalent. FlitStack exports the workflow definitions as JSON reference documents your team uses to rebuild equivalent automations in Twenty's Settings → Workflows. This is a manual rebuild step — plan 1–3 days of configuration work.