Doug, I’ve had this suggestion come up a couple times in the past (mostly related to DataGrab, but also standalone import/export), and I’m not sure the time I would spend on creating it would be worth the effort. The main issue I have is long term support of such a feature. If I give people an option to export/import JSON or whatever, if they modify that JSON and try to re-import it, and it doesn’t work, then I have to figure out why. If the table structure of Bloqs changes, and someone tries to import an old export file, and that doesn’t work, then the customer isn’t in a good spot and I have to figure out how to fix their import file. I think the use case for a natively supported import/export is low, given the amount of work needed to implement and support it. If you’re just needing to create a base set of blocks to start a project from, you’re probably better off creating an sql dump of your base configuration, then just running those queries on new projects. I know this seems like passing the buck, but I’m just not sure I want to go down the path of building and supporting an import/export feature.