# Workflow Automation & Integrations Art. 06 Automate # Your data moves. You don't. Deal terms flow from your CRM into the lease. Lease data flows from the document into your property management system. No copying. No pasting. No re-entering the same rent schedule into three different systems. [Schedule a Demo](/demo)[See All Capabilities](/product) Data flow S Salesforce CRM TenantTermRentDates L LeasePilot Drafting Draft TenantTermRentDates Y Yardi PM TenantTermRentDates ## Someone on your team is the integration layer. And they hate it. Here's how it works today. A deal closes. Someone prints the executed lease, or opens the PDF, and starts highlighting. Tenant name. Suite number. Commencement date. Base rent. Escalation schedule. Then they open Yardi. Or MRI. And they type it all in. Every field. Every number. It takes an hour. Sometimes two. And it has to be perfect, because if the rent schedule in Yardi doesn't match the executed lease, someone's going to find out. Maybe during an audit. Maybe when the tenant gets the wrong invoice. 1. 01 ### The data entry loop The same deal data, tenant name, rent, dates, entered once in the CRM, again in the drafting form, again in the PM system. Three chances to get it wrong. 2. 02 ### The island systems Your CRM knows about deals. Your PM system knows about properties. Neither knows what the other knows. You're the connection. 3. 03 ### The re-entry risk A transposed number in the rent schedule. A missed escalation date. The wrong pro-rata share. These errors sit in the system until someone finds them, during an audit, a refinancing, or a property sale. ## Deal data flows in. Lease data flows out. Nobody re-types anything. LeasePilot connects to the systems your team already uses. Data flows in at the start of a deal and flows out when the lease is finalized. The integration is built to match your setup, your systems, your data model. § 06.A ### Inbound: CRM to LeasePilot When a deal reaches the lease stage, your CRM pushes the deal terms directly into LeasePilot. Tenant name, property, premises, rent, term. The drafter opens the document and it's already populated. No data entry. - Salesforce, deal pipeline data - Microsoft Dynamics 365, enterprise CRM - Any system with an API via open SDK - Deal terms populated before drafting begins - Review and adjust, then start drafting § 06.B ### Outbound: LeasePilot to PM When the lease is finalized, the user changes the document status, and LeasePilot pushes structured data to the property management system. Tenant, premises, rent schedule, dates, options. In about 60 seconds. - Yardi Voyager, custom charge code mapping - MRI Software, official integration partner - Complete rent schedule, every period, every escalation - All dates, options, and operating expenses - Amendments use the same workflow ## Deal data flows in. Lease data flows out. Your CRM pushes deal terms into LeasePilot before drafting begins. When the lease is finalized, structured data pushes to your property management system. The same information, entered once. Connects to 1. 01Salesforce 2. 02Microsoft Dynamics 365 3. 03Yardi Voyager 4. 04MRI Software 5. 05Any system via open SDK Carries 1. 01Tenant and property data 2. 02Complete rent schedule 3. 03Dates and deadlines 4. 04Options and renewals 5. 05Operating expenses 6. 06Amendments No re-entry. No manual handoff. The rent roll matches the lease. Every time. ## It's not a connector. It's an open SDK. Manual re-entry ### Error-prone Someone prints the executed lease, highlights the key terms, and types them into Yardi. An hour of data entry. A transposed number in the rent schedule. A missed escalation date. These errors sit in the system until someone finds them. Preset connectors ### Rigid Most integration stories mean: we built one connector, it works one way, and if your setup doesn't match our assumptions, good luck. Your charge codes, your custom fields, your data model, they don't fit the template. LeasePilot ### Matches your setup Every integration is built using the same open SDK, a RESTful API any system can push to or pull from. The data mapping matches your configuration. Your charge codes in Yardi. Your opportunity fields in Salesforce. Your data model, not a generic template. 1. § 01 · Re-entry None Data that flows through the integration requires no manual re-entry. 2. § 02 · Latency 0s From status change to data push. On LeasePilot's side, near real-time. 3. § 03 · Workload 0% less Admin work on lease data movement. Internal estimate based on team knowledge. ## Deal closes at 4:30 PM. Data in Yardi by 4:32. Without integrations 1. 4:30 PM Signed lease arrives. Someone prints it and starts highlighting key terms. 2. 4:45 PM Open Yardi. Navigate to the property. Start entering tenant information. 3. 5:15 PM Enter the rent schedule year by year. Every period, every escalation. 4. 5:45 PM Enter options, restrictions, contacts. Double-check everything. 5. 6:15 PM Finally done. Hope nothing was transposed. 2 hours of data entry. Every time. With LeasePilot 1. 4:30 PM Lease is finalized. 2. 4:31 PM Status changed to “Final.” - Tenant and premises data pushed - Complete rent schedule exported - All dates and option deadlines - Operating expenses and pro-rata share 3. 4:32 PM Data in Yardi. Everyone goes home. Under 2 minutes. Nothing re-entered. ## See your data flow. We'll walk you through how LeasePilot connects to the systems your team already uses. Your CRM, your PM platform, your data model. [Schedule a Demo](/demo)