Map Yardi and MRI CAM data
Use exports for context. Keep signed files as proof.
Build one neutral file map for either vendor. Then test stable keys.
Do not promise a CAMAudit connector. The client controls each export.
Yardi Smart Lease writes checked lease fields into Voyager. Its page also requires user review and approval.
MRI ProLease covers lease records, dates, duties, and work steps. Available fields depend on the client's setup.
Start with neutral keys
Map each vendor record to shared keys.
OSCRE provides common real estate entities. Use that idea for a vendor-neutral file contract.
Keep these keys on every row:
| Key | Plain meaning |
|---|---|
| Property key | One site or property |
| Tenant key | One lease party |
| Suite key | One leased area |
| Lease key | One signed lease record |
| Statement key | One CAM bill year |
| Source key | Original vendor record |
Do not create keys from names alone. Names can change or repeat.
Store the source key beside your shared key. That makes a replay possible.
Export context fields
Ask the client which fields its tools can export.
The neutral contract can request these groups:
| Group | Candidate fields |
|---|---|
| Property | Key, name, address |
| Tenant | Key, legal name |
| Lease | Key, start date, end date |
| Space | Suite key, area field |
| Charge | Account, date, amount |
| Statement | Year, source record key |
| Status | Active flag, export time |
Your file plan requests these fields. Vendors may differ. Check each live export.
Do not infer an absent field. Mark it missing.
Keep source files outside exports
The CAM review still needs signed source files.
Keep these documents with the packet:
- Signed lease
- Signed lease changes
- Landlord CAM statement
- Charge support supplied for review
- Prior statement when the lease test needs it
An export can point to a file. It does not replace the file text.
A lease date field may aid intake. The signed page still controls review.
A charge total may aid a tie out. The landlord bill shows the billed lines.
Record every field change
Many exports reshape values. Write those changes down.
Use a map with these columns:
source_system,source_field,source_key,target_field
change_rule,null_rule,owner,checked_date
Do not hide a combined field. Name how it was split.
Do not change currency, dates, or signs without a rule. Keep the old value.
The client system owner approves source changes. Your firm can flag a conflict.
Give each row a state
Use clear row states before full transfer.
| State | Meaning | Next step |
|---|---|---|
| Checked | Keys and source agree | Keep row |
| Missing | Needed field is blank | Ask owner |
| Conflict | Sources disagree | Hold row |
| Changed | A stated rule altered value | Review rule |
| Rejected | Row does not fit scope | Record reason |
Do not call every imported row clean. A loaded row may still be wrong.
JLL's CRE tech guide calls scale complex. The page explains how to organize for successful scaling.
This guide proposes these handoff states.
Test ten rows first
Choose ten rows from each available export.
The number is a test design choice. It is not a quality claim.
For each row, check:
- Property key
- Tenant key
- Lease key
- Statement year
- Source record key
- Linked source files
Stop if keys drift. Fix the map before adding more rows.
Also test a blank field and a conflict. A happy path is not enough.
Walk one sample handoff
This fictional sample uses made-up names.
Assume Cedar Tech serves West Bay Shops. The client exports a lease table.
| Field | Export value | Source check | State |
|---|---|---|---|
| Property key | WB-14 | Matches bill | Checked |
| Tenant key | T-882 | Matches lease | Checked |
| Lease key | L-301 | Matches lease | Checked |
| Statement year | 2025 | Matches bill | Checked |
| Suite area | Blank | Lease has value | Missing |
The missing area stops any area-based test. The source owner fixes the handoff.
The sample assumes no connector. It predicts no result.
Prove the handoff
Keep a small proof packet after testing.
It should include the export file and field map. Add row states and source links.
Also record the export time and client owner. Keep the original file unchanged.
Another reviewer must be able to replay your handoff.
A clean file load proves too little.
Link the broader work
The PropTech firm pillar starts with the full offer. The tech consultant hub adds related system guides.
Map every lane with the system handoff guide. Send failed rows to the exception queue guide.
The PropTech ROI guide sets later proof stages. The Practice Growth hub lists more firm paths.
Where CAMAudit fits
Proptech consultants can add this review to the proof packet.
The proof packet stays with the client system owner. CAMAudit needs document copies, not a live vendor link.
Send neutral keys with the chosen lease and CAM files. Fixed math checks may identify cited items.
Your firm checks those items. It selects entries for the branded CAM audit. Your firm reviews and signs the final audit.
The firm then sends that audit. Client staff keep all export fixes.
An approved item may lead to a dispute letter draft. CAMAudit can prepare the draft.
The draft is not legal advice. Your firm reviews it.
Have counsel review before sending.
Use the service line guide to name the next owner.
Ready to add this work to your firm? Get started.