Overview
If you're an accounting partner, you can move a client team from VRIntegrations to VRTrust through an AI assistant, using the VRPlatform MCP connection, and you don't need to write any code .
The migration has four parts:
1. Create the VRT team. This copies listings, owners, connections, ownership periods and commission rates from the VRI team.
2. Map accounts. Each legacy VRI account gets matched to a VRT chart-of-accounts account.
3. Map listings. Each legacy listing gets matched to a VRT listing, or is kept as history only.
4. Import historical owner statements. Past statements land in a separate historical ledger, so owners keep their full history. Live GL accounting starts at the cutover date.
Cutover date: live GL starts on the first day of the month after the team's last published owner statement. You can request a later date, but never an earlier one.
Before you start:
Use your partner account. Your partner account must manage both the VRI team and the new VRT team. You can't migrate a team that another partner manages.
Select your partner team. With OAuth, tell the assistant which partner team you're working in, or set the team on the MCP connection. If you connect with a partner API key instead, the partner team comes from the key automatically.
Check your permissions. Creating the VRT team needs partner provisioning access. Mapping and importing statements need partner general-ledger access. (If you use an API key, it needs both the `partner:provisioning:v1` and `partner:general-ledger:v1` bundles.)
Publish the final VRI statement. The cutover is set by the last published owner statement. Make sure every statement you want carried over is published in VRI first.
Have these details ready: the VRI team's name, the name for the new VRT team, and your requested GL start date.
The assistant asks you to confirm before it makes any change. Read each summary before you approve it.
Migrate the team step by step
Run these steps in order, in a single conversation with your assistant. The prompts below are examples. Change the names and dates to fit your client.
Step 1: Create the VRT team
"Using VRPlatform MCP, migrate the VRI team **Mountain Papa** to a new VRT team called **Mountain Papa**, with a GL start date of **2025-01-01**. Don't move connection credentials."
The assistant creates the GL team and copies these from VRI:
- The team itself, its listings and its owners
- Its PMS and other connections. Credentials stay behind unless you ask to move them, so plan to reconnect.
- Ownership periods
- A chart of accounts, statement layouts and recurring fees from the default template
- Management commission rates, which become VRT fee drafts for you to review
When it's done, note the effective cutover date the assistant reports. It may be later than the date you asked for.
Step 2: Review account mappings
"Show me the account mappings for the Mountain Papa migration. List any accounts that don't have a suggested match."
The assistant lists every legacy account used on the statements you're importing, along with a suggested VRT account for each one.
- Suggested match: confirm it, or pick a different account.
- No suggestion: you must choose a target account. The import won't run until every account is mapped.
- Broad accounts such as "Owner Expenses": you can split these by line description. For example: "Send lines that mention *propane* to Utilities."
Step 3: Review listing mappings
"Show me the listing mappings for the Mountain Papa migration. Which listings need a decision from me?"
A listing is matched automatically only when exactly one VRT listing shares its unique reference. For every other listing, choose one of two options:
- Map it to a live VRT listing. Use this for re-listed properties: map every old listing to the property's current listing, even if the names differ. You can map several old listings to one current listing.
- Import it as history only. Use this for properties that have left. Their statements still import, but the listing stays inactive.
Step 4: Import historical statements
"Import the historical statements for Mountain Papa using the mappings we agreed on. Let me know when the job finishes."
The import runs in the background. Ask the assistant to check the job status until it reports completed or failed. If any mapping is missing, the job stops before it writes anything, so it's safe to fix the mapping and run it again. Your mappings are saved on the VRT team, so a rerun doesn't start from scratch.
Check the migration
Once the import completes, the VRT team's statement start date moves to the cutover, and VRT records the date of the historical import. Then work through this list:
Historical statements: open a few owners and confirm their past statements appear in the historical ledger.
Cutover: confirm live GL activity starts on the effective cutover date.
Connections: reconnect the PMS and any other integrations if you didn't move credentials.
Fees: review the management fee drafts converted from the VRI commission rates, then activate them.
Listings: check that history-only listings show as inactive, and that re-listed properties carry their full history.
Booking channels: spot-check that reservations show the right channel.
Known behaviors
Statement lines with a zero value don't need a mapping and don't create journal entries.
Historical reservations whose check-out date isn't after check-in import with zero nights and no check-out date.
Currency codes on imported statements display in lowercase, for example "usd".
FAQ and troubleshooting
Why is my cutover date later than the one I requested? Live GL can't start before the VRI team's last published statement. VRT moves it to the first day of the following month.
The import failed. Did it change anything? If a mapping was missing, no. The job checks every mapping before it writes any statements. Ask the assistant which account or listing is unmapped, fix it, and run the import again.
I already created the VRT team another way. Can I still import history? Yes. Ask the assistant to link the existing VRT team to the VRI team, then go to Step 2. The VRT team must have GL turned on, and both teams must be managed by you and be in the same data region.
Booking channels are missing on a team I migrated earlier. Ask the assistant to "backfill booking channels from the VRI team." This is safe to run more than once. It doesn't recreate the team or re-import statements.
I get a permissions error. Check that you're signed in as the partner that manages both teams, and that you selected the right partner team. If you use an API key, confirm it has both partner bundles listed under Before you start.
Need help? Contact VRPlatform support through the chat in the app.
Sources