Migrate from Funnel Leasing to Microsoft Dynamics 365 Sales

Funnel prospects with status 'Inquiry', 'Tour Scheduled', or 'Application Started' map directly to D365 Sales Leads. We preserve the original Funnel create date as Original_Create_Date__c since D365 sets CreatedDate at migration time. Owner resolved by email match against D365 users.

Prospects who have submitted an application or signed a lease transition to D365 Contacts linked to an Account representing the resident household or company. The primary email and phone map directly; additional contact details become custom fields on the Contact record.

D365 Sales has no native property object. We create a custom Property__c table in Dataverse with fields for property name, address (street, city, state, zip), property type, total units, and occupancy rate. The Property__c record is created before any Unit or Lease records referencing it.

Units map to a custom Unit__c table with a lookup to Property__c (Parent_Property__c). Fields include unit number, floor plan type, bedroom/bath count, square footage, market rent, and current status. Unit-to-property hierarchy is preserved through the Parent_Property__c lookup. Each unit record maintains a reference to its parent property, ensuring that queries and reports can aggregate data at the property level.

Active leases map to both an Opportunity record (for pipeline tracking) and a custom Lease__c table capturing rent amount, term start/end dates, security deposit, and renewal status. The Opportunity Name references the lease ID; Lease__c holds the contractual details. Closed leases migrate as historical records with status 'Won' or 'Closed Lost'.

Funnel's unified communication timeline splits across D365's activity types: email becomes email activity, phone calls become phonecall activities, in-person or video tours become appointment activities. Original timestamps, participants, and body content are preserved. The Regarding lookup links each activity to the corresponding Contact or Lead record.

Funnel tasks and follow-up items map directly to D365 Tasks. Subject, description, due date, priority, and status map one-to-one. Owner resolved by email match. Completed tasks preserve their completed date and actual completion time. This ensures that pending follow-ups are immediately actionable in Dynamics 365 Sales and that historical task completion records remain available for performance tracking and audit purposes.

Funnel file attachments (lease PDFs, ID scans, move-in photos) are downloaded and re-uploaded to a SharePoint document library connected to the corresponding D365 record via the SharePoint document location entity. File size limits (250MB per file in SharePoint Online) are respected.

Funnel team members map to D365 SystemUser records by email address lookup. Active and inactive status is preserved. Unmatched Funnel owners are flagged before migration — your admin either invites them to D365 or reassigns their records to a fallback owner.

Funnel's custom property attributes (e.g., amenities flags, building amenities, pet policy) map to custom fields on the Property__c Dataverse table. Field types are matched: boolean flags become Two Option fields, text values become Text fields, and pick-list values become Option Sets.

Funnel's AI-generated message suggestions and AI call summaries are system-generated outputs, not stored data records. They do not exist as queryable entities in Funnel's API and therefore cannot migrate. Teams should activate Dynamics 365 Sales Copilot post-migration to generate similar AI-assisted communication guidance.

Funnel workflows, automated routing rules, and sequence triggers do not have a D365 Sales equivalent and do not migrate. We export your Funnel workflow definitions as a reference document for your D365 admin to rebuild in Power Automate or Dynamics workflow designer post-migration.

Funnel's built-in leasing reports (tour conversion, application-to-lease rate, occupancy dashboards) do not migrate. The underlying data (prospect pipeline, lease activity, unit status) does transfer. Teams rebuild reports in Power BI using the migrated Dataverse tables as data sources. This approach allows operators to design custom visualizations that match their specific reporting needs and can be refreshed in real-time from the live D365 environment.