Migrate from Property Minder to Pipedrive

Property Minder contacts map directly to Pipedrive Persons. Name, email, phone, and address fields transfer as-is. Owner resolution uses email matching against Pipedrive users. Contacts without email get flagged for manual owner assignment before migration. If a contact's email matches multiple Pipedrive users, we create a unique match based on additional criteria such as name or department.

Property Minder leads not yet converted to clients route to Pipedrive Leads. Leads Inbox in Pipedrive captures pre-qualified prospects separately from active clients in the Persons module. Conversion creates a linked Person record automatically. We recommend reviewing the Leads Inbox after migration to ensure proper routing and to merge any duplicates.

Property Minder property data (address, listing price, property type, status) does not have a native Pipedrive equivalent. We map property details to custom fields on a mirrored Organization record, or optionally to a custom Property object. Your admin chooses the structure before migration.

Property-specific attributes (listing ID, property type, asking price, listing status) migrate as custom fields on the linked Person or Organization record. Pipedrive's field types (text, number, varchar, enum) are matched to source field types during mapping. If a source field uses a picklist, we map it to a Pipedrive enum field with matching options to preserve data integrity.

Property Minder deals representing active purchase/sale transactions map to Pipedrive Deals. Deal name, value, stage, and expected close date transfer. Pipedrive Deal stages are configured to match Property Minder's transaction lifecycle (Inquiry, Offer, Under Contract, Closed). We also preserve the original deal creation date as a custom datetime field for historical reporting continuity.

Property Minder deal stages map to Pipedrive pipeline stages by value. We preserve the stage-enter timestamp as a custom datetime field. Stage probability weights are configurable in Pipedrive per stage and set during migration configuration. If you require custom probability assumptions per stage, we can adjust them before the final import.

Property Minder viewings and property showings map to Pipedrive Activities of type 'Meeting' with original timestamps and duration preserved. Notes attached to viewings become Activity notes. The linked Property reference is preserved as a custom field on the Activity. If a viewing has multiple participants, each is linked as an Activity participant.

Property Minder inquiries and buyer questions map to Pipedrive Activities of type 'Task' or 'Email' depending on the communication channel. Original timestamps and contact associations transfer. Unassigned inquiries route to a default Pipedrive user during migration. You can specify the default user in the migration configuration to ensure inquiries land with the appropriate team member.

Property Minder notes attached to contacts, properties, or deals migrate as Pipedrive Notes. Rich-text formatting is preserved where supported. Notes are linked to the parent Person, Organization, or Deal record by reference. If a note contains embedded images, we store them as file attachments and link them to the note record for complete context.

Property Minder file attachments (listing photos, contracts, disclosures) re-upload to Pipedrive Files. Files are linked to the parent record by type. File size limits from Pipedrive's storage tier apply — files exceeding limits are flagged for manual handling. We recommend reviewing the flagged files after migration to upload them manually to avoid data loss.

Property Minder custom fields specific to your setup (commission rate, listing source, buyer preference profile) require corresponding custom fields in Pipedrive. We deliver a custom-field creation guide as part of the migration plan. Fields must be created before the migration run to enable mapping.

Property Minder agent and owner records resolve by email match against Pipedrive users. Unmatched owners are flagged before migration. You can invite them to Pipedrive first or assign their records to a fallback owner. No record lands without a Pipedrive owner reference.