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.
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, this import happens automatically as part of your migration to VRTrust.
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.
Reviewing and Mapping Historical Accounts
Before historical statements can be imported, the accounts used on your old statements need to be mapped to your VRTrust chart of accounts. You'll be prompted to do this from Settings > Opening Balances, where you can open the Review Historical Statement Mappings step.
VRTrust automatically narrows the list to only the legacy accounts that were actually used on a posted statement line, so you won't need to map accounts that were never used.
For each legacy account, choose the matching VRTrust account from the target account dropdown. Only revenue and expense accounts are shown as options, since historical statement lines don't post to asset or liability accounts.
If a suggested match is offered, review it before accepting. Suggestions are a starting point, not a guarantee.
Submit the mapping to complete the import.
If your VRTrust team was created manually and linked to your VR Integrations account afterward (rather than through our standard migration flow), listings may not resolve automatically during mapping. If you don't see the mapping options you expect, contact our support team for help linking your legacy listings.
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.
Refreshing Historical Statements
If your account mappings change, or you need to re-pull historical statement data after a correction, use the Refresh Historical Statements option from the same Settings > Opening Balances area.
This reopens the mapping step: review your mappings again before resubmitting, since a refresh does not assume your previous mappings are still correct.
Troubleshooting
I don't see an option to migrate historical statements
This option appears automatically for teams that came through our standard VRPlatform-to-VRTrust migration flow. If your team was set up manually, or you're not seeing it after a migration, reach out to our support team and we'll get it connected.
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.