Migrate from Property Shell to Pipedrive

Direct map. Property Shell contacts (buyer names, agent names, property manager contacts) migrate to Pipedrive People. Email, phone, address, and owner assignment carry over as direct field mappings. FlitStack's migration engine validates email format and uniqueness against Pipedrive's Person object requirements before inserting each record. Contacts without a valid email address format are flagged for manual review before migration commits — your admin confirms the correct contact record or supplies a valid email.

Direct map. Property Shell company records (real estate agencies, developer entities, law firms, property management companies) migrate to Pipedrive Organizations. Company name, domain/website, physical address, industry classification, employee count, and owner assignment map to their Pipedrive Organization equivalents as direct field mappings. Any custom fields present on Property Shell companies are inventoried during the schema audit phase and created as custom fields on the Pipedrive Organization object before the migration run.

Direct map. Property Shell's enquiry and lead records map to Pipedrive's Lead object. Lead status, source attribution, property interest, and any custom fields from Property Shell map to corresponding custom fields in Pipedrive. Pipedrive's Lead object is separate from Person — leads convert to People at the point of deal creation or through a manual conversion action in the Pipedrive UI.

Direct map. Property Shell deals (sale contracts, reservation agreements, off-the-plan purchase contracts) migrate to Pipedrive Deals. Deal title, monetary value, stage in pipeline, expected close date, assigned owner, and property association carry over as direct field mappings. Pipedrive Deals inherit all accessible custom fields from the parent Organization and Person records during migration. Deals without a valid owner assignment or without a linked property identifier are flagged for admin review before the migration run commits those records to Pipedrive.

Property Shell's Project object has no direct equivalent in Pipedrive's object model. Development context — including project name, development type (residential, commercial, mixed-use), and construction completion stage — migrates as text custom fields on Pipedrive Organizations and is mirrored on associated Deals for cross-reporting in Pipedrive Insights. This dual placement allows your Pipedrive admin to filter and segment reports by development across the full deal pipeline.

Property Shell units (lot number, street address, asking price, settlement date, floor level, unit type) map to custom fields on Pipedrive Deals. Each deal represents one unit or lot sale. Multi-unit contracts in Property Shell that were modelled as single records will need to be split into one Deal per unit — your FlitStack consultant confirms the splitting logic during the schema audit phase before the migration ETL run executes.

Direct map. Property Shell engagement records — call logs, email threads, meeting notes, and general notes — migrate as Pipedrive Activities attached to the relevant Person, Organization, or Deal record. Original timestamps (create date and time) and owner assignments are preserved during migration. FlitStack's migration engine maps the Property Shell activity type to the nearest Pipedrive activity_type value; unrecognized types are flagged for your Pipedrive admin to configure in Pipedrive Settings > Activity Types before migration runs.

Direct map. File attachments from Property Shell records — contract PDFs, floor plans, site images, legal documents — re-upload to Pipedrive Files and are linked to the corresponding Person, Organization, or Deal record via Pipedrive's file attachment API. Pipedrive enforces a 25MB per-file size limit; files exceeding this threshold are flagged in the pre-migration file inventory report for your team to handle separately before the migration run.

Owner resolution by email match. Property Shell owner IDs are resolved against Pipedrive user email addresses. Unmatched owners are flagged before migration — your team either invites them to Pipedrive or assigns their records to a nominated fallback owner. No record lands in Pipedrive without a valid user_id owner assignment.

Property Shell automations — including enquiry-to-inspection nurture sequences, stage-triggered email follow-ups, contract-sent alerts, and AI-powered lead scoring — do not have equivalents in Pipedrive that can receive them via automated migration. FlitStack exports the automation definitions as a structured reference document in JSON or spreadsheet format. Your Pipedrive admin uses this reference to rebuild each workflow using Pipedrive Automations (field-change and stage-change triggers) and Pipedrive Sequences (multi-step email nurture campaigns).

Property Shell's development-level reports — absorption rate by project, enquiry-to-contract conversion pipeline, settlement forecast, stock-on-hand dashboard — have no direct equivalent in Pipedrive's standard reporting module. The underlying data migrates fully, enabling your Pipedrive admin to rebuild reports using Pipedrive Insights with custom fields from Deals and Organizations. FlitStack delivers a report-mapping guide alongside the migration package, listing each Property Shell report and the recommended Pipedrive Insights configuration to replicate its output.