EAFLOW · CASE · PREVISIONAL
Migration from the legacy BPA to portable BPMN 2.0, connected to the graph
A social-security contributions financial-services organization, with an operation in Chile, tested Process Knowledge as a proof of concept, over a representative scenario with sample data: processes from an enterprise BPA tool —EPC and extended BPMN notations— migrated to EAFlow normalizing to portable BPMN 2.0, with their legacy hierarchy and codes preserved, and connected to risks, controls and continuity over the same Operational Graph.
The proof of concept showed that the solution works over a representative scenario of the social-security domain and the value it delivers: the sample corpus available in portable BPMN 2.0 and connected to the Operational Graph, with the legacy structure as a navigable anchor and the processes linked to the compliance and continuity model.
The challenge
Social-security contributions financial-services organizations that keep their process practice on a legacy enterprise BPA tool face the same pattern. The problem is not the quality of the models: it is that the corpus lives trapped in the original modeler, isolated from the rest of the operation.
- The legacy BPA repository is a valuable asset: years of curated models in proprietary notations (EPC, the modeler's extended BPMN) represent investment, while the license cost grows and the models are not portable outside the tool.
- The decomposition hierarchy and the legacy codes are the language the organization knows. Replacing them with a new numbering breaks operational knowledge.
- EPC and extended BPMN do not move trivially to portable BPMN 2.0: a serious migration demands equivalence rules, exception validation and explicit reporting of the cases that do not migrate cleanly.
- The repository lives isolated from the rest of the operational model: the processes are not connected to the risks, controls nor to continuity, even though they share the same universe.
- Migration proposals are usually binary —migrate everything at once (risky) or migrate nothing (the legacy bill keeps growing)—, without a prior capability test that reduces the perceived risk.
Process knowledge is not sustained with an isolated modeler. It is sustained with processes migrated, portable, connected to the graph and queryable alongside their compliance and continuity context.
The EAFlow solution
Process Knowledge is a cross-cutting solution of the Process and Architecture Modernization area, built on the shared Operational Graph layer of EAFlow Platform, operating on top of the enterprise BPA tool corpus —without being tied to the original modeler. The proof of concept covered, over a representative scenario with sample data, the legacy enterprise BPA replacement scenario:
- Migration from the legacy BPA to portable BPMN 2.0. A scoped set of processes from the legacy enterprise modeler is migrated to EAFlow and normalized to portable BPMN 2.0, with the decomposition hierarchy and the legacy codes preserved as a navigable anchor.
- EPC → portable BPMN 2.0 equivalence rules. Each source notation is mapped to its equivalence with a written rule; the cases that do not migrate cleanly are explicitly reported for human review.
- Processes connected to the compliance model. The migrated processes are connected to risks and controls in the graph, demonstrating the value of the shared context over the same base.
- Processes connected to the continuity model. The critical processes of the scenario are linked to the continuity model, connecting process, risk, control and dependency.
- Operational Graph as the unified destination. Processes, tasks, roles, risks, controls, critical continuity processes and relationships become connected as first-class entities, with source citation and event-level traceability.
- Deterministic analytical support. Navigation, structural querying and reporting over the migrated processes operate deterministically over the graph.
The legacy enterprise BPA replacement is assisted, not automatic: the cases that do not migrate cleanly are reported for human review. The real level of integration with each modeler is validated by maturity and technical validation in discovery, and the equivalence rules are documented by notation family. The base is ready to incorporate natural-language querying over the corpus as a later evolution, without that capability being part of what was tested in this proof of concept.
What was tested
The proof of concept was run over a representative scenario with sample data of the social-security domain. The team walked the complete migration capability: reading the legacy BPA model (EPC, extended BPMN), normalization to portable BPMN 2.0 with equivalence rules and exception reporting, preservation of the decomposition hierarchy and of the legacy codes as a navigable anchor, and connection of the migrated processes to risks, controls and critical continuity processes over the shared graph. Navigation, structural querying and reporting over the structure of the migrated corpus worked deterministically.
Demonstrated capabilities
- Operational Graph as the shared context base.
- Assisted migration of the legacy BPA corpus to portable BPMN 2.0, with explicit reporting of cases that do not migrate cleanly.
- Documented EPC → portable BPMN 2.0 equivalence rules.
- Decomposition hierarchy and legacy codes preserved as a navigable anchor.
- Processes connected to risks and controls in the compliance model.
- Critical processes connected to the continuity model.
- Deterministic graph navigation, structural querying and reporting over the migrated corpus.
Observed result
The sample corpus went from "being trapped in the legacy modeler" to being available in portable BPMN 2.0 and connected to the graph, with the decomposition hierarchy and the legacy codes preserved as a navigable anchor and the processes linked to risks, controls and continuity over the same base. The source notations were normalized with written rules and the cases that did not migrate cleanly were reported for human review.
The proof of concept showed that the legacy enterprise BPA migration capability is applicable to the social-security domain over a representative scenario, leaving the evolutionary-path decision —migrate the real repository at scale, complete the connection to the inventory and the risk-control universe, or incorporate natural-language querying— in the team's hands, with the tested capability as evidence and not as a forced decision.
Why it matters for other organizations
The pattern repeats in social-security contributions financial-services organizations with years of investment in an enterprise BPA tool: the corpus is valuable, the hierarchy and the legacy codes are the team's language, the processes live isolated from the compliance and continuity model, and the license cost grows while migration is perceived as risky. Showing, over a representative scenario with sample data, that the notations are normalized to portable BPMN 2.0, that the legacy structure is preserved and that the processes become connected to the compliance and continuity model turns an "all or nothing" decision into a decision informed by evidence, as a step prior to migrating the real repository.
Starting with process knowledge is also a low-risk entry point: the same Operational Graph that sustains the processes later sustains architecture, inventory, documents, risk and operation.
How it scales — related solutions
The migrated process corpus is reused over the same Operational Graph:
- Toward migrating the real repository Process Knowledge
At-scale migration of the legacy enterprise BPA repository, full connection to the graph and —if the client decides— natural-language querying over the migrated corpus.
- Toward risk and control Risk & Control Assurance
The migrated processes connect to the risk-control universe, with evidence and process-control-evidence traceability.
- Toward continuity Operational Continuity & Resilience
The migrated critical processes feed the impact analysis and the critical dependencies.
- Toward the application inventory Live IT Inventory
The applications that support the processes connect to the IT portfolio with owners, criticality, dependencies and integrations.
- Toward architecture governance Enterprise Architecture Governance
The process corpus becomes the base of the living architecture repository, with metamodel, traceability and governance by domain.
- Toward changes and roadmap Change Impact
When a change touches a process in the corpus, the graph allows estimating the impact over applications, integrations, data and documents before deciding.