The heterogeneity in enterprise design stakeholders and models gen- erally demands for consistent and efﬁcient transformations of enterprise design knowledge between different conceptual modelling languages. A systematic pro- cess and precise model transformation speciﬁcations are a prerequisite for realizing such transformations. The Design and Engineering Methodology for Organiza- tions (DEMO) approach represents the organization design of an enterprise in four linguistically based, semantically sound aspect models. The Business Pro- cess Model and Notation (BPMN) on the other hand enables more ﬂexibility in creating models and beneﬁts from wide adoption in industry, the execution of pro- cesses e.g., by simulations, and the availability of proper tooling. A transformation of DEMO models into BPMN models is thus desirable to avail of both, the seman- tic sound foundation of DEMO and the wide adoption and execution possibilities of BPMN. Previous research already developed some principles and practices for transforming DEMO models into BPMN models, based on DEMOSL 3.7. This study focuses on the latest DEMO language speciﬁcation, DEMOSL 4.5, since we believe that more clarity is required to specify consistent, well-motivated trans- formation speciﬁcations. We present a list of main requirements for developing transformation speciﬁcations to transform concepts represented in a Coordination Structure Diagram and Process Structure Diagram of DEMO into corresponding concepts in a BPMN collaboration diagram. The article makes three contribu- tions: (1) Generic requirements for developing DEMO-to-BPMN transformation speciﬁcations; (2) Nine transformation scenarios that are validated by multiple demonstration cases; and (3) A comprehensive college case that demonstrates all transformation scenarios.