You can use my KJAR for reproducing but the essence of the issue is rather simple - migrate process instance while there is active timer. Deploy the attached KJAR twice onto kie-server - use per process instance strategy first time with ID TimerProjectV1 second time with ID TimerProjectV2 Execute Migration with kie-server-client: private static final String SRC_CONTAINER = "TimerProjectV1" ; private static final String TARGET_CONTAINER = "TimerProjectV2" ; private static final String SRC_PROCESS_ID = "TimerProject.TimerProcess1" ; private static final String TARGET_PROCESS_ID = "TimerProject.TimerProcess2" ; ... long pid = processClient.startProcess(SRC_CONTAINER, SRC_PROCESS_ID); MigrationReportInstance report = admin.migrateProcessInstance(SRC_CONTAINER, pid, TARGET_CONTAINER,TARGET_PROCESS_ID); The migration will be successful, however, when the timer is suppose to fire after the migration, you will observe this exception -see ppi.log With Singleton the exception is different - see singleton.log