• Documentation >
• Guide >
• Repository >
• Data migration >
• Data migration

Data migration

Data migration allows exporting and importing selected data from an Ibexa DXP installation.

Exporting data consists in saving selected Repository information in YAML format. Importing reads migration YAML files and creates or modifies Repository content based on them. You can migrate your Repository data, that is Content items, as well as Content Types, languages, Object states, Sections, and so on, between installations.

You can use migrations in projects that require the same data to be present across multiple instances. They can be useful for project templates. Migrations are able to store shared data, so they can be applied for each new project you start, or incrementally upgrade older projects to your new standard, if needed. They are a developer-friendly tool that allows you to share data without writing code.

You can run data migrations either with a command, or with the PHP API.

Exporting data

Export Repository data to use in future data migrations.

Data migration actions

Data migration actions enable you to run special operations while executing data migrations, such as assigning Roles, Sections, Objects states, and so on.

Managing migrations

Manage data migrations by adding files, converting from Kaliop migration bundle, checking migration status, and setting up configuration.

Do not enable EzMigrationBundle2

If you are migrating your data either with kaliop-uk/ezmigrationbundle or ezsystems/ezmigrationbundle, do not install the tanoconsulting/ezmigrationbundle2 package, or your application will stop working due to multiple duplicated classes.

As of v3.3.3, the ezmigrationbundle package has been removed to mitigate this issue. It is recommended that you use the default ibexa/migrations package to migrate your data.