# Export Data and Metadata CsvPath Framework enables you to publish data to its immutable archive. That's its job. But the Framework also gives you options for pushing data to other locations and/or to site your archive in part of your data lake. The options are: * Configure individual csvpaths within named-paths runs to [push results files to an SFTP server](/topics/how-tos/sftp-export.md) * Configure individual csvpaths within named-paths runs to [transfer results files to a local file system location or locally mounted remote share](/topics/how-tos/file-system-transfers.md) * Publish all or any of the result files of an individual csvpath within a named-paths run [to a CKAN server](/topics/how-tos/ckan/ckan-csvpath-setup.md) * Site the whole archive on one of [the CsvPath Framework's backends](/topics/how-tos/storage-backends.md): * AWS S3 * Azure Blob Storage * Google Cloud Storage * SFTP * And, of course, the local filesystem or mounted share And keep in mind, the CsvPath Framework's Archive is essentially a namespace. You can locate your archive anywhere. And you can run multiple archives to publish from multiple backends or in the same place, but under a different root directory. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://www.csvpath.org/topics/higher-level-topics/organizing-inbound-data/how-data-progresses-through-csvpath-framework/publishing/export-data-and-metadata.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.