PHPackages                             byng/pimcore-doctrine-migrations-library - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Database & ORM](/categories/database)
4. /
5. byng/pimcore-doctrine-migrations-library

ActiveLibrary[Database & ORM](/categories/database)

byng/pimcore-doctrine-migrations-library
========================================

A library to add integration for Doctrine migrations in Pimcore.

v1.1.1(7y ago)11.2kMITPHPPHP >=5.4.0

Since Apr 26Pushed 7y ago2 watchersCompare

[ Source](https://github.com/byng-systems/pimcore-doctrine-migrations-library)[ Packagist](https://packagist.org/packages/byng/pimcore-doctrine-migrations-library)[ RSS](/packages/byng-pimcore-doctrine-migrations-library/feed)WikiDiscussions master Synced yesterday

READMEChangelog (2)Dependencies (1)Versions (4)Used By (0)

Pimcore Doctrine Migrations
===========================

[](#pimcore-doctrine-migrations)

In some Pimcore workflows you may find yourself repeatedly setting up the same content on several different environments (e.g. locally -> dev -> uat -> live). Doing this work manually is not only cumbersome, but it's also incredibly error prone. To alleviate this issue Byng decided to use Doctrine Migrations.

Using Doctrine Migrations you can automate database changes, and changes within Pimcore itself. For example; create pages, object, changing settings, etc.

Installation
------------

[](#installation)

Require the library via Composer (this library must be installed via Composer):

```
$ composer require byng/pimcore-doctrine-migrations-library

```

Then in your project's `composer.json` file add the following snippets:

```
{
    ...
    "config": {
        "project-root-path": "./"
    },
    ...
    "scripts": {
        "post-install-cmd": [
            "Byng\\Pimcore\\DoctrineMigrations\\Installer::install"
        ],
        "post-update-cmd": [
            "Byng\\Pimcore\\DoctrineMigrations\\Installer::install"
        ]
    }
    ...
}

```

The project root path is necessary so that the installer can create a migrations folder.

Note: The installation script will overwrite the migrations configuration files created in the project root. Changes to these files will be overwritten on composer install and update. We recommend placing them in your ignore file(s).

Usage
-----

[](#usage)

Once installed, you can simply use the library like you normally would with Doctrine Migrations. See [their documentation here](http://docs.doctrine-project.org/projects/doctrine-migrations/en/latest/).

License
-------

[](#license)

MIT

###  Health Score

29

—

LowBetter than 57% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity16

Limited adoption so far

Community11

Small or concentrated contributor base

Maturity60

Established project with proven stability

 Bus Factor1

Top contributor holds 80% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~440 days

Total

3

Last Release

2837d ago

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/2078024?v=4)[Byng](/maintainers/byng)[@byng](https://github.com/byng)

---

Top Contributors

[![seeruk](https://avatars.githubusercontent.com/u/2083033?v=4)](https://github.com/seeruk "seeruk (8 commits)")[![byng](https://avatars.githubusercontent.com/u/2078024?v=4)](https://github.com/byng "byng (1 commits)")[![nunojsferreira](https://avatars.githubusercontent.com/u/1738141?v=4)](https://github.com/nunojsferreira "nunojsferreira (1 commits)")

### Embed Badge

![Health badge](/badges/byng-pimcore-doctrine-migrations-library/health.svg)

```
[![Health](https://phpackages.com/badges/byng-pimcore-doctrine-migrations-library/health.svg)](https://phpackages.com/packages/byng-pimcore-doctrine-migrations-library)
```

###  Alternatives

[doctrine/doctrine-migrations-bundle

Symfony DoctrineMigrationsBundle

4.3k188.8M672](/packages/doctrine-doctrine-migrations-bundle)[sylius/sylius

E-Commerce platform for PHP, based on Symfony framework.

8.5k5.9M725](/packages/sylius-sylius)[patchlevel/event-sourcing

A lightweight but also all-inclusive event sourcing library with a focus on developer experience

207362.9k13](/packages/patchlevel-event-sourcing)[laravel-doctrine/migrations

Doctrine Migrations for Laravel

792.9M17](/packages/laravel-doctrine-migrations)[oat-sa/tao-core

TAO core extension

66143.7k119](/packages/oat-sa-tao-core)[sylius-labs/doctrine-migrations-extra-bundle

227.1M17](/packages/sylius-labs-doctrine-migrations-extra-bundle)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)