> For the complete documentation index, see [llms.txt](https://docs.motivewave.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.motivewave.com/user-guide/charts-1/importing-tick-data.md).

# Importing Tick Data

Historical tick data may be imported into MotiveWave™ by choosing ***Chart > Data > Import Tick Data*** from the top Console menu bar. 

Two types of data formats are supported:

* **CSV** – Comma Separated Values. This is a very common format for many historical data services. The format of the data file will be automatically detected when specifying files of this type.
* ASCII - Another popular and simple text-based file format.

<figure><img src="/files/SBfWbQhDFSuHKzyFWlZ5" alt=""><figcaption></figcaption></figure>

This dialog has the following elements:

* **Data Files** – Specify one or more data files by clicking on the Add button to left of the Data Files list.
* **Time Zone** – Choose the time zone for the input file. This is important for resolving the data/time values for each historical price bar in the input file.
* **Replace Existing Data** – Replaces data that is already in the local historical database.


---

# 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.motivewave.com/user-guide/charts-1/importing-tick-data.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.