Migrate from PropFlo to Salesforce Sales Cloud

PropFlo stores both leads and customers in a unified contact model. FlitStack splits by PropFlo's contact type: 'Lead' type routes to Salesforce Lead; 'Customer' type routes to Salesforce Contact. Email, phone, and address fields map directly. Untyped contacts default to Lead for Salesforce.

PropFlo company records map directly to Salesforce Account. Company name, industry, website, phone, and billing address fields translate one-to-one. PropFlo's parent-company hierarchy maps to Salesforce ParentId lookup — the parent account must migrate first to prevent circular reference errors during loading.

PropFlo deals are unit-level bookings tied to a property. Each booking maps to one Salesforce Opportunity with unit details stored in custom fields (Unit_Number__c, Tower__c, Floor__c). For projects with multiple units, FlitStack creates separate Opportunities per booked unit and optionally links them via a Project custom object.

PropFlo property data (tower name, unit type, floor, facing, carpet area, rate per sq ft, total cost) requires either a custom Property__c object with a lookup from Opportunity, or custom fields on Opportunity. FlitStack recommends the custom object approach for projects with complex unit inventories and field-based storage for simple single-project setups.

PropFlo booking status values (Inquiry, Site Visit, Booking Confirmed, AOS Generated, Loan Under Processing, Registered) map to Salesforce Opportunity Stage pick-list values. Each stage requires probability and forecast category assignment. Stage-entry timestamps from PropFlo are preserved as custom datetime fields for audit trail continuity.

PropFlo cost sheet line items (base price, GST, parking, PLC, floor rise) map to Salesforce OpportunityLineItem records using a PriceBookEntry, or to custom decimal fields on Opportunity if a formal quote structure is not needed. FlitStack preserves unit rate and total amount as custom fields for reporting continuity.

PropFlo activity logs including site visit calls, follow-up tasks, and meetings map to Salesforce Task and Event records. Subject, description, due date, and ownerId resolve by email match. Original activity timestamps are preserved. Task Type distinguishes call, email, meeting, and site visit activity types.

PropFlo file attachments including AOS PDFs, payment receipts, and KYC documents re-upload to Salesforce Files (ContentDocument) linked to the corresponding Opportunity or Account record. File size limits apply — Salesforce Files cap at 25MB per file. Inline images embedded in PropFlo notes are extracted and re-hosted as Salesforce Files.

PropFlo owner assignments resolve to Salesforce User records by email address. Unmatched owners are flagged in the pre-flight report before migration — admin either provisions Salesforce user accounts or assigns records to a fallback user. Active or inactive status and role are preserved where available.

PropFlo custom properties (RERA number, possession date, parking slot, loan status, channel partner) migrate as Salesforce custom fields with __c suffix on the appropriate object. Field type mapping applies: text fields to Text(255), dates to Date, pick-lists to Picklist with value-by-value mapping.

PropFlo workflows for demand note approval, AOS generation triggers, and payment reminder schedules do not migrate to Salesforce. FlitStack exports workflow definitions as a JSON reference document for admin review. Rebuilding these automations in Salesforce Flow is scoped separately from the data migration engagement.

PropFlo reports and dashboards do not migrate — underlying data transfers but reporting configurations are destination-specific. FlitStack maps the record types and custom fields so reports can be rebuilt in Salesforce Reports & Dashboards post-migration with the same data structure.