Skip to main content

Database Migrations

Database migrations change durable workspace state and must be planned, validated, and verified carefully.

Operator Workflow​

  • Apply migrations only when the change requires schema or data movement.
  • Confirm the target environment before remote migration commands.
  • Verify affected API and app behavior after migration.

Verification Gates​

Verification gates: define the affected scope, run the relevant build or validation checks, perform the smallest appropriate deploy or config action, and verify the live user-facing or API behavior that changed.

For high-risk work, also prepare a rollback or follow-up plan before touching production.

Evidence To Capture​

  • Target environment and affected service, docs surface, API group, workspace, artifact, or operation.
  • Validation command or manual check performed.
  • Live route, API response, screenshot, or operation timeline proving the result.
  • Follow-up needed if verification is incomplete.

Media To Add​

  • Checklist table: migration scope, backup posture, validation, apply step, and post-check. It helps operators reduce migration risk. Source: database release process.