Migrate clients to VRTrust

Clients on the legacy VRPlatform product, also called VR Integrations, move to VRTrust as new teams. The fastest way is an AI assistant connected to the VRPlatform MCP, which runs the steps and asks before each change. See MCP setup.

The full sequence, from creating the VRTrust team to importing history, is in the legacy migration guide.

Historical owner statements

Past statements come along as read-only history in a separate ledger. They do not touch the general ledger, reports or trust reconciliation. Owners see them next to their new statements.

1. Map the accounts. Map each legacy account used on a statement line to a VRTrust account. VRTrust suggests matches. Review each one. A broad account such as owner expenses can be split by line description.
2. Map the listings. A legacy listing matches on its own when exactly one VRTrust listing shares its reference. Decide for every other listing.
3. Import. The import runs in the background and stops before writing anything when a mapping is missing.

Ask the assistant, for example:

Show me the historical statement account mappings for <team name>. List any accounts without a suggested match.

Historical statements cannot be paid or change status. Mappings are saved on the team, so a re-run starts from them. Review them before each re-run. For statement history from another system, see historic statements or contact support.

Tell your clients

Tell each client before the move: you set up VRTrust and migrate the data, and their owners get an invitation to the new owner portal. Owners log in with the same email and password. Point owners to For owners.