> For the complete documentation index, see [llms.txt](https://docs.dat-hub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dat-hub.com/overview/core-concepts/source.md).

# Source

This is the place from where you want to move your data.

This marks the beginning of the data migration process. All essential information to be transferred is initially stored here. From this point, the data will undergo the required steps and transformations to ensure its efficient transfer to the target destination.

Focusing on this key location marks the start of the  entire ETL operation. Here, we initiate procedures to ensure precise data capture, comprehensive analysis, and thorough preparation for migration. By doing so, we facilitate a seamless transition, reducing risks and errors while enhancing data integrity and security. Proper data handling at this stage sets the foundation for a dependable, robust, and resilient data migration strategy.

For an ETL pipeline configuration, the source refers to the Webpage, Database, or File from which data is moved. For example, if transferring data from AWS S3 to a Pinecone Vector database, AWS S3 is the source.


---

# 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.dat-hub.com/overview/core-concepts/source.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.