Migrate from PropFlo to Pipedrive

PropFlo Leads map 1:1 to Pipedrive People. All standard Lead fields (name, email, phone, address) map to corresponding Pipedrive Person fields. PropFlo's lead_score, lead_status, and lead_source migrate as Pipedrive custom fields since Pipedrive has no native scoring field. FlitStack AI pre-creates these custom fields using Pipedrive's hash-key mechanism, preserves created_at timestamps and owner assignments, and validates the mapping during the sample migration step to ensure integrity before dataset is loaded.

PropFlo Company Contacts map to Pipedrive People. Each contact's primary PropFlo company becomes the Pipedrive Person's Organization link. Contacts with no primary company land as standalone Pipedrive People. FlitStack AI matches the primary company to the corresponding Pipedrive Organization, preserving custom fields and ownership details, and runs duplicate detection to avoid re-creating contacts that already exist in Pipedrive.

PropFlo Companies map to Pipedrive Organizations. Company name, website, industry, employee count, and annual revenue map to corresponding Organization fields. PropFlo company hierarchy (parent/child) maps to Pipedrive Organization parent_id. FlitStack AI also maps PropFlo's custom fields such as company_type to Pipedrive custom fields, and validates the hierarchy during the sample migration to ensure the parent/child structure is reproduced accurately in Pipedrive.

PropFlo Deals map 1:1 to Pipedrive Deals. Deal name, value, stage, expected_close_date, and owner map to Pipedrive Deal fields. PropFlo deal pipeline maps to Pipedrive Pipeline; PropFlo deal stage values map to Pipedrive Stage values per pipeline. FlitStack AI also maps PropFlo custom fields such as asking_price to Pipedrive custom fields on Deal, preserves created_at timestamps, and resolves owners to Pipedrive users by email to ensure ownership during migration runs.

PropFlo call activities migrate as Pipedrive Activities with type=Call. Original timestamp, duration, call notes, and owner preserved. Linked Person or Deal association preserved via Pipedrive's activity sub-resources. FlitStack AI maps the call duration and notes to the appropriate Pipedrive activity fields, pre-creates any custom fields needed for call metadata, and validates that the Person or Deal link is correctly established using Pipedrive's sub-resources API during the migration.

PropFlo meetings migrate as Pipedrive Activities with type=Meeting. Start/end times, location, agenda notes, and attendees (linked People) preserved. Recurring meeting series are not natively supported in Pipedrive and are imported as individual activity records. FlitStack AI transfers meeting details including start/end times, location, agenda, and attendee links, pre-creates custom fields for any meeting-specific metadata, and handles recurring series by creating individual activity records to match Pipedrive's structure.

PropFlo email activities migrate as Pipedrive Activities with type=Email. Subject, body content, direction (sent/received), timestamp, and linked Person or Deal preserved. Full email threading preserved via activity sub-resource links where available. FlitStack AI transfers the email subject, body, direction, and timestamp, pre-creates any custom fields for email-specific metadata, and ensures the thread link to the Person or Deal is correctly set using Pipedrive's activity sub-resources during migration.

PropFlo notes migrate as Pipedrive Notes. Original note content, create timestamp, and owner preserved. Notes attached to a specific PropFlo entity (Lead, Contact, Deal) are linked to the corresponding Pipedrive Person or Deal during migration. FlitStack AI also maps any note-specific custom fields, verifies that the note's owner matches the corresponding Pipedrive user, and retains the original creation timestamp as a custom field to preserve audit history.

PropFlo Projects have no Pipedrive equivalent. We migrate Project name, project_status, and project_type as custom fields on the Pipedrive Organization representing the developer/client. Project-level data is preserved for manual segmentation in Pipedrive. FlitStack AI pre-creates project custom fields in Pipedrive, maps each project's name, status, and type to the fields on the Organization, and validates the mapping during the sample migration to ensure project data is accurately represented for segmentation and reporting.

PropFlo Units (properties within a Project) have no Pipedrive native equivalent. Unit details — unit_number, floor, bedrooms, area_sqft, facing, unit_type, status — migrate as custom fields on the parent Organization or as a structured Note attachment. Your Pipedrive admin chooses the preferred display approach.

PropFlo Property records (asking_price, property_type, listing_type, days_on_market) map to Pipedrive custom fields on Organization or Deal depending on where the property context is stored in PropFlo. FlitStack AI creates the custom fields for asking_price, property_type, listing_type, and days_on_market in Pipedrive, maps them to the appropriate Organization or Deal based on the source context, and runs a diff during the sample migration to confirm accuracy before import.

PropFlo assignment rules (auto-assigning leads to agents by territory or property) do not migrate. We export the rule definitions as a reference document your Pipedrive admin uses to rebuild them as Pipedrive Automations triggered by Lead creation or field-change events.

PropFlo workflows including AOS generation, demand note approval flows, and chatbot automation have no Pipedrive equivalent. We export workflow definitions as a rebuild reference for Pipedrive Automations (triggers and actions) or Pipedrive Sequences (email drip with tasks). FlitStack AI captures each workflow's trigger events, conditions, actions, and approvers in a structured format, enabling your Pipedrive admin to rebuild the logic as Pipedrive Automations or Sequences with minimal manual effort.

PropFlo file attachments (AOS PDFs, demand notes, property brochures) re-upload to Pipedrive as file attachments on the linked Person, Organization, or Deal. File size limits per Pipedrive plan apply; large files are chunked or linked via URL reference. FlitStack AI copies each file's metadata (filename, creation date) and uploads it via Pipedrive's API, splitting any file that exceeds the plan limit into chunks or storing a URL link for accessibility.