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 Stripe settlement data, follow the Stripe deposit import guide.
- Preserve stable external identity and process item-level outcomes.
- Use dedicated import or migration workflows for existing history.
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.