> For the complete documentation index, see [llms.txt](https://help.form.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.form.io/form-building/submissions/importing-submissions.md).
# Importing Submissions
## Importing Submission Data
Whether you're migrating data between projects or importing data from an external database, the **Import CSV** button allows you to select a CSV file containing data from your local machine and import that data into the given Form or Resource.
{% hint style="warning" %}
When importing submissions through a CSV, each imported submission may trigger any configured [actions](/form-building/actions.md) as if that submission derived from a form user. When importing a significant number of submissions, consider temporarily disabling actions such as email notifications.
{% endhint %}
### **Configuring CSV Files**
In order to import data, a properly configured CSV File is required for the import to succeed. The CSV column headers need to map directly to the fields on the form you wish to import data to. Ensure that your column headers match the **Property Name** of your fields before importing the file.
Use the CSV rows to add different submission entries within the file.
### Importing File
When your CSV file is ready, click the **Import CSV** button within the data tab and select the file.
{% hint style="warning" %}
Selecting the **Replace all submissions** setting will replace all existing submission entries with the row data inside the CSV file
{% endhint %}
Once the import is complete, the Submission View table will reflect the CSV file entries.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.form.io/form-building/submissions/importing-submissions.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
