# Migration Data API

**URL:** <https://forum.getodk.org/t/migration-data-api/53548>\
**Category:** Support\
**Tags:** odk-central\
**Created:** [February 11, 2025, 12:20pm UTC](https://forum.getodk.org/t/migration-data-api/53548 "2025-02-11T12:20:29Z")\
**Posts on this page:** 1\
**Showing post:** 32

<div class="post-metadata">

**Author:** ![yanokwa](https://getodk.b-cdn.net/user_avatar/forum.getodk.org/yanokwa/32/1695_2.png) [@yanokwa](https://forum.getodk.org/u/yanokwa)\
**Post date:** [March 17, 2025, 12:08am UTC](https://forum.getodk.org/t/migration-data-api/53548/32 "2025-03-17T00:08:07Z")

</div>

I'm not sure the backups you took with the Central API/CLI when you set up the tunnel were good backups. My guess is that they are corrupt due to no disk space. If I had this problem, I would:

1. Make a written plan and have my teammates (and maybe ChatGPT?) critique it before proceeding. I'd also get [https://asciinema.org](https://asciinema.org) installed so I have a record of all actions taken to go along with notes I took during the process.
2. Use rsync to move the docker install from the source machine to a larger destination machine with the same OS and docker version. If rsync doesn't work, use the tunnel method to run pg\_dump on the source database and restore it with pg\_restore using [the scripts I shared earlier](https://forum.getodk.org/t/migration-data-api/53548/28).
3. Confirm everything works after rsync move, then upgrade Central on the destination machine, version by version. Make sure you can login to every version before continuing. Use snapshots so you can easily rollback if something fails.

---

_[View the full topic](https://forum.getodk.org/t/migration-data-api/53548)._