Integrate & Migrate Data
Integrate & Migrate Data
Establish connections, submit source data, and preserve history
Use this journey when your main job is establishing source identity and moving data into VRPlatform.
- Create or select the team.
- Create and operate a connection.
- Submit data through the product API batch endpoints. For settlement data, follow the source-specific deposit composition below.
- Preserve stable external identity and process item-level outcomes.
- Use dedicated import or migration workflows for existing history.
Deposit Compositions
Use the provider's actual settlement boundary. A payout ID, settled batch, statement descriptor, or disbursement date is not interchangeable with an individual guest charge.
| Source | Deposit boundary | Source data | Guide |
|---|---|---|---|
| Airbnb | Payout row | Payout CSV | Guide |
| Authorize.Net | Settled batch | Batch API | Guide |
| Booking.com | Payout or descriptor | Payout CSV | Guide |
| Braintree | Disbursement date | Transaction API | Guide |
| Lynbrook | Settlement ID | Settlement API | Guide |
| Stripe | Payout ID | Balance API | Guide |
| Vacation Rent Payment | Settlement ID | Report API | Guide |
For a provider not listed here, use Batch imports and compose the transaction from that provider's authoritative bank-settlement boundary. Generic payout and direct-deposit CSV importers are file transports, not additional settlement sources.
Historical work is deliberately separated:
- Historical statements preserve owner-facing statement history.
- Historical journal entries keep pre-go-live GL detail available.
- Opening trial balance establishes the combined balance immediately before go-live.
- PMS migration performs a source cutover.
- VRI migration moves a team off VRI — the legacy pre-general-ledger product generation — into the GL model.
Use Integration-sourced data for idempotency, batch outcomes, dry-run boundaries, and irreversible side effects.