Prepare a representative sample
An authorized organization owner or administrator manages migration in Settings → OPAS migration. Confirm the destination workspace, timezone, data permissions and migration scope first. Keep the original export. Use a small anonymized sample to review the format before submitting personal or confidential data.
The workspace accepts CSV/TSV tables for roster, productions, services and repertoire, or a JSON package in the supported shape. Download the sample JSON package to inspect that shape. Keep stable source IDs and the links between records. Other records in a JSON package need their own supported fields and validation; an arbitrary OPAS export is not automatically compatible.
Preview before writing
- Upload or paste the sample and run the dry run. This previews the plan without importing operational records.
- Review proposed creates, updates, duplicates, skipped rows and validation errors. Check names, email addresses, record links and service times against the source.
- Correct the source and run the plan again after changes. Resolve blocking errors before confirming an import.
This is an export-based migration workflow. It does not establish an OPAS connection, vendor endorsement or continuing synchronization.
Authorize and reconcile
A write import needs explicit confirmation and the current reviewed plan. Where required, an authorized owner or administrator must open a time-limited, single-use migration window with a reason and the displayed confirmation. Opening a window is a separate action from importing.
After import, inspect the batch history and counts, then check representative people, productions, services and permissions. Reconcile dates and times in the organization’s timezone before sign-off. Import completion does not prove invitation delivery or authorize sharing documents.
If something needs correction
Keep the batch reference and inspect the recorded outcome before retrying. Source IDs help match records, but a changed export can update existing data. Rollback is available for eligible batches and can report conflicts or a partial result when records have changed or gained dependencies. Resolve those with support; do not assume every import can be undone completely. Sign off only after reconciliation.
See roster import for a personnel-only CSV and migration planning for scope and billing. Contact support with the batch reference and visible error, without sending credentials or unrestricted source files.