> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chunkr.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrate to Extend

> How to move a Chunkr v1 integration to Extend

The full guide for moving to [Extend](https://extend.ai) lives in the current documentation. It applies to v1 integrations as well: the v1 `TaskResponse` output (chunks containing segments with `segment_type`, `bbox`, and `content`) has the same structure as the current API, so the Parse and Extract mappings carry over directly.

<CardGroup cols={2}>
  <Card title="Migration overview" href="/pages/migrate-to-extend/overview" icon="arrow-right-arrow-left">
    Step-by-step migration plan.
  </Card>

  <Card title="Concept mapping" href="/pages/migrate-to-extend/concepts" icon="table">
    Every Chunkr concept and its Extend equivalent.
  </Card>

  <Card title="Migrating Parse" href="/pages/migrate-to-extend/parse" icon="crop-simple">
    Segments to blocks, bounding boxes, chunking, spreadsheets.
  </Card>

  <Card title="Migrating Extract" href="/pages/migrate-to-extend/extract" icon="brackets-curly">
    Schema rules, citations, and confidence.
  </Card>
</CardGroup>

## v1-specific notes

| Chunkr v1 | Extend |
| :- | :- |
| `chunkr.upload(file)` | `client.parse_runs.create_and_poll(file={...})` |
| `chunkr.get_task(task_id)` | `client.parse_runs.retrieve(id)` |
| `task.poll()` | Built into `create_and_poll` |
| `task.update(config)` | Create a new run with the new `config` |
| `task.cancel()` / `task.delete()` | `client.parse_runs.cancel(id)` / `client.parse_runs.delete(id)` |
| `task.html()` / `task.markdown()` / `task.content()` | Join `chunk.content` across `run.output.chunks` |
| `Configuration(...)` object | `config` dictionary on the request |
| `pipeline`, `segmentation_strategy`, `ocr_strategy` | See the [configuration mapping](/pages/migrate-to-extend/parse#configuration-mapping) |
| Self-hosting (Docker Compose, Kubernetes) | Extend offers BYOC and Hybrid deployments; see the [FAQ](/pages/migrate-to-extend/faq#deployment) |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.