Knowledge migration and transformation capabilities

1. Source material

Evaluate existing knowledge files such as HTML, Word, PDF, Markdown, text, spreadsheets, CSV, JSON or ZIP archives. Parsing and rich-asset preservation depend on the actual files supplied; use representative samples to establish compatibility.

2. Bring your own target requirements

Provide real target examples, JSON/XML output samples, schemas or specifications. iluva uses this evidence to determine the target structure and mapping requirements. A platform name alone is not a substitute for a target specification.

3. Mapping and content fidelity

iluva never authors, rewrites, paraphrases, summarizes or invents source article content. The objective is to map existing titles, bodies, metadata and article elements into the target structure while preserving what the original article says. Verify wording, tables, lists, images, attachments and hyperlinks against the source before acceptance.

4. Validation and exceptions

Review required target fields, structural validity and unresolved links or missing evidence. Where an external link points to an article that was not provided, supply the referenced article when available; if a link is invalid, confirm any removal instead of silently discarding it.

5. Self-service evaluation

1. Register for the Beta.
2. Upload a small, representative set of real source articles.
3. Provide target output examples or specifications.
4. Review mappings, generated outputs and any exceptions.
5. Confirm output compatibility before expanding the migration.

There is no public, independently verified benchmark or customer case study claimed on this page. Evaluate the product using your own representative source and target files.

Start with 50 free items

The current Beta includes up to 50 free knowledge Processing Items, subject to program terms. Paid processing is disabled during Beta.

Already registered? For project-specific questions and ticket history, sign in and use Ask Ted.