Supported database combinations for process instance move

Edit online
Draft comment:
This topic is shared by BAW, CP4BA. Last updated on 2026-04-29
Process instance move supports 16 database combinations, helping you to move from any supported source database to any supported target database.

Supported database combinations

The following table shows the supported source and target database combinations for process instance move:

Table 1. Database move combinations
Source database Oracle target SQL Server target Db2 target PostgreSQL target
Oracle Supported Supported Supported Supported
SQL Server Supported Supported Supported Supported
Db2 Supported Supported Supported Supported
PostgreSQL Supported Supported Supported Supported
Note: All database combinations that are listed in the table 1 are supported in version 26.0.0 GA for both CP4BA BAW and BAW on container deployments.

Supported deployment targets

Process instance move supports the following deployment scenarios:

  • BAW Traditional to CP4BA BAW: move from traditional WebSphere Application Server (tWAS) with Db2, Oracle, SQL Server, or PostgreSQL to CP4BA BAW with Db2, Oracle, SQL Server, or PostgreSQL.
  • BAW Traditional to BAW on Container: move from traditional WebSphere Application Server (tWAS) with Db2, Oracle, SQL Server, or PostgreSQL to BAW Containers with Db2, Oracle, or PostgreSQL.

Supported Kubernetes platforms

Process instance move is supported on the following Kubernetes platforms:

  • Red Hat OpenShift Container Platform (OCP)
  • Rancher
  • VMware Tanzu
  • Google Kubernetes Engine (GKE)
  • Azure Kubernetes Service (AKS)
  • Amazon Elastic Kubernetes Service (EKS)
Note: Platform support for GKE, AKS, and EKS depends on the availability of other required capabilities in those environments.

Database version requirements

Ensure that both source and target databases meet the following requirement:

  • Database versions must be compatible with Business Automation Workflow and Cloud Pak for Business Automation requirements.