Skip to main content
This section walks you through moving a Chunkr Parse or Extract integration to Extend. Both capabilities exist on Extend with the same core outputs: markdown and HTML content, bounding boxes, and structured JSON with citations and confidence. The task-based model maps directly onto Extend’s runs, so most migrations are a client swap plus field renames.

​
Migration at a glance

1

Create an Extend account and API key

Sign up, generate a key, and install the SDK. Set up your Extend account →
2

Learn the concept mapping

Tasks become runs, segments become blocks, results becomes value. Concept mapping →
3

Migrate Parse, then Extract

Swap the client calls and update how you read the output. Parse → and Extract →
4

Move polling and webhooks

Replace polling loops with create_and_poll and re-point webhook endpoints. Production handling →
5

Validate on your documents

Run a representative sample through both systems and compare. Extend’s evaluation sets can automate this for extraction.

​
Guide

Concept Mapping

Side-by-side reference of every Chunkr concept and its Extend equivalent.

Getting Started

Account, API key, SDK install, and your first Extend call.

Migrating Parse

Chunks, segments, bounding boxes, spreadsheets, and configuration.

Migrating Extract

Schema rules, citations, confidence, and reading results.

Polling, Webhooks & Production

Async runs, webhook events, signatures, retention, and limits.

FAQ

Accounts, deployment, legacy API, and feature differences.

​
Resources