Migrate from PropertySimple to Pipedrive

PropertySimple contacts map directly to Pipedrive Person records. Standard fields (name, email, phone, address) transfer as-is. Custom properties on contacts migrate to Pipedrive custom fields on the Person object via the /personFields API endpoint. Original create timestamps are preserved as a custom field since Pipedrive's created_at is set at migration time.

PropertySimple companies transfer as Pipedrive Organizations. Fields including name, domain/website, industry, address, and employee count map to their Pipedrive equivalents. Multi-address companies are handled by migrating the primary address and storing secondary addresses in a custom field for admin review.

PropertySimple deals map to Pipedrive Deals with direct field transfer for name, value/amount, expected close date, and owner. Deal stage names from PropertySimple pipelines map to Pipedrive stage names within the corresponding Pipedrive pipeline. Stage probability weights transfer as Pipedrive stage probability values.

Each PropertySimple pipeline becomes a Pipedrive Pipeline. Pipeline-level settings (name, stage count, stage order) transfer directly. Pipedrive Pipelines use a visual Kanban view; stage colors transfer as Pipedrive stage color codes if configured. One PropertySimple pipeline maps to one Pipedrive pipeline with matching stages.

Stage names are mapped one-to-one from PropertySimple to Pipedrive within the corresponding pipeline. Stage probability values transfer as Pipedrive stage probability percentages. Stage order is preserved in Pipedrive's stage sequence. Custom stage names (e.g., 'Under Contract', 'Inspection Pending') map directly without transformation.

PropertySimple leads with a status indicating they have not entered a deal flow transfer to Pipedrive's Lead Inbox. Leads that have email addresses and are marked as contacted convert to Persons with org associations. Uncontacted leads remain in Pipedrive's Lead Inbox for follow-up routing before conversion.

PropertySimple custom properties on contacts create Pipedrive custom fields on the Person object. This requires creating the field in Pipedrive via POST /personFields before migration. Field types (text, number, date, picklist) map to Pipedrive's supported field types. Multi-select pick-lists in PropertySimple become Pipedrive set-type fields.

Deal-level custom properties transfer to Pipedrive Deal custom fields via POST /dealFields. PropertySimple deal custom fields (e.g., property address, listing type, referral source) create equivalent Pipedrive fields. Field options are mapped value-by-value for pick-list fields; default values apply where source values have no destination match.

All PropertySimple activity types (calls, emails, meetings, notes) consolidate into Pipedrive's Activity object. The activity type field in Pipedrive distinguishes between call, email, meeting, and task. Original timestamps, subject lines, and body content transfer. Owner attribution maps by email match to Pipedrive users.

Files attached to PropertySimple contacts, companies, or deals are downloaded and re-uploaded to Pipedrive Files. Files attach to the corresponding Person, Organization, or Deal record using Pipedrive's file attachment API. File size limits apply (Pipedrive's default storage limits by plan). Inline images in notes are extracted and rehosted as attachments.

PropertySimple users are resolved by email address against Pipedrive user accounts. Unmatched owners are flagged in the pre-migration report; teams either invite them to Pipedrive first or reassign records to a fallback owner before migration. Owner names and roles transfer as a custom field on records for reference.

PropertySimple contact-to-company associations transfer as Pipedrive Person-Organization relationship links. Each Person can have one primary Organization and multiple secondary org links. The association label (if any) from PropertySimple is preserved as a custom field on the link for admin review and potential reorganization.