Migrate from PropFlo to Twenty CRM

PropFlo Contact maps 1:1 to Twenty People object. All standard contact properties such as first name, last name, email address, phone number, job title, and physical address fields map directly to their corresponding Twenty People fields. The contact-to-company association from PropFlo resolves cleanly through the people.companyId field, which points to the migrated Companies record by ID. Custom contact fields in PropFlo are also transferred as custom fields on the Twenty People object during migration.

PropFlo Company maps directly to Twenty Companies object. Fields including company name, domain, industry classification, employee count, and annual revenue transfer directly. PropFlo company hierarchies featuring parent and child relationships are preserved using Twenty's same-instance relation capability on the Companies object, maintaining organizational structure across the migration. Any custom company fields migrate as custom fields on the Companies record.

PropFlo Deal maps directly to Twenty Opportunities object. Deal name, monetary amount, pipeline stage, and expected close date transfer directly to their corresponding Twenty Opportunity fields. PropFlo's pipeline stages map to Twenty's configurable opportunity stage pick-list values, which your Twenty administrator can customize to match your sales process. Deal-level custom fields and the PropFlo deal owner also transfer to Twenty with this mapping.

PropFlo Property is a real-estate-specific object with no Twenty standard equivalent. We create a PropertyListing custom object in Twenty with fields for property type, address components, listing status, price, and bedrooms/sqft. Each listing is linked to the owning Company record via a relation field.

PropFlo AOS records have no standard CRM equivalent. We store AOS data (agreement date, terms, parties, plot/unit reference) as a structured JSON custom field on the related Twenty Opportunity. A rebuild in Twenty can split this into separate fields if needed.

PropFlo demand notes containing payment milestone details, amounts due, and demand status have no native Twenty CRM equivalent. These migrate as three separate custom fields on the related Opportunity record: DemandNote_Status__c stores the current status, DemandNote_AmountDue__c holds the outstanding payment amount, and DemandNote_DueDate__c captures the payment due date. These fields enable your team to track payment progress directly within Twenty's Opportunity view.

PropFlo calls and emails map to Twenty Tasks with type indicated in the task body. Meetings map to Twenty Events with original start/end times preserved. Notes migrate as Twenty Notes attached to the relevant People or Opportunities record by ID.

PropFlo owner and assignment fields resolve against Twenty Workspace Members by email match. Unmatched owners are flagged before migration — your team either creates the Twenty user first or assigns records to a fallback member. No record lands without a Twenty owner.

PropFlo custom objects beyond Property, AOS, and DemandNote map directly to Twenty custom objects with their field structures preserved. For PropFlo custom objects that use an N:N relationship model between entities, a linking custom object must be created in Twenty to maintain those associations — we identify and document each N:N relationship requiring a junction object in the pre-migration mapping document provided before migration execution begins.

PropFlo file attachments on records migrate as Twenty Notes with the file content stored as an attachment. File size limits apply (Twenty's attachment size limit is 10MB per file in cloud deployments). Inline images in PropFlo notes are rehosted and linked.