When migrating from VRPlatform (VR Integrations) to VRTrust, past owner statements come along as read-only historical records. This gives owners a continuous statement history in one place, even though your live accounting now runs entirely in VRTrust.
Who this applies to: Teams that migrated (or are migrating) from VRPlatform / VR Integrations to VRTrust and have owner statement history from before the cutover date.
If you are looking for help importing historical owner statements from outside of VRPlatform through our API, refer to this help doc.
What "Historical Statements" Means in VRTrust
Historical statements live in a separate Historical ledger inside VRTrust. This ledger is non-posting — it does not affect your live financial reports, trust reconciliation, or general ledger. Its only purpose is to feed your Owner Statement Summary history, so owners and your team can see statement activity from before your VRTrust start date without it touching current-period accounting.
Historical statement data can come from two sources:
VR Integrations (VRI): for teams migrating from our legacy VRPlatform product, statements are imported as the final step of the VRI-to-VRTrust migration, run through the VRPlatform MCP or API.
Other sources (CSV/manual import): if your prior statement history comes from a different PMS or a spreadsheet rather than VR Integrations, our team can help import it. Reach out to support to see if this applies to your team.
How the Import Works
Accounting partners run the import by asking an AI assistant (such as Claude) connected to the VRPlatform MCP. The assistant handles the API calls and asks you to confirm before it makes any change. For full step-by-step instructions and example prompts, see Migrating a Team to VRTrust Using the MCP. API users can follow the Legacy (VRI) Migration Guide.
Before you start: the VRTrust team must already be created from (or linked to) the VRI team, and your partner account needs general-ledger access.
1. Review account mappings
The accounts used on your old statements need to be mapped to your VRTrust chart of accounts.
Only legacy accounts that were actually used on a statement line need mapping. Lines with a zero value are skipped.
VRTrust suggests a matching account where it can. Suggestions are a starting point, not a guarantee, so review each one. Accounts with no suggestion need you to choose one; the import won't run until every account is mapped.
Broad legacy accounts such as "Owner Expenses" can be split by line description, for example sending lines that mention propane to Utilities.
"Show me the historical statement account mappings for [team name]. List any accounts that don't have a suggested match."
2. Review listing mappings
A legacy listing is matched automatically only when exactly one VRTrust listing shares its unique reference. For every other listing, either map it to a live VRTrust listing (useful for re-listed properties) or import it as history only (for properties that have left).
"Show me the listing mappings for [team name]. Which listings need a decision from me?"
3. Import the statements
Once mappings are confirmed, the import runs in the background. Ask the assistant to check the job until it reports completed or failed. If a mapping is missing, the job stops before writing anything.
"Import the historical statements for [team name] using the mappings we agreed on. Let me know when the job finishes."
What Historical Statements Look Like After Import
Historical statements appear in your owner statement list and detail views alongside your live VRTrust statements, and can be filtered by month and year like any other statement.
They are frozen: no payouts can be created from a historical statement, and its status can't be changed. They exist as a record of the past, not as an editable account.
Owners can see historical statements in the owner portal alongside their current VRTrust statements, so their statement history stays continuous through the transition.
Re-running the Import
If account mappings change, or historical statement data needs to be re-pulled after a correction, re-run the import through the MCP or API.
Your mappings are saved on the VRTrust team, so a re-run doesn't start from scratch.
Review the saved mappings again before importing. A re-run does not assume your previous mappings are still correct.
"Show me the saved historical statement mappings for [team name]. Change [legacy account] to map to [VRTrust account], then re-run the import."
Troubleshooting
I don't see an option to migrate historical statements
Historical statements are imported through the VRPlatform MCP or API, not from the VRTrust app. Ask your accounting partner, or contact our support team if you don't work with one.
Listings aren't matching
This usually happens when the VRTrust team was created manually and linked to the VR Integrations team afterward. Map those listings explicitly during the listing mapping step, or contact our support team for help.
An account won't map, or the numbers don't look right
Contact our support team with the account or statement in question. Our team can help resolve account mapping issues or investigate discrepancies between your legacy and VRTrust statements.