Read the conversion report before adopting the result.

Choose a supported source

Use the formats offered by your Center's import screen. Integrations can read GET /api/v1/import/formats and submit files through POST /api/v1/import. Check that list for the build you are evaluating instead of assuming that a filename extension guarantees support.

Review the converted documents and the report together. If the report asks for missing linked images, supply the matching files and run the conversion again.

Understand the four fidelity classes

The fidelity report grades object or mapping results using four classes. The values in parentheses are the contract's identifiers.

Class	Meaning	What to review
Exact exakt	The source construct maps one-to-one without loss under the importer's mapping rules.	Check the resulting content in the context of the complete label or workflow.
Approximated approximiert	A close mapping is possible, with a small semantic change.	Read the notes and decide whether the difference is acceptable for the task.
Annotated annotiert	The construct cannot be mapped automatically as intended; an annotation describes the outstanding issue.	Inspect the source reference, affected generated object where available, and suggested next action.
Unsupported nicht unterstützt	The construct is recognized but unsupported by the current conversion contract.	Decide how to handle that requirement before adopting the converted workflow.

Mapping coverage includes exact and approximated mappings. A high coverage percentage does not establish unchanged semantics or equivalent physical output. Read the individual results and compare representative rendered and printed examples.

Turn annotations into review work

An annotation identifies where the issue came from in the source and, when applicable, which generated objects it affects. Some findings concern the document or a variable rather than a particular object. Use those references to inspect the right place.

Annotations can also be grouped into credential issues, non-renderable constructs and fidelity differences. Those three issue groups are separate from the four fidelity classes above.

Reconnect required data sources through stored credential references, review missing artwork and inspect retained hints in the Designer. An open label import hint is a warning; it does not by itself block approval or printing. Independent validation and print requirements still apply.

Evaluate before rollout

1. Inspect the converted label

   Check dimensions, fonts, images, barcode data and longer or missing values. The report's mapping class is not a physical-print comparison.

2. Review automation behavior

   Confirm source access, field mapping, conditions, error handling and the intended printer. Separate a queued print request from its later delivery result.

3. Record decisions and deploy deliberately

   Resolve or document the findings that matter to your task, review the result with its owner and publish the chosen version when it is ready.

Explore the migration workflow → · Plan a representative migration → · Evaluate the output connection →