Replacing Drone with Gitea Actions. How to "cleanup" database?

I’m planning on replacing Drone with Gitea Actions once Gitea 1.23 is released. Can/should I “cleanup” the Gitea database before this?

For example, I see that if I run this query…

SELECT * FROM commit_status ORDER BY id DESC LIMIT 100;

I get these results showing build status for each commit…

SELECT * FROM commit_status ORDER BY id DESC LIMIT 100;

  id   | index | repo_id |  state  |                   sha                    |                               target_url                                |   description    |               context_hash               |              context              | creator_id | created_unix | updated_unix 
-------+-------+---------+---------+------------------------------------------+-------------------------------------------------------------------------+------------------+------------------------------------------+-----------------------------------+------------+--------------+--------------
 11303 |     6 |      11 | success | 641f8d67b490702779cc2fd89df0f0e3cc1fd7bc | https://drone.mydomain.com/myname/docker/2144                           | Build is passing | d67078ee392b187966ea94a72d24c282204f0d9c | continuous-integration/drone/pr   |          2 |   1734671812 |   1734671812
 11302 |     5 |      11 | pending | 641f8d67b490702779cc2fd89df0f0e3cc1fd7bc | https://drone.mydomain.com/myname/docker/2144                           | Build is running | d67078ee392b187966ea94a72d24c282204f0d9c | continuous-integration/drone/pr   |          2 |   1734671800 |   1734671800
 11301 |     4 |      11 | success | 641f8d67b490702779cc2fd89df0f0e3cc1fd7bc | https://drone.mydomain.com/myname/docker/2143                           | Build is passing | d67078ee392b187966ea94a72d24c282204f0d9c | continuous-integration/drone/pr   |          2 |   1734671800 |   1734671800
 11300 |     3 |      11 | pending | 641f8d67b490702779cc2fd89df0f0e3cc1fd7bc | https://drone.mydomain.com/myname/docker/2143                           | Build is running | d67078ee392b187966ea94a72d24c282204f0d9c | continuous-integration/drone/pr   |          2 |   1734671788 |   1734671788
 11299 |     3 |      11 | success | 0be79b011c21bb36c95d4f8575432f1569f5f933 | https://drone.mydomain.com/myname/docker/2142                           | Build is passing | d67078ee392b187966ea94a72d24c282204f0d9c | continuous-integration/drone/pr   |          2 |   1734671787 |   1734671787
 11298 |     2 |      11 | pending | 641f8d67b490702779cc2fd89df0f0e3cc1fd7bc | https://drone.mydomain.com/myname/docker/2144                           | Build is pending | d67078ee392b187966ea94a72d24c282204f0d9c | continuous-integration/drone/pr   |          2 |   1734671777 |   1734671777
 11297 |     1 |      11 | pending | 641f8d67b490702779cc2fd89df0f0e3cc1fd7bc | https://drone.mydomain.com/myname/docker/2143                           | Build is pending | d67078ee392b187966ea94a72d24c282204f0d9c | continuous-integration/drone/pr   |          2 |   1734671776 |   1734671776

Does this stuff need to be removed? Should I just backup my git repos (stored on Docker in /var/lib/docker/volumes/gitea_gitea_new_data/_data/git/repositories/) then delete the entire database and start fresh?