Migrate from LeadManaging to Salesforce Sales Cloud

LeadManaging leads map 1:1 to Salesforce Leads for prospects still in the qualification pipeline. Core fields (name, email, phone, status, source) map directly. Salesforce Lead records require a Status pick-list value — FlitStack AI maps LeadManaging lead_status values to Salesforce Lead Status values or flags unmapped statuses for manual review before migration runs.

When a LeadManaging lead reaches 'Lease Signed' status, the record converts to a Salesforce Contact with a link to the corresponding Account (property). The original Lead record is preserved with Original_Lead_ID__c for audit traceability. This conversion rule is configurable — your team specifies the status threshold for Contact vs. Lead routing before migration begins.

LeadManaging properties map to Salesforce Account records. The Account Name holds the property name, Website maps from the property's web presence, and industry is set to 'Real Estate' by default. LeadManaging's property hierarchy (parent property / child building) maps to Salesforce Account.ParentId for orgs with multi-building portfolios.

LeadManaging units within a property require a mapping decision: either as a custom Units__c field on the Account (for simple count/rent tracking) or as a separate Unit__c custom object with a lookup to Account if detailed unit-level fields (bed/bath, floor, rent, vacancy status) need to be preserved. FlitStack surfaces this choice during discovery and delivers both options in the migration plan.

LeadManaging's lead_status pick-list values (New, Contacted, Qualified, Lease Signed, Lost) map to Salesforce Lead Status values. Each Salesforce Sales Process has its own Status pick-list — if your org uses multiple Sales Processes or Record Types, value mapping is scoped per process. Unmapped values are flagged and must be resolved in Salesforce Setup before the migration validates.

LeadManaging's lead_source field (Organic, Paid Search, Referral, Walk-in, and any other custom values) maps to Salesforce Lead.LeadSource pick-list. When LeadManaging contains custom source values that don't exist in Salesforce's defaults, each requires explicit value-by-value mapping to either an existing pick-list option or a custom Lead_Source_Detail__c field to preserve all attribution data without truncation. The chosen approach is documented in the mapping spreadsheet and confirmed before migration execution.

LeadManaging call logs, emails, and notes map to Salesforce Task records with Type='Call', Type='Email', or Type='Other' respectively. FlitStack AI preserves the original subject line, description body, activity date, and owner by mapping to Task.Subject, Task.Description, Task.ActivityDate, and Task.OwnerId. Tasks are linked to the Salesforce Lead or Contact via WhoId.

LeadManaging property tour records map to Salesforce Event with Subject='Property Tour', StartDateTime, EndDateTime, and Location preserved. FlitStack AI maps the event description to Event.Description and links the Event to the Salesforce Lead or Contact via WhoId. All-day events in LeadManaging become Salesforce Events with All-Day Event=true.

LeadManaging file attachments (lease applications, ID scans, property photos) are downloaded and re-uploaded to Salesforce Files (ContentDocument/ContentVersion model). Files are linked to the relevant Salesforce Lead, Contact, or Account record via ContentDocumentLink. Salesforce's 25MB per-file limit is enforced — files exceeding this are flagged for manual handling.

LeadManaging's assigned leasing agent resolves to a Salesforce User by email match. Unmatched owners (agents who will not have Salesforce licenses) are flagged before migration — your team either creates their Salesforce User record first or reassigns their leads to a fallback owner. No record lands without a valid OwnerId.

LeadManaging custom fields on Lead records (e.g., 'Move-in Date', 'Lease End Date', 'Bedroom Preference', 'Budget Range') map to Salesforce custom fields using the __c suffix convention. FlitStack AI creates the field in Salesforce Setup, applies the correct data type (Date, Number, Text), and maps values during migration. Custom field count is the primary driver of migration complexity.

LeadManaging workflow rules, email sequences, and task-assignment automations do not have a Salesforce equivalent because the execution engine is architecturally different. FlitStack AI exports your LeadManaging automation definitions as a structured JSON reference document your Salesforce admin uses to rebuild equivalent Flows after go-live. This is always a manual step — we surface exactly what was configured so nothing is silently dropped.