Agent Operating Guide
/bridge-auditboard-migrate
One-shot import of an AuditBoard tenant into Cowork Canvas, workpapers, issues, controls, audits, and remediation tasks, chunked, mapping-driven, and validation-gated.
Import an entire AuditBoard tenant into Canvas in one pass. The skill parses your AuditBoard export, applies the field mapping, validates every record against your Canvas schema, and submits the results as batched suggestions via suggest_change: nothing lands in your tenant until an admin approves. It chunks aggressively and never drops a record silently.
When to use
Section titled “When to use”When you’re moving off AuditBoard onto Canvas and need workpapers, issues, controls, audits, and remediation tasks brought over. Run the whole tenant at once, or a single scope at a time.
Inputs
Section titled “Inputs”| Flag | Required | Notes |
|---|---|---|
--source-export <path> |
Yes | The AuditBoard export folder or zip. |
--scope <set> |
No | all (default), or one of audits, issues, controls, workpapers for a partial migration. |
--chunk-size <n> |
No | Records per batch. Defaults to 500. |
--dry-run |
No | Validate mappings and report chunk counts without submitting. |
Example
Section titled “Example”/bridge-auditboard-migrate --source-export ./ab-export.zip --scope issues
parses the export, chunks the issues into batches of 500, validates each record
against the Canvas schema (via get_schema), and
submits them as suggest_change batches for bulk approval. Records that fail
validation are written to a per-record error log rather than dropped, and
re-running the same export skips anything already proposed. --dry-run
validates the mappings and reports chunk counts without submitting.
Good to know
Section titled “Good to know”- A migration produces suggestions in volume, so commit them through the Canvas bulk-approve flow rather than one at a time.
- It’s idempotent at the record level: each record carries its AuditBoard ID, so re-running the same export skips what’s already been proposed.
- Failed records are logged per record and retried with backoff: nothing is lost silently.
- A live progress artifact shows status as the migration runs.
Related
Section titled “Related”- /bridge-mapping-edit: configure the AuditBoard field mapping before you migrate.
- Items and item types: what the imported records become in Canvas.
- Builds on get_schema (validation) and suggest_change: the migration lands as proposals, not direct writes.