CCPM to OCPM

Hi Akshay,

Hi ​@Navya K ,

Thanks for sharing the docs but I am unable to access the google sheets and also not able to request the access for the same. Please help me with another link if possible.
 

Thanks,
Akshay

Hi ​@Navya K Can this documentation be shared with the customer, or is it intended for internal use only?

 Hi there is any documentation on how to migrate ccpm to ocpm?

When planning a migration from Case-Centric Process Mining (CCPM) to Object-Centric Process Mining (OCPM), the approach depends entirely on your current setup.

If you are aiming for a standard view, you can simply explore the OCPM starter kits and catalogs. However, if your goal is to move a custom CCPM implementation to OCPM, there is no step-by-step guide or automated tool for this. Custom logic must be thoroughly understood and manually recreated.

Tanks ​@abhishek.chatu14 . If there isn't a standard migration guide, what is the best practice for migrating a custom CCPM implementation to OCPM? How do you usually approach it in real projects?

1. Map Current Activity Logic

Before migrating, document your current case-centric implementation to understand exactly how custom it is. Identify the base tables, timestamp fields, filter logic, and join logic that define your current activities.

2. Validate Event Counts

Set up a side-by-side comparison of event counts in both models.

• Add any custom events missing from the OCPM catalog and fix activities with zero counts.

• Focus on explaining logic differences and variance with process owners rather than forcing a perfect 1:1 count match.

3. Validate Timestamps

Once counts are within a reasonable margin of error, pull sample records to ensure both models are capturing the exact same timestamps for your events.

4. Map and Validate Attributes

Ensure all necessary case-centric attributes are accounted for in the new object-centric data model. Document any attribute name changes this map will be critical when you eventually migrate your existing KPIs and dashboard assets.

There are script available to automate this process. All eventlogs events are automatically written as Events and all other (case) tables are resulting in Objects. This is very quick, but also has some downsides:

• You keep the technical names of your tables and columns, instead of the business friendly Object attributes as in the Celonis Catalog Objects (but this is a design choice)
• Events are not linked to various objects, but you can add this later eventually
• With Objects you can re-use certain tables by using embeddings. You might want to make your model ‘smarter’ 
   

What we propose to our customers:

• Use the Celonis Catalog as much as possible (Procurement, Order Management, AP, AR, Inventory Management) as mentioned by ​@abhishek.chatu14 above
• Redesign your current CCDM instead of using the migration script, use the OCPM best practices and features
• If you want to use technical names instead of the pretty business oriented names, you can always create new objects from tables almost instantly, saving you a lot of time. You then only focus on creating the right/optimal connections.