Migrate from Property Minder to Twenty CRM

Property Minder contacts map directly to Twenty People records. The People object stores name, email, phone, job title, and a companyId relation. HubSpot-style custom contact properties (lifecycle stage, lead source, etc.) migrate as Twenty custom fields on the People object.

Property Minder companies map to Twenty Companies records. Company names, domains, and industry classifications transfer directly. If Property Minder stores parent-child company hierarchies, the top-level company migrates first, and child companies reference it via a parentCompanyId custom field in Twenty.

Property Minder deals map to Twenty Opportunities. Deal name becomes Opportunity name, amount transfers to a custom amount field (Twenty Opportunities lack a native currency amount field in all tiers — we flag this and recommend a custom field setup before migration runs). Pipeline and stage names migrate as select custom fields.

Property Minder owner IDs resolve by email match against Twenty Workspace Members. If an owner email does not match a Twenty member, records are assigned to a designated fallback user and flagged for review. This step requires Twenty workspace members to be invited and active before migration begins.

Property Minder call logs, emails, and meetings migrate as Twenty Tasks with the task type preserved in a custom type field (Call, Email, Meeting). Meeting start/end times map to Twenty's due dates and custom datetime fields. Notes migrate as Twenty Notes with original body text and timestamps.

Property Minder drip campaigns (IDX listing triggers, open/click events, saved-search alerts) have no native equivalent in Twenty's workflow builder. We export campaign definitions including step order, delay intervals, and trigger conditions as a structured JSON document. Rebuild references are delivered alongside the migration so the team can recreate campaign logic in Twenty's visual workflow editor.

Property Minder custom fields on contacts (real-estate-specific properties like license number, preferred neighborhood, or buyer/seller type) map to Twenty custom fields on People. Twenty requires these fields to be created in Settings → Data Model before import — we deliver a custom field creation checklist as part of the pre-migration workspace setup plan.

Property Minder leads generated through IDX website interactions carry source metadata (listing viewed, search criteria) that does not exist as a standard Twenty field. We capture this as a custom field (Lead_Source_Detail__c) on People records so the original IDX context is preserved for reporting.

Property Minder file attachments on contacts, companies, and deals re-upload as Twenty Notes with a link reference to the file stored in the configured storage backend. If the self-hosted Twenty instance uses local file storage, files are re-hosted on the same infrastructure during migration.

Property Minder's contact-to-company association (a contact may have a primary company) maps directly to People.companyId in Twenty. If a contact has multiple associated companies in Property Minder, the primary company becomes companyId, and secondary associations are captured as a custom multi-select field for admin reference.

Property Minder deal pipeline stages (Active, Under Contract, Inspection, Closed Won, etc.) map to a custom select field (Deal_Stage__c) on Twenty Opportunities. We document the value-by-value mapping before migration and recommend configuring the pick-list options in Twenty's Data Model settings prior to import to avoid import errors.

Property Minder's internal record IDs and original create timestamps are preserved as custom fields (Source_System_ID__c, Original_Create_Date__c) on all migrated objects. This preserves system provenance and supports delta-run de-duplication on future imports, maintaining audit continuity for reporting on deal age and contact tenure from the original Property Minder system.