> For the complete documentation index, see [llms.txt](https://docs.movebot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.movebot.io/using-movebot/transfer-execution-and-cutover/deltas-and-changes.md).

# Deltas and Changes

### Keeping Your Data Up to Date

In active environments, it’s common for files to be added or updated during a migration. Movebot’s **Delta Migration** feature helps keep your destination up to date by copying **only the files that have been added or modified** since the last transfer.

***

### How Delta Migrations Work

Delta Migrations compare the **source and destination** using each file’s **modification time (modtime)**.\
Only files that are **new** or have a **more recent modtime** on the source will be transferred. This reduces duplication and speeds up the process by skipping files that haven't changed.

> **Important:**\
> Movebot does **not delete or move** files at the destination.  \
> \
> If you rename, move, or delete files or folders in the source, those changes will **not** be reflected in the destination. \
> \
> To avoid duplication or confusion, we recommend avoiding major restructuring during the migration process.

***

### Enabling "Always Use Delta"

To enable Delta Migrations across all runs:

1. Go to **Step 4** in your project settings.
2. Enable the **“Only Include Changed Files/Objects”** option.

This ensures Movebot will compare the source and destination before each transfer and skip any files that haven’t changed.\
Note: This option may increase **scan time**, but reduces **transfer time** by focusing only on what’s changed.

***

### Running a Delta Migration Manually

You can manually launch a Delta Migration at any time. Here’s how:

1. Open your project.
2. Select the job(s) you want to run a Delta for.
3. Click **Launch Scan or Transfer**.
4. Choose **Start Delta Migration**.<br>

Delta runs may take slightly longer to scan but are **much faster during the transfer stage** than full migrations. They can be run as often as needed and are particularly helpful for:

* Catching files that were created or updated during a prior transfer
* Cleaning up certain error types, such as:
  * **Unknown errors**
  * **File-not-found**
  * **Checksum-mismatches**


---

# 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.movebot.io/using-movebot/transfer-execution-and-cutover/deltas-and-changes.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.