# Export / Import CSV

{% tabs %}
{% tab title="Export" %}
Birdie provides four interrelated CSV files when exporting user feedback data. This document explains their structure, relationships, and common usage rules.

### feedbacks.csv — Main Feedback Export

This file contains raw records of all feedback captured in your Birdie account, based on the filters applied at export time.

Each row represents a unique piece of feedback. Feedback may or may not be mapped to any area or opportunity. Unmapped feedback is common and can include irrelevant or neutral comments.

Key fields:

* Ingested\_ID
* Posted\_at
* Text
* Source
* Rating
* Account\_id
* Language
* ... (extra fields)

### areas.csv — Feedback to Area Relationships

This file lists feedbacks that have been associated with one or more Areas configured in your Birdie account.

A single feedback can be linked to multiple areas. Feedback not associated with any area will not appear in this file.

Key fields:

* Feedback Ingested ID
* Area\_ID
* Area\_Name
* (Also may contain Feedback ID, Area ID, Area Name as additional fields)

### opportunities.csv — Relationship Between Feedbacks, Areas, and Opportunities

This file lists cases where feedback has been mapped to both an Interest Area and a Business Opportunity.

Feedbacks with positive sentiment or without friction typically do not generate opportunities, so they may appear in areas.csv but not in opportunities.csv.

Key fields:

* Feedback Ingested ID
* opportunity\_id
* opportunity\_name
* (Also may contain Feedback ID, Area ID, Area Name, Signal Type)

### area\_opportunities.csv — Linking Areas and Opportunities

This file defines the many-to-many relationship between Areas and Opportunities. Previously this relationship was included in opportunities.csv; it has been moved into its own file for clarity and flexibility.

Each row represents a unique pairing between an area and an opportunity.

Key fields:

* area\_id
* opportunity\_id

## Linking and Rules

* All files use the field ingested\_id (in feedbacks.csv) and area\_id / opportunity\_id as linking keys between tables.
* You can join them using the following logic:

Examples:

* Feedback → Areas\
  feedbacks.ingested\_id = areas.ingested\_id\
  Find all areas mentioned in feedback.
* Feedback → Opportunities\
  feedbacks.ingested\_id → areas.ingested\_id → area\_opportunities.area\_id → opportunities.opportunity\_id\
  Trace which feedback generated specific opportunities.
* Area ↔ Opportunity\
  area\_opportunities.area\_id = areas.area\_id and area\_opportunities.opportunity\_id = opportunities.opportunity\_id\
  Link opportunities to their respective areas.

## Typical Data Presence Rules

* A feedback may appear only in feedbacks.csv if it hasn’t been mapped to any area or opportunity.
* A feedback may appear in areas.csv but not in area\_opportunities.csv if no opportunity was identified in that area.
* A feedback appears in all four files if it is linked to both an area and an opportunity.

## Additional Fields

The following additional fields are present in the CSVs but are typically used for internal or metadata purposes:

feedbacks.csv

* ID, Batch ID, Ingested At, Updated At
* Messages First Posted At, Messages Last Posted At, Total Messages
* Accounts, Custom Fields, Channel, Kind Name
* Source Alias, Status, Priority, Subject, Category, URL

areas.csv

* Feedback ID, Area ID, Area Name

opportunities.csv

* Feedback ID, Area ID, Area Name
* Opportunity ID, Opportunity Name
* Signal Type

## Diagram — Birdie CSV Data Export Structure

Below is a conceptual diagram that illustrates the relationship between the CSVs:

```
+--------------------+
|    feedbacks.csv   |
|--------------------|
| ingested_id (PK)   |
| posted_at          |
| text               |
| source             |
| rating             |
| account_id         |
| language           |
| ... (extra fields) |
+--------------------+
         |
         | 1
         |────────┐
         |       |
  0..*   |       |   0..*
+--------------------+     +-----------------------------+
|      areas.csv     |     |   area_opportunities.csv    |
|--------------------|     |-----------------------------|
| ingested_id (FK)   |     | area_id (FK)                |
| area_id (PK)       |     | opportunity_id (FK)         |
| area_name          |     +-----------------------------+
+--------------------+               |
                                     | 0..*
                                     |
                                     | 1
                          +---------------------------+
                          |     opportunities.csv     |
                          |---------------------------|
                          | opportunity_id (PK)       |
                          | opportunity_name          |
                          | signal_type               |
                          | ... (extra fields)        |
                          +---------------------------+
```

{% endtab %}

{% tab title="Import" %}
Opening the exported CSV from Birdie in Excel can become a hassle. In order to properly import all the csv rows into a new Excel File, follow these steps:

{% stepper %}
{% step %}

### In a new Excel file, open the Data panel

Click the Data tab in the toolbar.
{% endstep %}

{% step %}

### Choose Get Data

Click the Get Data option.

![](https://tawk.link/685001d2e1d1cb19110409b6/kb/attachments/COEdWVnwj1.png)
{% endstep %}

{% step %}

### In the Import wizard, choose Text/CSV

Select the Text/CSV option in the import wizard.

![](https://tawk.link/685001d2e1d1cb19110409b6/kb/attachments/7jba3DrKdE.png)
{% endstep %}

{% step %}

### Browse and select your CSV file

Locate and select the CSV file you exported from Birdie.

![](https://tawk.link/685001d2e1d1cb19110409b6/kb/attachments/m2p8gWejWZ.png)
{% endstep %}

{% step %}

### Select the delimiter

If Excel doesn't detect it automatically, select Comma as the delimiter.
{% endstep %}

{% step %}

### Load the data

Click Load to import the CSV into Excel.

![](https://tawk.link/685001d2e1d1cb19110409b6/kb/attachments/9PsA9rYBlt.png)
{% endstep %}
{% endstepper %}
{% endtab %}
{% endtabs %}