Well done. But you can use cf-terraforming easily.
"cf-terraforming is a command line utility to facilitate terraforming your existing Cloudflare resources."
Lots of DNS tools speak text/dns natively - and being able to easily get all zones in that format makes things like export / point in time backups much easier.
Shameless plug: After doing this kind of thing manually for a while, I created a service a few years ago to backup and alert you on DNS changes for all of your providers (CF, AWS, DO, Linode, etc).
It's free for one domain if anyone wants to take it for a spin: https://zonewatcher.com/
I added an equivalent script after we moved to Cloudflare. I found it's easy to make a mistake in the Cloudflare DNS web interface, e.g. it's easy to accidentally remove an entry.
Now, at every deploy to production, we do a backup of the DNS configuration on Cloudflare and save it on S3. This hardly costs us anything as each backup is only a small text file. But I now feel much more comfortable when editing our DNS config.
You can also use Terraform to manage CloudFlare DNS, and you get history, backups, consistency, and change management all for free. Just push the Terraform repo up to GitHub or GitBucket.
text/dns is a standard way to move DNS zones around - this means you can export this to a file, and possibly import it elsewhere, or just archive it as a point in time backup