Migrate from Real Properties to Pipedrive

Real Properties Contact maps directly to Pipedrive Person. All standard person fields including name components, email addresses, phone numbers, and postal addresses transfer as-is to the corresponding Pipedrive Person fields. The owner assignment is resolved by matching the Real Properties owner email against Pipedrive user accounts — if a Pipedrive user with the matching email exists, that user becomes the Person's owner. If no match is found, the record is flagged and assigned to a fallback owner designated by your team before migration begins.

Real Properties Company records map to Pipedrive Organizations. Company name, domain/website, industry classification, employee count, and annual revenue fields transfer to the matching Org fields in Pipedrive. If your Real Properties account includes parent-child company hierarchies, those relationships are preserved using the Org's Parent Organization field in Pipedrive. Each company record must exist in Pipedrive before any Person records that link to it can be written, because Pipedrive requires the Organization to be present for the org_id link to resolve correctly.

Real Properties Property Listing has no native equivalent in Pipedrive. FlitStack creates a Pipedrive Deal with property details (address, listing price, property type, square footage) stored as custom fields on the Deal, and the property address as a linked Organization representing the physical property.

Real Properties Deal maps to Pipedrive Deal. Deal name, amount, stage, close date, and owner transfer directly. The pipeline-to-pipeline mapping is 1:1; stage names are mapped value-by-value based on your Pipedrive pipeline stage configuration.

Real Properties pipeline stages are mapped to Pipedrive deal stages on a per-pipeline basis. Each Real Properties stage name is matched value-by-value to the corresponding Pipedrive stage, and Pipedrive's stage probability percentages and forecast category settings are applied from your Pipedrive stage configuration. If your Real Properties setup includes custom stages that do not have obvious Pipedrive equivalents, your team must make explicit mapping decisions during the pre-migration planning phase. Stages that cannot be matched are flagged for manual resolution before the migration run executes.

Real Properties logged calls, emails, and meetings migrate as Pipedrive Activities. Activity type (Call, Meeting, Task), subject line, timestamp, duration, and the associated person or deal links are all preserved during the migration. The original Real Properties owner is assigned to the matching Pipedrive user based on email resolution. If an activity record references a person or deal that could not be migrated, the activity is attached to the nearest available parent record to preserve the historical context as completely as possible.

Real Properties notes migrate as Pipedrive Notes attached to the corresponding Person or Deal record. Rich-text formatting in Real Properties notes is preserved as HTML content in Pipedrive Notes. Notes without a linked record are attached to the Person if one exists.

Real Properties custom fields on Contact records create custom fields on Pipedrive Person objects. Field types (text, number, date, picklist, checkbox) are matched to Pipedrive's supported field types. Each custom field key is a 40-character hash in Pipedrive; FlitStack creates the field in Pipedrive before data writes begin.

Property-specific custom fields (listing_price, mls_number, property_type, bedrooms, bathrooms, square_footage, year_built) migrate as custom fields on the Pipedrive Deal created for each listing record. These must be pre-created in Pipedrive with the correct field type before migration.

Real Properties owner records are matched to Pipedrive users by email address as the primary key. Unmatched owners are flagged before migration begins — your team either creates Pipedrive user accounts for them or assigns their records to a fallback owner designated in advance. No record lands in Pipedrive without an assigned user, ensuring your Pipedrive account maintains proper accountability and assignment visibility from the moment migration completes.

Files attached to Real Properties contacts, companies, deals, or property listings are re-uploaded to Pipedrive as attachments on the equivalent record. File size limits apply (Pipedrive caps individual attachments at the plan's storage limit).

If your Real Properties setup maintains a separate Lead object distinct from Contact, those Lead records migrate as Pipedrive Leads. Pipedrive Leads exist as their own object type with a separate set of custom fields independent from the People object. FlitStack creates matching custom fields on the Lead object before migration runs, especially for property-related data that may be attached to Lead records. The Lead custom field hash keys are captured and used for all subsequent data writes to ensure field associations remain intact throughout the migration process.