> For the complete documentation index, see [llms.txt](https://docs.shadow.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shadow.xyz/getting-data/recurring-exports.md).

# Recurring exports

{% hint style="info" %}
Recurring exports are included on paid [Pro Shadow Fork plans](https://www.shadow.xyz/pricing).
{% endhint %}

Recurring exports allow you to export data to a destination of your choice on a recurring basis.

## Steps

1. **Choose your data:** Export shadow and/or mainnet data (coming soon), and specify which contracts and events you want to export.
2. **Choose your destination:** Export your data to Dune Analytics, GCS, or S3 (coming soon).
3. **Choose your settings:** Specify the starting block you want to export for, the file format (CSV or Parquet), and how to partition the data (daily, hourly, or no partitioning).

{% embed url="<https://www.veed.io/view/c60e69f2-a6e9-41e5-9d0b-94996e7ea7fe?panel=share>" %}

{% hint style="warning" %}
If you choose to export shadow data, you’ll only be able to select events from contract addresses that you have shadowed (e.g. deployed modifications to).\
\
If you shadowed the implementation of a proxy contract, you’ll need to perform a “no-op deploy” on the proxy contract by hitting “Compile > Deploy” in the editor without making any shadow changes. We’re working on a better experience for this!
{% endhint %}