Migrate from Funnel Leasing to Salesforce Sales Cloud

Funnel prospects map to Salesforce Leads — contact information, source channel, and renter profile fields migrate as custom fields on Lead. Funnel's renter lifecycle stages (Inquiry, Touring, Applied, Approved) map to a custom pick-list field in Salesforce since Salesforce has no native equivalent.

Prospects who have completed a lease application in Funnel and are active residents split to Salesforce Contacts, since the relationship has transitioned from a sales lead to an ongoing account relationship. A custom field flags the original Funnel prospect ID for reconciliation.

Funnel properties map to Salesforce Accounts using the property name as Account.Name. Funnel's property hierarchy (parent property / child property) maps to Salesforce ParentId on Account so the property portfolio structure is preserved. Address fields map directly to BillingAddress fields.

Funnel units do not have a Salesforce native equivalent. Units per property migrate as a custom Unit__c child object or as custom fields on the Account (e.g., Total_Units__c, Available_Units__c, Unit_Numbers__c). Availability status maps to a custom pick-list Availability_Status__c. If a child Unit__c object is used, each unit includes a lookup to the parent Account and fields for bedroom count, rent, and lease term, enabling per-unit reporting in Salesforce.

Funnel lease applications map to Salesforce Opportunities representing the deal to lease a specific unit. The Opportunity Name combines the renter name and unit number. Lease terms (start date, end date, monthly rent, security deposit) migrate as custom fields on Opportunity. A custom Lookup field links the Opportunity to the Account representing the property.

Funnel lease status values (Applied, Under Review, Approved, Denied, Executed) map to Salesforce Opportunity StageName values. A custom pick-list on the Opportunity captures the full Funnel status taxonomy, since the default Salesforce stage names do not cover the lease-approval lifecycle.

Funnel's omnichannel communication history maps to Salesforce Tasks (for emails and calls) and Events (for scheduled activities). A custom pick-list field Communication_Channel__c on Task captures the original channel (Email, SMS, Voice, Chat) since Salesforce Task.Type alone does not distinguish all four channels.

Funnel AI-generated message suggestions and call summaries have no Salesforce native equivalent. These migrate as a custom long-text field AI_Suggestions__c on the Lead and Contact for reference, but the content is not re-used in Salesforce AI features. Although the fields are static after migration, they preserve the AI insights for audit and analysis. Teams should plan to replace these with fresh AI outputs using Salesforce Flow and Einstein prompts post-migration.

Funnel team members who own prospects and leases resolve to Salesforce Users by email match. Unmatched owners are flagged before migration and assigned to a fallback user. Owner history is preserved as a custom text field Original_Owner_Email__c. The email match process is case-insensitive and handles domain aliases to increase resolution rates. FlitStack logs the match confidence for each record for audit purposes.

Funnel file attachments (lease documents, ID scans, application PDFs) re-upload to Salesforce Files and link to the appropriate record via ContentDocumentLink. File size limits apply: Salesforce Files default to 25MB per file; larger files require Salesforce CRM Content or external storage.

Funnel custom properties on prospects, properties, and leases migrate to Salesforce custom fields on the corresponding standard or custom object. Complex custom properties (structured objects with sub-fields) may require a Salesforce custom object with lookup relationships to the parent record.

Funnel's PMS integration status (synced from Blue Moon, ResMan, or AppFolio) has no Salesforce equivalent. The integration status migrates as a custom field Last_PMS_Sync__c and the sync source as a text field PMS_Source__c for manual reconciliation after migration. Post-migration, operators should rebuild the real-time sync using Salesforce's REST API, MuleSoft, or an AppExchange PMS connector to keep availability and lease data current.