Migrate from Real Estate CRM Software to Pipedrive

Direct map. Pipedrive Person records store name, email, phone, and address fields. Primary phone and secondary phone in the source map to Pipedrive's phone and mobile fields. If the source stores multiple email addresses, the primary email maps to Pipedrive's email field and secondary emails are preserved as custom fields.

Direct map. Pipedrive Organization records represent brokerages, property management firms, or any company associated with a transaction. Organization name, website, and address fields map directly. Parent-child company hierarchies in the source map to Pipedrive's owner_org_id for sub-organization relationships. If the source uses a flat list without hierarchy, each company becomes a standalone Organization record.

Direct map. Pipedrive Deal records represent individual transactions or listings. Deal name, value (commission or sale price), expected close date, and stage map directly. Pipedrive's deal_value field stores the monetary amount; the source's commission field maps to a custom field if the percentage or flat fee needs separate tracking.

Each distinct pipeline in the source (e.g., Buyer Pipeline, Seller Pipeline, Rental Pipeline) becomes a separate Pipedrive Pipeline. Pipeline stages in the source map to Pipedrive Stage records within each pipeline, with stage names, probabilities, and forecast category re-applied. Pipedrive requires at least one active stage per pipeline.

Pipedrive has no native Property object. Listings are represented as Deals with property details (address, MLS number, property type, bedrooms/bathrooms) stored as custom fields on the Deal record. The property address can also be stored in the linked Organization for portfolio-level tracking.

Showings, inspections, and general notes from the source map to Pipedrive Activities. Type is set to 'meeting' for showings and 'note' for general observations. Original timestamps and owner assignments are preserved. Standalone notes not linked to a specific deal or person are imported as unattached activities.

Logged emails from the source system map to Pipedrive Activity records with Type set to 'email'. Pipedrive stores email content in the Activity's subject and body fields. Email attachments are downloaded and re-uploaded as Deal or Person files. Note that Pipedrive does not support threaded email conversation view at the CRM level.

Tasks and reminders from the source map to Pipedrive Activities with Type set to 'task'. Due dates and assigned owners are preserved. Completed status maps to Pipedrive's marked_as_done flag. Overdue tasks retain their original due date. Recurring tasks are imported as a series of individual Activity records with their respective due dates.

Owners are resolved by email match against Pipedrive users. If a source owner email does not match an existing Pipedrive user, the record is flagged for manual assignment or a fallback owner is applied. Provisioning Pipedrive accounts for all active agents before migration eliminates owner-resolution gaps.

If the source uses custom objects for property types, rental units, or listing statuses, FlitStack maps these to Pipedrive custom fields on Deal or Organization. Many-to-many relationships (a property linked to multiple agents) are resolved by creating the primary relationship in Pipedrive and surfacing secondary links as custom multi-select fields.

File attachments on contacts, deals, or properties are downloaded and re-uploaded to Pipedrive's Files section, linked to the corresponding Person, Organization, or Deal record. Pipedrive's file size limit is 150MB per file. Files exceeding this limit are flagged for manual handling.

Source tags are preserved as Pipedrive custom fields of type 'varchar' (text) if they represent a small set of categorical values, or stored as comma-separated values in a single custom field. High-cardinality tag sets (more than 50 unique values) are reviewed with the customer before migration to determine the best storage approach.