Migrate from Propertybase to Pipedrive

Propertybase Individual Contacts (SystemIsIndividual=TRUE, ghost company in background) map directly to Pipedrive People. The ghost company record that Propertybase creates to satisfy Salesforce's AccountId requirement does not generate a corresponding Pipedrive Organization — only explicitly linked Company Contacts do. Individual Contact create dates and owner assignments are preserved on the Pipedrive Person record.

Propertybase Company Contacts link to an actual Company record. Each Company Contact becomes a Pipedrive Person linked to a Pipedrive Organization via the Organization ID. Multiple Company Contacts sharing one Propertybase Company produce multiple Pipedrive People all pointing to the same Organization.

Propertybase Companies map directly to Pipedrive Organizations. Company name becomes Organization name; domain maps to website field. Parent/child company hierarchies in Propertybase map to Pipedrive Organization's parent organization field if available, or are flattened if the nesting depth exceeds Pipedrive's single-level parent model.

Propertybase Individual Listings have no Pipedrive equivalent — the listing address, price, status, type, and media links migrate as custom fields on the associated Pipedrive Deal. Pipedrive custom fields must be created in the Deal object before migration runs so the field keys (hash-based) are available for mapping. We preserve the original Listing ID as a custom field for traceability.

Propertybase Project Listings represent master developments with sub-listings. The project metadata (project name, stage, master project ID) migrates as custom fields on the Pipedrive Deal. Each sub-listing's individual property data (unit number, floor, price) also becomes custom fields on the associated Pipedrive Deal. No equivalent of Pipedrive's Product catalog exists natively in Propertybase, so no Product mapping is generated.

Propertybase Offers/Contracts reference both a Listing and a Contact. Since Pipedrive has no offer object, offer data (offer amount, status, purchaser name, offer date, closing conditions) migrates as custom fields on the Pipedrive Deal linked to that listing. When a single Propertybase listing has multiple offers, each offer generates a separate Pipedrive Deal sharing the same listing custom field values.

Propertybase Enquiries/Requests attached to a Contact migrate as a note or activity on the Pipedrive Person. Pipedrive does not have a native inquiry object, so the inquiry subject, source, and status are captured in a custom field on the Person record. Pipeline stage tracking for enquiries requires a separate Pipedrive Deal if the enquiry converts to an active transaction.

Propertybase users are matched to Pipedrive users by email address. Unmatched owners are flagged before migration so your team can create the Pipedrive user first or assign their records to a fallback owner. Active vs. inactive user status is preserved as a Pipedrive user-active flag — inactive Propertybase users are not invited to Pipedrive unless your team specifies otherwise.

Propertybase activities map to Pipedrive Activities with type differentiation: calls become Activity type 'call', emails become 'email', and meetings become 'meeting'. Original timestamps, subject, and duration are preserved. Propertybase notes map to Pipedrive Notes attached to the associated Person, Organization, or Deal. The Salesforce ActivityRelation model (multiple contacts on one task) maps to Pipedrive's activity-person linkage.

Propertybase Favorites link Contacts to Listings. Pipedrive has no favorite construct — these associations migrate as Deal-Person linkages via the Pipedrive deal_id + person_id association endpoint. Multiple contacts with favorites on the same listing generate multiple Deal-Person links under the same Pipedrive Deal representing that listing.

Propertybase listing images and documents managed in Media Loader have no native equivalent in Pipedrive. We re-upload images as note attachments on the Pipedrive Deal where supported, or store the original Propertybase media URL as a custom field for reference. If Propertybase media is stored externally, we preserve the URL rather than re-hosting. Media Loader metadata (caption, order) is not migrated.

Propertybase custom Salesforce objects (real estate extensions) have no Pipedrive equivalent. Each custom object's fields are mapped to custom fields on the most appropriate Pipedrive entity — typically Deal for transactional custom data or Person for contact-level extensions. Lookup relationships in Propertybase custom objects that reference other custom objects become text fields in Pipedrive storing the related record ID.

Propertybase workflows, Process Builder flows, validation rules, and assignment rules do not have a migration path to Pipedrive. Pipedrive Automations operate on a different trigger model. We export your Propertybase workflow definitions as a structured JSON reference document listing trigger objects, criteria, and actions so your Pipedrive admin can rebuild equivalent automations using Pipedrive Automations or Sequences.