How to define a general process migration plan?

Hello everyone,

Given the following hypothetical cases:

Case1: We have process definition 1.1.1 -> 1.1.2 with a change in some class. To perform this migration we need a migration plan defining the mapping.

Case 2: Process migration 1.1.2 -> 1.2.1 Another Change will require a new mapping and therefore a new migration plan.

Is there a way to have a general migration plan, or does it always have to be dependent on the type of change (meaning the migration plan)?

Thank you,

Best regards,