Converting migration files¶
If you want to convert a file from the format used by the
Kaliop migration bundle
to the current migration format, use the
The source file must use Kaliop mode and type combinations. The converter handles Kaliop types that are different from Ibexa types.
You can also convert multiple files using
If you do not specify the output folder, the command overwrites the input files.
Adding migration files¶
ibexa:migrations:import command to add files to the migration folder defined in configuration
Checking migration status¶
To check the status of migration files in the migration folder defined in configuration, run the following command:
The command lists the migration files and indicates which of them have already been migrated.
The default migration folder is
You can configure a different folder by using the following settings:
1 2 3
You can get default configuration along with option descriptions by executing the following command:
References are key-value pairs necessary when one migration depends on another.
Since some migrations generate object properties (like IDs) during their execution, which cannot be known in advance,
references provide migrations with the ability to use previously created object properties in further migrations.
They can be subsequently used by passing them in their desired place with
The example below creates a Content item of type "folder", and stores its Location path as
Then this reference is reused as part of a new role, as a limitation.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46
By default, reference files are located in a separate directory
(see previewing reference
Reference files are NOT loaded by default. A separate step (type: "reference", mode: "load", with filename as "value") is required. Similarly, saving a reference file is done using type: "reference", mode: "save" step, with filename.
1 2 3 4 5 6 7 8 9 10
You don't need to save references if they are used in the same migration file. References are stored in memory during migration, whether they are used or not.
Available reference types¶