> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/build/v1/move/mode.md).

# Data movement

A type defines how Nilus moves data: in scheduled chunks, as a stream of row-level changes, or as a continuous flow of events. The type is the one real decision in Move, and it follows from two questions: how fresh must the data be, and what does the source expose?

| Type                                       | Use it when                                                                                                          | Freshness        |
| ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------- | ---------------- |
| [Batch](/build/v1/move/mode/batch.md)      | Periodic full or incremental loads are acceptable, and the source is a database, warehouse, SaaS API, or file system | Minutes to hours |
| [CDC](/build/v1/move/mode/cdc.md)          | You need every insert, update, and delete from a transactional database, without full reloads                        | Near real-time   |
| [Streaming](/build/v1/move/mode/stream.md) | The source is a message broker (Kafka, NATS) producing continuous events                                             | Near real-time   |

All three share the same manifest shape: a `nilus` resource naming a source, a sink, and the type in `spec.type`. They differ in what the source must support and how the data lands. Refer to the specific page created for each type.

When in doubt, start with [Batch](/build/v1/move/mode/batch.md). It has the widest source support and the simplest setup.


---

# 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://v2.dataos.info/build/v1/move/mode.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.