This document should be able to answer the following questions:
-
Which data fields/tables we pull and when
-
Which data fields we push and when
-
Triggers in LeadManaging (LM) that initiate data transfer to Property Vista (PV)
-
Triggers in Property Vista (PV) that initiate data transfer to LeadManaging (LM)
-
Triggers in PV that initiate the data push to Yardi
Export
-
LM pushes guest cards to PV
-
Frequency and timing:
-
Within 5 minutes after manually pushing a guest card
-
-
PV pushes Approved Lease Application details to Yardi in Real time
Workflow: Export/Push Guest Card From LM to PV:
Workflow pdf:
In order to successfully push a guest card into PV, the following fields within LM should always be filled out:
-
First name (Mandatory)
-
Last name (Optional)
-
Phone Number or Email Address
-
Bedroom Type
-
Move-In Date
Once the fields are correctly filled out, you will then be able to push the guest card to PV by processing an event under the Event History section of your guest card:
Important to Note: Appointment events cannot be used to push a guest card to PV.
Within the “Quick Event Update” window, please ensure to select “Application” in the “Contact Stage” field and “Applied” in the “Result” field because that is the only stage and result that will allow you to successfully push to PV. Once all the other fields reflect the appropriate information, please click save:
Import
-
Existing feature: LM pulls Yardi information
-
Limitation: LM does not pull Guest Card information from Property Vista as of this time. The information reflected comes from Yardi.
-
Prerequisite: LM does not pull Guest Cards from Yardi if they do not have at least 1 form of contact information (email or phone number).
-
Frequency and Timing:
-
Every 30 mins - Customer Details (New Leads and updating status of leads)
-
12 pm and 12 am Eastern - Property Information (units, bedroom types, building, etc.), Ad Sources, and Agent Information
-
Note: If a lead comes in and the building has not been synced from Yardi, the lead will not be processed until we pull the building information from Yardi (at 12 pm or 12 am).
-
-
PV to Yardi Export:
Once a Lead is imported into PV CRM, to proceed further the Agent information will need to be filled out as this does not get imported from LM. After this step, the user can convert this Lead into a Lease Application
After the Lead is converted into an Application it will be displayed in the Lease Applications lister. From here, the User can take one of the following steps to proceed;
-
Click on Actions – Online Application – Start
-
Click on Actions – Submit Application by filling in the reason – Complete – Approve Application
Once this Application is approved it will be moved into the Lease Lister in PV and will be updated real time in Yardi. Important Note: Yardi to PV sync does not happen real time and any updates will move into PV only after the nightly sync.
LeadManaging and Yardi Integration
|
Category |
Fields in Yardi (non-customer facing) |
Fields in LM (UI) |
Notes |
|---|
|
Category |
Fields in Yardi (non-customer facing) |
Fields in LM (UI) |
Notes |
|---|---|---|---|
|
Unit |
Unit ID |
Unit (DB) → Building (UI) |
Unit ID in Yardi is mapped to LM DB as Unit and LM UI as Building. |
|
Bedroom Type |
Unit ID with Bedroom Type |
Description of the Unit (Bedroom Type) ex: 1 Bedroom with balcony (1 bdrm) |
|
|
Date/Time |
Event Date |
Date/Time |
First Contact event date and time |
|
Contact Info |
Customer P-Code (non-customer facing)
|
Contact
|
If Phone Number OR Email Address do not match - LM creates a new contact then later on merges the contact. |
|
Target Move-in Date |
Target Move-in Date |
Move-in Date |
Before the prospect’s application |
|
Expected Move-in Date |
Expected Move-in Date |
N/A |
For an existing guest card in LM, once the status changes to Leased in Yardi, LM will update the status of the Guest Card to Leased and reflect the expected move-in date in LM. |
|
Lease from |
Lease from |
N/A |
Not a lead that is created in LM. |
|
Lease to |
Lease to |
N/A |
Not a lead that is created in LM. |
|
Desired Floor Plan |
Desired Floor Plan |
N/A |
Not a lead that is created in LM. |
|
Desired Unit (UnitID) |
Desired Unit (UnitID) |
Unit |
|
|
Desired Rent Value |
Desired Rent Value |
N/A |
Not a lead that is created in LM. |
|
Comment |
Comment |
Remarks |
|
|
Agent Info |
Agent (FirstName LastName) |
Agent Name (FirstName LastName) |
In case LM does not have a match from Yardi, LM uses a Default Agent. |
|
Event Type |
Event Type |
Event Type and Lead Type |
|
|
|
|
||
|
Walk-in |
Walk-in |
||
|
Call to Prospect |
Call Event |
||
|
Call from Prospect |
|||
|
Other |
|||
|
Contact Stage |
Event Types
|
Contact Stage:
|
Yardi does not send LM Guest Card statuses. LM updates Guest Card statuses from Yardi Event Types.
|
|
Ad Source |
Transaction Source
|
Media Source or Originating Source |
If the source is not mapped between Yardi and LM, LM will show this source as “No Media Found.” We need to make sure that the source is listed in both LM and Yardi to reflect accurate information. [Future enhancement: categorized mapping ex: source is not exactly mapped with LM, this will be moved to a generic media source] |
|
Unit Availability |
Occupancy > Status
|
Available:
|
This is not included in the Guest Card but can be found on LM > Settings > Availability. |
|
Price |
Unit Rent |
Price (no specific currency, just numbers) |
This is not included in the Guest Card but can be found on LM > Settings > Availability. |