> For the complete documentation index, see [llms.txt](https://docs.countercyclical.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.countercyclical.io/extras/imports/formatting-guide-for-imports.md).

# Formatting Guide for Imports

{% hint style="info" %}
This page refers to the initial file that you upload on the first step of Imports.

Companies imported into Countercyclical are only available through the workspace it was imported into.
{% endhint %}

Following these guidelines will ensure that your data imports correctly and maps seamlessly with the platform’s existing structure, allowing you to use your own custom data alongside our powerful research and valuation tools.

***

## General Guidelines

1. **File Type**: Countercyclical accepts `.csv` and `.xlsx` file formats for Imports.
2. **File Size**: Each file can contain up to 1,000 rows. For bulk imports exceeding this limit, please split the data into separate files.
3. **Encoding**: UTF-8 encoding is recommended for best compatibility.
4. **Headers**: The first row in your file must contain the column headers.
5. **Date Format**: Use any valid Date Time format (e.g. `DD-MM-YYYY`, `YYYY-MM-DD`, etc.) for date fields to ensure consistency.

***

## Required Columns for Company Imports

Each import type requires a specific set of columns. Below are the details for the main types of financial data imports:

### **Company Metadata**

Required Columns:

* **`Company Name`** - Unique name identifier for each company.
* **`Website`** - Website/URL of the company

{% hint style="info" %}
The website field is essential for providing users with the best data enrichment experience possible. Learn about how Countercyclical enriches data here: [Enrichment Data](/extras/enrichment-data.md)
{% endhint %}

***

## Column Mapping Options

Countercyclical allows users to map their custom column names to the system's standard format. During the import process, you will have the opportunity to review and map your data fields.

### Supported Column Mapping

Countercyclical recognizes the following mappings for key company fields. If your columns have different names, you can manually map them during the import process:

| Platform Standard | Required (Y/N) | Data Type |
| ----------------- | -------------- | --------- |
| `Name`            | `Yes`          | Text      |
| `Website`         | `Yes`          | Text      |
| `Sector`          | `No`           | Text      |
| `Industry`        | `No`           | Text      |
| `Description`     | `No`           | Text      |
| `City`            | `No`           | Text      |
| `State`           | `No`           | Text      |
| `Country`         | `No`           | Text      |
| `Address`         | `No`           | Text      |

***

## Data Verification

### **Validation**

After uploading your file, the platform will automatically validate each row based and the column mappings for steps 1 & 2.

### **Data Preview**

Preview the imported data before finalizing to confirm mappings.


---

# 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.countercyclical.io/extras/imports/formatting-guide-for-imports.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.