Skip to main content
Version: 8.8 (unreleased)

Configuration property reference

Reference for all Data Migrator configuration properties, set in the configuration/application.yml file.

camunda.client

Prefix: camunda.client

info

Read more about Camunda Client configuration options.

PropertyTypeDescription
.modestringOperation mode of the Camunda 8 client. Options: self-managed or cloud. Default: self-managed
.grpc-addressstringThe gRPC API endpoint for Camunda 8 Platform. Default: http://localhost:26500
.rest-addressstringThe REST API endpoint for Camunda 8 Platform. Default: http://localhost:8088

camunda.migrator

Prefix: camunda.migrator

PropertyTypeDescription
.page-sizenumberNumber of records to process in each page. Default: 100
.job-typestringJob type for actual job activation. Default: migrator.
.validation-job-typestringJob type for validation purposes. Optional: falls back to job-type if not defined. Set to DISABLED to disable job type execution listener validation entirely.
.auto-ddlbooleanAutomatically create/update migrator database schema. Default: false
.table-prefixstringOptional prefix for migrator database tables. Default: (empty)
.data-sourcestringChoose if the migrator schema is created in the C7 or C8 data source. Default: C7
.database-vendorstringDatabase vendor for migrator schema. Options: h2, postgresql, oracle. Default: Automatically detected.
.interceptorsarrayList of custom variable interceptors to apply during migration. Each interceptor must implement the VariableInterceptor interface.

camunda.migrator.c7.data-source

Prefix: camunda.migrator.c7.data-source

PropertyTypeDescription
.table-prefixstringOptional prefix for Camunda 7 database tables. Default: (empty)
.auto-ddlbooleanAutomatically create/update Camunda 7 database schema. Default: false
.database-vendorstringThe database vendor is automatically detected and can currently not be overridden.
.*You can apply all HikariConfig properties.
.jdbc-urlstringJDBC connection URL for the source Camunda 7 database. Default: jdbc:h2:mem:migrator
.usernamestringUsername for Camunda 7 database connection. Default: sa
.passwordstringPassword for Camunda 7 database connection. Default: sa
.driver-class-namestringJDBC driver class for Camunda 7 database. Default: org.h2.Driver

camunda.migrator.c8

Prefix: camunda.migrator.c8

PropertyTypeDescription
.deployment-dirstringDefine directory which resources like BPMN processes are automatically deployed to C8.

camunda.migrator.c8.data-source

Prefix: camunda.migrator.c8.data-source

If the c8.data-source configuration is absent, the RDBMS history data migrator is disabled.

info

Heads-up: History Data Migrator is experimental.

PropertyTypeDescription
.table-prefixstringOptional prefix for Camunda 8 RDBMS database tables. Default: (empty)
.auto-ddlbooleanAutomatically create/update Camunda 8 RDBMS database schema. Default: false
.database-vendorstringDatabase vendor for C8 schema. Options: h2, postgresql, oracle. Default: Automatically detected.
.*You can apply all HikariConfig properties. For example:
.jdbc-urlstringJDBC connection URL for the target Camunda 8 RDBMS database. Default: jdbc:h2:mem:migrator
.usernamestringUsername for Camunda 8 database connection. Default: sa
.passwordstringPassword for Camunda 8 database connection. Default: sa
.driver-class-namestringJDBC driver class for Camunda 8 database. Default: org.h2.Driver

logging

Prefix: logging

PropertyTypeDescription
.level.rootstringRoot logger level. Default: INFO
.level.io.camunda.migratorstringMigrator logging level. Default: INFO
.file.namestringLog file location. Set to: logs/camunda-7-to-8-data-migrator.log. If not specified, logs are output to the console.