I'm not clear from your question, but I'm guessing you're talking about data stored in Docker volumes? (if they are bind mounts you're all good - you can just copy it). The compose files I found online for FireflyIII use volumes, but Hammond looked like bind mounts. If you're not sure, post your compose files here with the secrets redacted.
To move data out of a Docker volume, a common way is to mount the volume into a temporary container to copy it out. Something like:
docker run --rm \
-v myvolume:/from \
-v $(pwd):/to \
alpine sh -c "cd /from && tar cf /to/myvolume.tar ."
Then on the machine you're moving to, create the new empty Docker volume and do the temporary copy back in:
docker volume create myvolume
docker run --rm \
-v myvolume:/to \
-v $(pwd):/from \
alpine sh -c "cd /to && tar xf /from/myvolume.tar"
Or, even better, just untar it into a data directory under your compose file and bind mount it so you don't have this problem in future. Perhaps there's some reason why Docker volumes are good, but I'm not sure what it is.