Documentation map
migrate tracks database changes as ordered version files. Use the CLI in a deployment step, or embed the same migration service in a Go application.
Make your first migration
Start with the SQLite quick start to create, apply and reverse one SQL migration without running a database server. For an existing project, choose a build in Installation, then set up Configuration.
Work with a database
- Write SQL migrations: version names, Up/Down sections and statement blocks.
- Apply migrations: preview the plan, execute it and verify the result.
- Roll back migrations: retain a target version or reverse all applied versions.
- History and baseline: understand status, checksums and adopting an existing schema.
Go beyond SQL
Use JavaScript or TypeScript for transformations that need code. Shared modules, the database API, and transaction boundaries cover the runtime separately. The examples let you try local imports, npm packages and embedded files.
For application integration, see Use from Go. For databases behind a bastion, see SSH tunnels and proxies.
Look something up
- CLI reference: commands, arguments and flags.
- Supported databases: verification, placeholders and engine limits.
- Troubleshooting: configuration, history and execution failures.
- Release notes: behavior shipped in a specific release.
Version availability
This website follows main. Use migrate version and the release notes to check whether a feature is available in your installed binary.