Doctrine Migrations
doctrine-project.org
- Free plan
- Linux
- Self-hosted
What Doctrine Migrations is
Doctrine Migrations is a free, self-hosted PHP library for tracking database schema versions and deploying changes in a reviewable, testable way. Built on Doctrine DBAL and ORM, it can generate migration code by comparing a current schema with ORM mapping information, with documentation also covering diffing without the ORM. Its console application lets users inspect status, perform dry runs, execute one or more migrations, and revert them. Generated SQL can be written to a file with `--write-sql`, while `--no-interaction` supports unattended execution. Documentation covers transaction choices, including all-or-nothing behavior and running with or without transactions. Install it through Composer, which provides a `doctrine-migrations` command, or download a PHAR from GitHub releases. Integrations include Doctrine Migrations Bundle for Symfony and community options for Zend, Laravel, Silex, and Nette. Version 3.9.8 is marked stable, while 3.8 and earlier are unmaintained. The repository identifies an MIT license, and commands warn about possible data loss before proceeding.
Who it suits
PHP teams managing schema changes in self-hosted applications, especially those using Doctrine DBAL or ORM. It also suits projects needing reviewable migrations, dry runs, rollback, and scripted execution.
Good to know, and what to watch
- Free MIT-licensed PHP library
- Generates migrations through schema diffing
- Supports dry runs and migration rollback
- Can write SQL without executing it
- Offers transaction controls and unattended runs
- Schema changes may cause data loss
- Versions 3.8 and earlier are unmaintained
- Primarily focused on PHP persistence projects
- No hosted deployment option is listed
Plans
Every plan and priceDoctrine Migrations
Free plan
The verdict
Doctrine Migrations provides detailed console controls for versioning and deploying database changes. Its warning about potential data loss and the need to stay on a maintained release should shape deployment practices.
What the maker publishes
- Automation
- The `--no-interaction` option allows migrations to run without additional prompts. source
- Command line
- A Composer installation provides a doctrine-migrations console application in vendor/bin. source
- Current stable version
- The project page lists version 3.9.8 as stable. source
- Database abstraction
- The project is built on top of Doctrine DBAL and ORM functionality. source
- Database integration
- The project builds on Doctrine DBAL and ORM. source
- Documentation support
- The documentation directs users to the Doctrine mailing list, Slack migrations channel, GitHub bug reports, and Stack Overflow for help. source
- Execution controls
- The documentation covers dry runs, executing one or multiple migrations, reverting migrations, and non-interactive execution. source
- Framework integrations
- The integrations guide lists community-built integrations for Symfony, Zend, Laravel, Silex, and Nette. source
- Installation
- The library can be installed with Composer or downloaded as a PHAR from GitHub releases. source
- Install options
- It can be installed with Composer or downloaded as a PHAR from GitHub releases. source
- Intended users
- The Doctrine Project describes its libraries as PHP libraries focused primarily on persistence services and related functionality. source
- License
- The GitHub repository identifies the project as MIT licensed. source
- Migration controls
- Users can inspect migration status, run dry runs, execute migrations, and revert them from the console. source
- Purpose
- Doctrine Migrations adds database schema versioning and helps deploy database changes in a reviewable and testable way. source
- Purpose
- Doctrine Migrations adds database schema versioning and helps deploy schema changes. source
- Release status
- The project page marks version 3.9.8 as stable and versions 3.8 and earlier as unmaintained. source
- Review and testing
- The project says schema changes can be reviewed and tested before production deployment. source
- Risk note
- The migration command warns that schema changes can result in data loss and prompts for confirmation by default. source
- Schema comparison
- It can generate migrations by comparing the current database schema with mapping information defined through the ORM. source
- Schema diffing
- The documentation includes migration generation by diffing with the ORM or without the ORM. source
- Security reporting
- Doctrine asks security researchers to report issues privately by email rather than through GitHub's public issue tracker. source
- SQL output
- The `--write-sql` option can write generated migration SQL to a file instead of executing it directly against a database. source
- Support
- The documentation directs users to the Doctrine mailing list, Slack, GitHub bug reporting, and Stack Overflow for help. source
- Symfony bundle
- Doctrine lists Doctrine Migrations Bundle as a Symfony integration with its own Composer package. source
Checked against the maker's pages on 8 Oct 2026.