For the complete documentation index, see llms.txt.
Skip to main content
Version: 8.9

Coverage

The following tables show which Camunda 8 entities and properties are migrated by the History Data Migrator.

Unsupported entities

The following entities are not supported for migration (no properties are migrated):

  • Batch operation
  • Batch operation item
  • Cluster variable
  • Correlated message subscription
  • Exporter position
  • History deletion
  • Job metrics batch
  • Message subscription
  • Sequence flow
  • Usage metric
  • Usage metric (TU)
  • Web session

Supported entities

The following limitations apply to audit log entries:

  • Audit log entries are migrated only for user tasks, process definitions, process instances, variables, jobs, external tasks, users, groups, and authorizations.
  • Audit log entries are not migrated for batch operations, identity links, attachments, decisions, job definitions, metrics, operation logs, filters, comments, and properties.

The Migration Supported column uses the following values:

  • Yes — the property is populated, either from a Camunda 7 value or with a fixed, semantically correct value (for example, a historic job's state is always COMPLETED).
  • Yes, with placeholder — the property is always populated, but the value may sometimes be a placeholder rather than data migrated from Camunda 7. See the Notes column for the placeholder used.
  • Partially — the property is populated for some records and not others.
  • No — the property is not populated.
Entity TypePropertyMigration SupportedNotes
Audit log
auditLogKeyYes
entityKeyYes, with placeholderSet to the target entity's key for entities related to user tasks, process definitions, and process instances. For all other entity types, a placeholder (C7_MIGRATED) is written.
entityTypeYes
operationTypeYes
entityVersionYes
entityValueTypeNo
entityOperationIntentNo
batchOperationKeyNo
batchOperationTypeNo
timestampYes
actorTypeYes
actorIdYes
agentElementIdNo
tenantIdYes
tenantScopeYes
resultYes
categoryYes
processDefinitionIdYes
decisionRequirementsIdNo
decisionDefinitionIdNo
processDefinitionKeyYes
processInstanceKeyYes
rootProcessInstanceKeyYes
elementInstanceKeyPartiallyMigrated only for entities related to user tasks
jobKeyPartiallyMigrated only for entities related to jobs
userTaskKeyYes
decisionRequirementsKeyNo
decisionDefinitionKeyNo
decisionEvaluationKeyNo
deploymentKeyNo
formKeyNo
resourceKeyNo
relatedEntityTypeNo
relatedEntityKeyNo
entityDescriptionPartiallyMigrated only for user, group, tenant, and delete variable operations
partitionIdYesAssigned based on the root process instance, or randomly if not related to a process instance. See partition distribution.
historyCleanupDateYes
Decision definition
decisionDefinitionKeyYes
nameYes
decisionDefinitionIdYes
tenantIdYes
versionYes
decisionRequirementsIdYesFor single Camunda 7 decisions that have no decision requirements definition (DRD), a synthetic DRD is generated. Its ID uses the configured legacy ID prefix followed by the decision ID, for example c7-legacy-<decisionId> with the default prefix.
decisionRequirementsKeyYes
decisionRequirementsNameYes
decisionRequirementsVersionYes
Decision instance
decisionInstanceIdYes
decisionInstanceKeyYes
stateYes
evaluationDateYes
evaluationFailureNo
evaluationFailureMessageNo
resultYesWhen the Camunda 7 decision produced no result, the value is migrated as the JSON literal string "null" instead of a database null.
flowNodeInstanceKeyYes
flowNodeIdYes
processInstanceKeyYes
processDefinitionKeyYes
processDefinitionIdYes
rootProcessInstanceKeyYes
decisionDefinitionKeyYes
decisionDefinitionIdYes
decisionRequirementsKeyYes
decisionRequirementsIdYes
rootDecisionDefinitionKeyYes
decisionTypeYes
tenantIdYes
partitionIdYesAssigned based on the root process instance, or randomly for standalone decisions. See partition distribution.
evaluatedInputsYes
evaluatedOutputsYes
historyCleanupDateYes
Decision requirements
decisionRequirementsKeyYes
decisionRequirementsIdYes
nameYes
resourceNameYes
versionYes
xmlYes
tenantIdYes
Flow node instance
flowNodeInstanceKeyYes
processInstanceKeyYes
processDefinitionKeyYes
processDefinitionIdYes
flowNodeScopeKeyYes
startDateYes
endDateYes
flowNodeIdYes
flowNodeNameYes
treePathYes
typeYes
stateYes
incidentKeyNo
numSubprocessIncidentsNo
tenantIdYes
partitionIdYesAssigned based on the root process instance. See partition distribution.
rootProcessInstanceKeyYes
Form
formKeyYes
tenantIdYes
formIdYes
schemaYes
versionYes
isDeletedYesAlways false.
Incident
incidentKeyYes
processDefinitionKeyYes
processDefinitionIdYes
processInstanceKeyYes
rootProcessInstanceKeyYes
flowNodeInstanceKeyYesAlways populated. Incidents for which a flow node instance key cannot be resolved are skipped; see Incidents limitations.
flowNodeIdYes
jobKeyPartiallyPopulated only for entities related to jobs of type asynchronous continuation.
errorTypeYesPopulated when an equivalent mapping is possible. In all other cases, it's set to UNKNOWN
errorMessageYes, with placeholderSet to the Camunda 7 incident message. When the incident has no message, a placeholder (C7_NO_MESSAGE) is written.
errorMessageHashNo
creationDateYes
stateYesAlways Resolved
treePathYes
tenantIdYes
partitionIdYesAssigned based on the root process instance. See partition distribution.
Job
jobKeyYes
typeNo
workerYes, with placeholderSet to the hostname of the machine where Camunda 7 executed the job. When the hostname is unavailable (for example, legacy rows or a custom HostnameProvider), a placeholder (C7_MIGRATED) is written.
stateYesAlways COMPLETED.
kindYesAlways BPMN_ELEMENT.
listenerEventTypeYesAlways UNSPECIFIED.
retriesYesAlways 0.
isDeniedNo
deniedReasonNo
hasFailedWithRetriesLeftNo
errorCodeNo
errorMessageNo
serializedCustomHeadersNo
customHeadersNo
deadlineNo
endTimeNo
processDefinitionIdYes
processDefinitionKeyYes
processInstanceKeyYes
rootProcessInstanceKeyYes
elementIdYes
elementInstanceKeyYesAlways populated. Jobs for which an element instance key cannot be resolved are skipped; see Jobs limitations.
tenantIdYes
partitionIdYesAssigned based on the root process instance. See partition distribution.
creationTimeYes
lastUpdateTimeYesSourced from the most recent Camunda 7 historic job log entry.
External Task as a Job
jobKeyYes
typeYesTopic name
workerYes, with placeholderAlways set to a placeholder (C7_MIGRATED); Camunda 7 does not record a worker hostname for external tasks.
stateYesAlways COMPLETED.
kindYesAlways BPMN_ELEMENT.
listenerEventTypeYesAlways UNSPECIFIED.
retriesYesAlways 0.
isDeniedNo
deniedReasonNo
hasFailedWithRetriesLeftNo
errorCodeNo
errorMessageNo
serializedCustomHeadersNo
customHeadersNo
deadlineNo
endTimeNo
processDefinitionIdYes
processDefinitionKeyYes
processInstanceKeyYes
rootProcessInstanceKeyYes
elementIdYes
elementInstanceKeyYesAlways populated. External tasks for which an element instance key cannot be resolved are skipped; see Jobs limitations.
tenantIdYes
partitionIdYesAssigned based on the root process instance. See partition distribution.
creationTimeYes
lastUpdateTimeYesSourced from the most recent Camunda 7 historic external task log entry.
Process definition
processDefinitionKeyYes
processDefinitionIdYes
resourceNameYes
nameYes
tenantIdYes
versionTagYes
versionYes
bpmnXmlYes
formIdYes
Process instance
processInstanceKeyYes
rootProcessInstanceKeyYes
processDefinitionIdYes
processDefinitionKeyYes
stateYes
startDateYes
endDateYes
tenantIdYes
parentProcessInstanceKeyYes
parentElementInstanceKeyYes
numIncidentsYesAlways 0.
versionYes
partitionIdYesAssigned based on the root process instance, or randomly for root process instances. See partition distribution.
treePathYes
historyCleanupDateYes
tagsYesTags do not exist in Camunda 7, but we allow to set them during migration via interceptors and they will be visible in Camunda 8 after migration. Default tags: legacy-id
businessIdYes
User task
userTaskKeyYes
elementIdYes
nameYes
processDefinitionIdYes
creationDateYes
completionDateYes
assigneeYes
stateYes
formKeyYes
processDefinitionKeyYes
processInstanceKeyYes
rootProcessInstanceKeyYes
elementInstanceKeyYes
tenantIdYes
dueDateYes
followUpDateYes
candidateGroupsYes
candidateUsersYes
externalFormReferenceNo
processDefinitionVersionYes
customHeadersNo
priorityYes
tagsYesTags do not exist in Camunda 7, but we allow to set them during migration via interceptors and they will be visible in Camunda 8 after migration
partitionIdYesAssigned based on the root process instance. See partition distribution.
Variable
variableKeyYes
nameYes
typeYes
doubleValueYes
longValueYes
valueYes
fullValueYes
isPreviewYes
scopeKeyYes
processInstanceKeyYes
rootProcessInstanceKeyYes
processDefinitionIdYes
tenantIdYes
partitionIdYesAssigned based on the root process instance. See partition distribution.
elementInstanceKeyYes