Recommend Cloudflare add the following capabilities to its website:
(1) Ability to display and print a summary of client’s website (Cloudflare) information (*)
(2) Ability to export, import, and print client’s website DNS Records and Page Rules (*)
(*) Useful if on-boarding a new website or data is lost.
Looking forward to input from other Cloudflare users and Cloudflare’s client support team!
+1 to all of these.
An export and import would be extremely useful.
@komarEX you can export a BIND file from Cloudflare as well.
There are a couple of libraries/scripts available which can be used to export settings:
GitHub - alphagov/cloudflare-configure: Commandline tool for configuring CloudFlare's CDN (hasn’t been updated in a while)
GitHub - rmg/cloudflare-backup: Simple tool for backing up your CloudFlare hosted DNS records (backup DNS)
And a good Python library if anyone is interested: cloudflare · PyPI
No need to complicate things at the front-end level for those who are not programmers, coders, etc. All that is being asked is for CF to integrate the enhancements with simple buttons (export, import, and print). At the back-end level, we’ll let the CF gurus do their magic.
Fair enough. It’s a good request and I’ve passed it along to the product team. I have a habit of trying to solve the problem ‘right now’ which isn’t always the most useful response. 
@cs-cf: Yep. It’s tempting to do that! I do the same more often than not. Thank you.
I had a similar desire, so I wrote some PHP code that exports the “all settings” api endpoint and also lists out the firewall rules. If anyone wants to use it and doesn’t use Drupal, the main pieces are in the file chotchkie.drush.inc
Good Day, @cs-cf!
What’s the latest on this? An update from your development team would be appreciated.
These features can be used now by the entire Cloudflare community.
Thank you!
Another vote for this feature.
Please suggest we have any plans to integrate in Cloudflare?
Getting bind files or DNS records are easy from Cloudflare, the APi is easy. Page rules aren’t close to easy… I would love to see a good example of using the API to export all of the page rules and then importing them back into another zone.
Hi @cs-cf,
I’m back … hahaha.
Hey, where does CF stand with this (adding export, import, and print buttons)?
We’re on the stands watching this. Popcorn is running low.
Cheers!
No button, but we do now have a better/supported way to export your current config now.
What is the reason for not providing these “buttons” (or similar front-end functionality)?
Remember, we’re not developers, so the Terraforming approach doesn’t seem to help at all.
Simplicity and performing the requested functions at the front-end (not back end) would be helpful.
Thank you!
I don’t think it’s a question of not providing this functionality, rather there’s a (very long) list of things we can build and it’s prioritized based on a lot of different criteria across individual teams and the company as a whole. And having looked at the scope/effort/value of the particular feature it hasn’t yet made it to the bar where the work has been prioritized.
For perspective at the moment we’ve had Cloudflare registrar live for over a year and still don’t have the ability for a customer to buy a net new domain through Cloudflare. Obviously a feature that provides value, but in the list of things which need to be done for registrar, as prioritized by the folks trusted to make decisions on what needs to be done next, it hasn’t yet hit that bar.
Today we have an import function for BIND files which is, all things considered, a pretty simple function, but I can tell you I’ve spent hours in total debugging why a particular BIND file won’t parse. Import logic, file formatting, error handling, long term maintenance as new features are added has a very real cost associated with it far beyond just adding a button.
I don’t have any particular insight into this feature’s prioritization (I’m not a developer or on the product team but I’ve been helping to build SaaS solutions for ~= 20 years so just speaking to the situation generally). For the moment Terraform integration is the best solution we have and the one we’ve prioritized spending resources on.
Another vote, even though it seems like this isn’t a major priority.
I try to take my own backups of every cloud service that I use.
cf-terraforming continues to be where we invest in exporting current config and Terraform generally for modification of items. Beyond that there’s an API and libraries in Go, Python, etc one can write their own tools.
Fair enough. But suffice to say that I share @Aviator’s sentiments. Some users simply want a simple GUI to pull their data out!
+1 To this