> For the complete documentation index, see [llms.txt](https://docs.middle.app/middle-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.middle.app/middle-docs/faqs/how-do-i-back-sync-data.md).
# How do I back-sync data?
## What is an ad-hoc sync?
A manual one-time execution of a sync where you define the record or datetime range data will be pulled from.
## How do I run one?
1. Open the account you want to run the ad-hoc sync in
2. Select the app connection you want to sync from the left-hand menu
3. Scroll to the record type you want to sync
4. Click **Run ad-hoc sync**
5. Depending on the sync type, you may be asked for more information (see below)
{% hint style="info" %}
Running an ad-hoc sync doesn't disable or change the automatic schedule for that record type. It's a one-off addition, not a replacement.
{% endhint %}
### Do I need to enter anything, or does it just run?
That depends on the type of sync:
* **Complete transfer:** no input needed. It grabs everything available from that endpoint
* **Primary key lookup:** you'll need to enter the specific ID of the record you want (for example, a single member's ID)
* **Recent record lookup:** you'll need to pick a date range
Selecting a date range to sync
### What if it fails?
Check the sync history entry first and it'll usually point to the cause. If the credentials look fine and it's still failing, reach out to support with the sync history link handy; it'll save time troubleshooting.
---
# 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://docs.middle.app/middle-docs/faqs/how-do-i-back-sync-data.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.
