Migrate from LockedOn to Pipedrive

LockedOn Contact name, email, phone, and address fields map directly to Pipedrive Person name, email, phone, and address fields. The primary company associated with the LockedOn contact maps to Pipedrive OrganizationId on the Person record, requiring the Organization to be migrated first. LockedOn contact owner resolves by email match to a Pipedrive user. Multi-address support in LockedOn collapses to Pipedrive's single address structure per Person.

LockedOn Company name maps to Pipedrive Organization name, and domain maps to Website. LockedOn industry pick-list and employee count have no direct Pipedrive equivalent — these migrate as Organization custom fields. Real estate agency-specific fields such as agent count, property count managed, and listing type specializations migrate as Organization custom fields and are surfaced in Pipedrive's organization detail view.

LockedOn Property has no Pipedrive equivalent. The Property address maps to Pipedrive Deal name — this is the most important field because Pipedrive deal lists are organized by deal name. List price maps to Deal amount. Listing type, property type, bedrooms, bathrooms, square footage, yard size, parking spaces, and year built all become Pipedrive custom fields on the Deal. The Property status (active, under contract, sold) maps to the appropriate Pipedrive deal stage through value mapping.

LockedOn listing pipeline stages (Active Listing, Under Offer, Under Contract, Conveyancing, Settled) map value-by-value to Pipedrive deal stages in the corresponding pipeline. Each stage maps individually with its order preserved. Stage probability percentages are not natively stored in LockedOn and are applied based on Pipedrive's default probability curve per stage unless custom probability mapping is specified.

LockedOn tasks, plan items, and triggers generate tasks with a subject, due date, linked contact, and linked property. These map to Pipedrive Activities with Type='Task', preserving the subject, due date, person association, and deal association. The trigger-based origin of a task (e.g., 'OFI follow-up triggered') is preserved as a note on the Activity since Pipedrive Activities do not natively store the trigger source.

LockedOn call logs record subject, date, duration, and outcome against a contact. These migrate as Pipedrive Activities with Type='Call', preserving the subject, start time, duration, and outcome. Call recordings attached to LockedOn call logs re-upload as Pipedrive file attachments linked to the Activity record.

LockedOn property inspections, open-for-inspection events, and meetings map to Pipedrive Activities with Type='Meeting'. The subject, start time, end time, and linked person and deal associations are preserved. Location and property address are carried into the Activity subject or description field.

LockedOn notes attached to contacts, companies, properties, or listings migrate to Pipedrive Notes. The note content, author, create date, and parent record link (person, organization, or deal) are preserved. Rich-text formatting in LockedOn notes is converted to Pipedrive's note body format.

Any LockedOn contact custom fields beyond the standard set (such as buying timeline, property budget range, or property interest type) require a corresponding Pipedrive Person custom field to be pre-created in Pipedrive before the migration runs. Pipedrive custom field keys are system-generated hashes, not the original LockedOn field names — a field mapping reference document is maintained so the correct Pipedrive field receives each value.

Property-specific fields such as listing type, property type, bedrooms, bathrooms, square footage, yard, parking, and year built require Pipedrive Deal custom fields. These must be created in Pipedrive before migration so field keys are available for mapping. The field types (text, integer, pick-list) match the source LockedOn field types to avoid type coercion issues during import.

LockedOn files attached to contacts, companies, properties, or listings are downloaded and re-uploaded to Pipedrive as file attachments linked to the parent record (Person, Organization, or Deal). Pipedrive enforces storage limits per plan tier — files exceeding the limit are flagged before migration and a storage plan upgrade is recommended if needed.

LockedOn contacts that have no associated company (e.g., a buyer who has not yet engaged an agency) receive a placeholder Organization named 'Unassigned' in Pipedrive so the Person.org_id foreign key is satisfied. A custom Person field (Original_Contact_ID__c) records the LockedOn contact ID for traceability and post-migration cleanup if a real organization association is identified later.

LockedOn's N:N contact-to-company association model allows one contact to have multiple agencies or companies. Pipedrive Person has a single primary OrganizationId. We migrate the most recently modified or most relevant company as the primary OrganizationId and create Pipedrive secondary Organization relationships for the remaining companies. The full list of associated companies is preserved in a custom Person field as a comma-separated reference.