How do we plan and estimate a migration from traditional BAW to CP4BA - assessment checklist?

Question

Management wants an estimate for moving 15 process apps and 6 toolkits from BAW 20.0.0.2 (WebSphere) to CP4BA 24.0. What should an assessment cover and which items usually drive the effort?

Answer 1

An assessment that produces a defendable estimate has five parts; the items in bold are the usual effort drivers:

1. Artifact inventory (from the twx exports or the repository REST): counts per type per app; heritage human services and heritage coaches (each is a rewrite as CSHS + coach views: 0.5-3 days per service), BPEL / IID modules (redesign as service flows or ACE), Java integrations (per jar: compile and test on Liberty, 0.5-2 days), file-system and OS-level scripts, custom Process Portal changes (rewrite for Workplace or drop), direct REST calls in coach views (prefix + CSRF), SQL integrations against BAW's own tables (fragile), tracking groups (fine), external services (recreate server definitions).
2. Integration inventory: every endpoint with protocol, auth and TLS; MQ / JMS queues (Liberty config), SMTP, LDAP, ECM; network path from the cluster (firewall rules, egress IPs, proxies); CORS for external UIs.
3. Platform and operations: OpenShift cluster sizing (production + non-production), storage classes, databases (new PostgreSQL vs migrated Db2), identity (LDAP / IdP with IAM), monitoring / logging stack, backup, CI/CD pipeline rebuild (Operations REST), runbooks and training for oc / operator.
4. Data: in-flight instances per app (drain vs database migration), document stores (BPM document store → FileNet or keep), PDW history (BAI going forward), audit requirements.
5. Testing: regression per app (a playback per exposed item), performance test of the top 3 processes, security test of the new front door, UAT of Workplace with business users (biggest change for them).

# quick inventory from a Process Center (classic REST): artifact types per snapshot
GET /rest/bpm/wle/v1/processApps                          -> apps, snapshots
GET /rest/bpm/wle/v1/snapshot/{snapshotId}?parts=validation    -> deprecated / heritage artifacts appear as warnings
GET /rest/bpm/wle/v1/assets?snapshotId={snapshotId}         -> managed files (jars, zips) to review

Rules of thumb from projects: an app with no heritage artifacts and REST-only integrations migrates in days (import, servers, env vars, test); each heritage human service adds days; each BPEL module adds weeks; the platform build (cluster, IAM, pipeline, monitoring) is a one-time 6-12 week effort that dominates small estates - do it with the first pilot app, then migrate the rest in waves.

References

• CP4BA documentation - planning and migrating from traditional BAW
• BAW - deprecated features to review