> Source: https://txtfetch.com/migrate > Plain-text twin — every page on txtfetch.com has one. https://txtfetch.com/text --- # Same document in. Here's what changes in your code. /compare told you why. This page shows the switch itself: the call you run today, the call that replaces it, and an adapter that keeps your pipeline untouched. ## What each spoke shows - Where you are today: the vendor call you run now, cited against their current docs. - The call that replaces it: one txtfetch request, in curl, Python, and JavaScript. - A drop-in adapter: a short function shaped like the vendor field your downstream code already reads. - A field-mapping table: their response field, the txtfetch equivalent, and a note where there isn't one. - What you lose, and what you gain, both stated plainly. - A cutover step: dual-run both calls and diff the output before you cut traffic over. pick a vendor **[Migrate from Unstructured.io](https://txtfetch.com/migrate/unstructured)** Its own Partition endpoint is now legacy. That's a migration moment either way. **[Migrate from LlamaParse](https://txtfetch.com/migrate/llamaparse)** Credit-metered tiers and a job to poll, for parsing you may not need. **[Migrate from AWS Textract](https://txtfetch.com/migrate/aws-textract)** A flat Blocks array, joined by hand. That join is the whole adapter. **[Migrate from Azure AI Document Intelligence](https://txtfetch.com/migrate/azure-document-intelligence)** The prebuilt-read model, minus the SDK, the poller, and the Azure resource. **[Migrate from Mindee](https://txtfetch.com/migrate/mindee)** Typed fields, not text. Read this one before you switch anything. partial migration ## Not every migration is a full swap Mindee returns typed fields, like an invoice total or a supplier name. txtfetch returns plain text. The Mindee page below says so directly, and does not pretend the two are equal. frequently asked questions **How is /migrate different from /compare?**: /compare answers why to switch: pricing and capability tables. /migrate answers what your code looks like afterwards: the call you run today, the call that replaces it, and a drop-in adapter. **Does every vendor here have a full migration path?**: No. Mindee returns typed fields txtfetch doesn't return. That page says so plainly and does not claim parity. **Are the vendor calls kept current?**: Each spoke cites the vendor's own docs with an accessed date, and a client version the call was checked against. Re-check before you copy a snippet past that date. **Do I have to give something up to switch?**: Usually, yes. Every spoke lists what you lose alongside what you gain, and links the full capability table on the matching /compare page. ## Swap the call. Keep the pipeline. Point your existing code at txtfetch, then diff the output before you cut over. [Get an API key →](https://app.txtfetch.com/signup) [See the migration guide →](https://txtfetch.com/migrate)