Skip to main content
Version: 8.9 (unreleased)

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
  • 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, decisions, users, groups, and authorizations.
  • Audit log entries are not migrated for batch operations, identity links, attachments, job definitions, jobs, external tasks, metrics, operation logs, filters, comments, and properties.
Entity TypePropertyMigration SupportedNotes
Audit log
auditLogKeyYes
entityKeyPartiallyMigrated only for entities related to user tasks, process definitions, and process instances
entityTypeYes
operationTypeYes
entityVersionYes
entityValueTypeNo
entityOperationIntentNo
batchOperationKeyNo
batchOperationTypeNo
timestampYes
actorTypeYes
actorIdYes
agentElementIdNo
tenantIdYes
tenantScopeYes
resultYes
annotationYes
categoryYes
processDefinitionIdYes
decisionRequirementsIdNo
decisionDefinitionIdNo
processDefinitionKeyYes
processInstanceKeyYes
rootProcessInstanceKeyYes
elementInstanceKeyPartiallyMigrated only for entities related to user tasks
jobKeyNo
userTaskKeyYes
decisionRequirementsKeyNo
decisionDefinitionKeyNo
decisionEvaluationKeyNo
deploymentKeyNo
formKeyNo
resourceKeyNo
relatedEntityTypeNo
relatedEntityKeyNo
entityDescriptionPartiallyMigrated only for user, group, tenant, and delete variable operations
partitionIdYes
historyCleanupDateYes
Decision definition
decisionDefinitionKeyYes
nameYes
decisionDefinitionIdYes
tenantIdYes
versionYes
decisionRequirementsIdYes
decisionRequirementsKeyYes
decisionRequirementsNameYes
decisionRequirementsVersionYes
Decision instance
decisionInstanceIdYes
decisionInstanceKeyYes
stateYes
evaluationDateYes
evaluationFailureNo
evaluationFailureMessageNo
resultYes
flowNodeInstanceKeyYes
flowNodeIdYes
processInstanceKeyYes
processDefinitionKeyYes
processDefinitionIdYes
decisionDefinitionKeyYes
decisionDefinitionIdYes
decisionRequirementsKeyYes
decisionRequirementsIdYes
rootDecisionDefinitionKeyYes
decisionTypeYes
tenantIdYes
partitionIdYes
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
hasIncidentNo
tenantIdYes
partitionIdYes
rootProcessInstanceKeyYes
Form
formKeyYes
tenantIdYes
formIdYes
schemaYes
versionYes
isDeletedNo
Incident
incidentKeyYes
processDefinitionKeyYes
processDefinitionIdYes
processInstanceKeyYes
rootProcessInstanceKeyYes
flowNodeInstanceKeyYesWill not be populated when an incident occurs in flow node in waiting state with asyncBefore configuration
flowNodeIdYes
jobKeyNo
errorTypeYesPopulated when an equivalent mapping is possible. In all other cases, it's set to UNKNOWN
errorMessageYes
errorMessageHashNo
creationDateYes
stateYes
treePathYes
tenantIdYes
partitionIdYes
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
partitionIdYes
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-<processInstanceId>, business-key-<businessKey> (if business key exists)
User task
userTaskKeyYes
elementIdYes
nameYes
processDefinitionIdYes
creationDateYes
completionDateYes
assigneeYes
stateYes
formKeyYes
processDefinitionKeyYes
processInstanceKeyYes
rootProcessInstanceKeyYes
elementInstanceKeyYes
tenantIdYes
dueDateYes
followUpDateYes
candidateGroupsNo
candidateUsersNo
externalFormReferenceNo
processDefinitionVersionYes
serializedCustomHeadersNo
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
partitionIdYes
Variable
variableKeyYes
nameYes
typeYes
doubleValueYes
longValueYes
valueYes
fullValueYes
isPreviewYes
scopeKeyYes
processInstanceKeyYes
rootProcessInstanceKeyYes
processDefinitionIdYes
tenantIdYes
partitionIdYes
elementInstanceKeyYes