# Liquibase migration from Camunda, already on version 7.24.0

**URL:** <https://forum.operaton.org/t/liquibase-migration-from-camunda-already-on-version-7-24-0/443>\
**Category:** Development\
**Created:** [August 25, 2026, 7:55am UTC](https://forum.operaton.org/t/liquibase-migration-from-camunda-already-on-version-7-24-0/443 "2026-08-25T07:55:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rares27](https://forum.operaton.org/letter_avatar_proxy/v4/letter/r/8c91f0/32.png) [@Rares27](https://forum.operaton.org/u/Rares27)\
**Post date:** [August 25, 2026, 7:55am UTC](https://forum.operaton.org/t/liquibase-migration-from-camunda-already-on-version-7-24-0/443/1 "2026-08-25T07:55:35Z")

</div>

Hello,

**Mention** : using **Operaton 2.2.0-M2**

As steps of how I overcame the problem mentioned in the link / came to a resolution.

I have a added **before-camunda.xml**.

**What does this include?**

```auto
DELETE FROM DATABASECHANGELOG
WHERE ID = '7.24.0-tag'
  AND AUTHOR = 'Camunda'
  AND FILENAME = 'org/camunda/bpm/engine/db/liquibase/camunda-changelog.xml'
  AND EXISTS (
    SELECT 1
    FROM DATABASECHANGELOG
    WHERE ID = '7.24.0-tag'
      AND AUTHOR = 'Operaton'
      AND FILENAME = 'org/camunda/bpm/engine/db/liquibase/camunda-changelog.xml'
);

```

and

```auto
UPDATE DATABASECHANGELOG
SET AUTHOR = 'Operaton',
    MD5SUM = NULL
WHERE AUTHOR = 'Camunda'
  AND ID IN ('7.23-to-7.24', '7.24.0-tag')
  AND FILENAME = 'org/camunda/bpm/engine/db/liquibase/camunda-changelog.xml';

```

**Reason?**

Liquibase identifies changesets by **ID + AUTHOR + FILENAME**. When upgrading from Camunda to Operaton, the AUTHOR changed from ‘Camunda’ to ‘Operaton’, so Liquibase sees it as a new changeset and tries to re-execute it.

**Solution**

**DELETE** — Remove the old Camunda tag if the new Operaton tag already exists (cleanup for failed/retried deployments)  
**UPDATE** — Change the AUTHOR from ‘Camunda’ to ‘Operaton’ for the two known changesets, plus clear the MD5SUM so Liquibase doesn’t complain about checksum mismatchesFor fresh databases: These statements do nothing (0 rows affected), and Operaton just creates everything normally.

I went for a solid idempotent migration pattern — smart defensive coding for the version transition.

**To be noted** : I was at **Camunda version**  **7.24.0 before integrating Operaton**.

Hope this helps, if you need any other information, let me know.  
Much appreciated. Enjoy your week!

> [@Liquibase migration from camunda](https://forum.operaton.org/t/liquibase-migration-from-camunda/304/17):
>
> Hello @kthoms , I have it running on PRD since yesterday, once I get back from holiday, on the 24th of August, I will leave the steps I did to make everything work properly given the current context. As mentioned I had 2 script changes that I had to do so, I will leave the database CHANGELOG situation before and after, maybe it will help and also with the proper explanations on why I went this route to make it run properly. If you need further assistance, please let me know. Much appreciated…