> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/grow-and-monetize/analytics/export-your-download-history-after-a-plan-change.md).

# Export your download history after a plan change

Request a CSV export of six months of download counts after you moved from an older plan.

Use this task to save the download counts of a podcast that lie outside the analytics history of your current plan. The export is a transition offer for customers who moved from an older plan.

## Before you start

* Sign in as the podcast owner, or as an admin or editor with the permission to view analytics for the podcast.
* Check that your account qualifies. The export is available when one of these conditions is true:
  * Your account moved from an older plan to a current plan less than six months ago.
  * Your account is on an older plan, and a cancellation of the subscription is scheduled but not yet executed.
* The export does not depend on the CSV export of your plan.

{% tabs %}
{% tab title="Classic view" %}

### Complete the task

1. In Analytics, open the podcast.
2. Next to the date range picker, select **Export historical download data (CSV)**.
3. Wait while the button shows **Preparing export...** and then **Export requested**. The page tells you that Podigee prepares the export in the background. You receive a download link by email.
4. Open the email **Your download history export is ready** and select **Download CSV**.
5. Save the file. The download link expires one hour after Podigee sent the email. If the link is expired, request the export again.

### What the export contains

* Six months of download counts for the podcast. When your account moved from an older plan, the six months end on the day of the plan change. When a cancellation is scheduled, the six months end today.
* The counts come from the complete data, not from the analytics history of your current plan.
* The file has the columns **Period start** and **Downloads**. The length of each period follows the amount of data automatically.

### Expected result

You receive one email per requested export with a working download link, and the CSV file opens in a spreadsheet with one row per period.

### If you cannot complete the task

* If the button is missing, your account does not meet one of the conditions above, or the podcast is not published.
* If the page shows **An export is already being prepared.**, an export for this podcast was requested a few minutes ago. Wait for its email before you request another one.
* If the page shows **Something went wrong. Please try again.**, request the export again later.
* If the email does not arrive, check your spam folder and the email address of your account.
  {% endtab %}

{% tab title="Podigee workspace" %}
The Podigee workspace does not include the export of your download history after a plan change yet. Switch to the classic view to request the export.
{% endtab %}
{% endtabs %}

## Next step

[Understand analytics history by plan](/documentation/grow-and-monetize/analytics/understand-analytics-history-by-plan.md) lists the history that each current plan includes.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.podigee.com/documentation/grow-and-monetize/analytics/export-your-download-history-after-a-plan-change.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.