Structured FrameMaker to DITA Conversion

This guide is for teams who already author element-based content in Structured FrameMaker and want to carry that investment into the open standard. It explains how DocentraX Structured FrameMaker to DITA conversion reads the HTML export as the book it was — the contents page you published defines the order — and turns it into clean, valid DITA with chapter reading order preserved and no text dropped. The one thing that matters most is that the HTML export flattens your EDD-driven model, so a hand pass loses chapter order and maps the same element two different ways; a deterministic conversion that reads the export as a publication does not.

Structured FrameMaker already gave you element-based authoring — you were most of the way to structured content. But an EDD-driven Frame model is not DITA, and when you export it as HTML you get a set of chapter pages that still are not a reusable content source. A Structured FrameMaker to DITA conversion turns that exported HTML into clean, valid DITA with chapter reading order preserved, so the structure you already invested in carries forward to the open standard.

Why convert Structured FrameMaker to DITA

Structured FrameMaker is a capable but closed ecosystem. Your content model lives in EDDs and templates that only Frame understands; reuse and conditional publishing follow Frame's rules rather than the industry's. Moving to DITA makes your structure portable — governed by an OASIS open standard, publishable to every channel you deliver, and reusable in any modern CCMS, whether that is Heretto, Paligo, IXIASOFT or Tridion Docs.

The temptation is to treat this as a quick manual tidy-up, precisely because the content is already structured. It is not: the HTML export flattens the model, and a hand pass loses chapter order and maps the same element two different ways in two different chapters. A deterministic Structured FrameMaker to DITA migration that reads the export as a book rather than as a folder of files protects the investment you already made, and runs through the same DITA conversion pipeline as every other source.

You already did the hard part — authoring structured. DITA is where that structure stops being Frame's and starts being yours.

What our Structured FrameMaker to DITA conversion does

We read your export the way a reader opens it. The contents page you published is what defines the order, so chapter one is chapter one and appendix C lands after appendix B — not wherever an alphabetical file listing happens to drop them. That single decision is what separates a conversion you can ship from one your writers have to re-sequence chapter by chapter before anyone can even review it.

From there the transform rebuilds real DITA semantics rather than wrapping the export in DITA clothing:

Your heading levels become a genuine topic hierarchy, and the procedures your readers follow become tasks — real steps, not paragraphs that merely look like steps.
Tables are rebuilt as CALS tables, so spans, headers and column widths survive into your CCMS instead of collapsing into a grid nobody can maintain.
Notes, cautions, cross-references and images come back as real DITA elements your publishing pipeline already knows how to render.
Special characters survive the trip, and typographic spacing is a decision you get to make: non-breaking spaces are normalised to ordinary spaces for clean XML by default, or preserved exactly where your typography depends on them.
How aggressively topic structure is inferred is tuned to your content rather than fixed, and your style mapping is configuration we agree with you, not code somebody rewrites each time.

Text is never dropped. Where the source genuinely cannot tell us what something was, structure degrades gracefully and the content survives — never the other way round.

The 5-stage Structured FrameMaker to DITA migration lifecycle

Analyse — your export is read as a publication: chapter reading order comes from the contents page you published, and every topic, image, style and link is inventoried before anything is transformed.
Transform — chapter structure and headings become a DITA topic hierarchy; procedures become tasks, tables become CALS, and notes, cross-references and images are rebuilt as real elements.
Enrich — your metadata, keys, IDs and naming conventions are applied, and you can optionally run Knowledge Fabric to write keywords into topic prologs.
Validate — the completeness check runs against your own schema: DTD conformance, links, conref and keyref resolution, image references, duplicate ids and keys, and circular maps.
Deliver — topics and a map or bookmap in the structure your platform expects, with folder layout, assets and references intact and ready to import.

Generic versus customer-specific Structured FrameMaker to DITA conversion

A generic run gives you valid DITA with inferred structure, generic topic types and generated IDs — a correct start, and enough to prove every word made the journey.

A customer-specific Structured FrameMaker to DITA conversion aligns that output to your standard. Concretely:

Your Frame elements and paragraph styles land on your specialization's elements — a caution style becomes a real caution note, a step style becomes a step inside a task.
Frame conditional text is the one claim we will not make: it does not survive into an HTML export, because the export is a single build with the conditions already applied. If you publish by audience or product, we re-establish that profiling with you in DITA — deliberately, not by pretending the export still carries it.
Content the export duplicated into every place it appeared is converged rather than copied forward: our Content Convergence pass keeps one master per repeated element and turns each occurrence into a conref, with a report that shows exactly the reuse it created.
IDs, filenames and folders follow your conventions, and the output validates against your DTD — the same rules your CCMS will apply on import.

Without that tailoring, the team reconciles element mapping by hand after delivery, which is the most expensive place to do it. With it, the DITA drops into your CCMS ready to use — and because the mapping is configuration we hold and reuse rather than a bespoke build each time, the tenth book behaves exactly like the first.

Where Structured FrameMaker to DITA transformation sits in the DITA industry

DITA gives you single-sourcing, conref and keyref reuse, conditional publishing and multi-channel output — once content is migrated cleanly. For Structured FrameMaker the common routes are manual re-authoring, a one-off script, or a desktop tool, and all three tend to lose the one thing an HTML export makes hardest to recover: the order the book was in. A DocentraX Structured FrameMaker to DITA transformation reads the export as the publication it was — identified by the contents page the export carries — and infers topic structure from your headings rather than from filenames. It sits alongside the rest of our DITA migration services, so a mixed FrameMaker estate — structured and unstructured, book and help — converges on one standard.

Your concern	How we answer it
"We already author structured — is this just a relabel?"	No: the HTML export flattens your model, so we rebuild real DITA topics, tasks and CALS tables from it rather than renaming whatever the export happens to contain.
"Chapter order must not shuffle."	Reading order comes from the contents page of your own export, not from a file listing, so chapters and appendices stay in the sequence your readers know.
"We need our specialization, not generic DITA."	A customer-specific mapping takes your Frame elements and paragraph styles onto your specialization, and the output validates against your DTD.
"How do we verify the result?"	The completeness check audits links, conref, keyref and image references against your schema before anything is delivered.

Your structure, finally portable

Your structured authoring investment carries forward into an open standard: single-sourced, reused with conref and keyref, conditionally published, and delivered to every channel your audience uses. If you also publish those books as online help, the same pipeline handles FrameMaker WebHelp to DITA conversion, and it covers RoboHelp to DITA conversion too — so every Frame and help source in the estate lands in one consistent DITA. The model becomes yours, not the tool's.

Frequently asked questions

How do you convert Structured FrameMaker to DITA?

DocentraX reads your HTML export as a publication rather than a folder of files: the contents page you published defines chapter order, and headings, procedures, tables, notes and images are rebuilt as real DITA topics, tasks, CALS tables and elements. The output is validated against your own schema before delivery.

Is Structured FrameMaker to DITA conversion just a relabel since the content is already structured?

No. The HTML export flattens the EDD-driven Frame model, so DocentraX rebuilds real DITA topics, tasks and CALS tables from it rather than simply renaming elements. That is what protects the chapter order and the structure you already invested in.

Does the conversion keep chapter order from the FrameMaker HTML export?

Yes. Reading order comes from the export's own contents page rather than from how the files happen to be named or listed, so chapters and appendices land in the correct sequence. Text is never dropped, and structure only degrades gracefully where the source genuinely cannot tell us what something was.

What is the difference between generic and customer-specific Structured FrameMaker to DITA migration?

A generic run gives valid DITA with inferred structure and generated IDs. A customer-specific run maps your Frame elements and paragraph styles onto your specialization, follows your ID and folder conventions, and validates against your DTD. Conditional text is the honest exception: an HTML export is a single build with the conditions already applied, so we re-establish profiling with you in DITA deliberately rather than pretending to recover it from the export.

Which files does the Structured FrameMaker to DITA converter need?

The complete HTML export as FrameMaker produced it — the whole folder, or a zip of it, with its images and, critically, the contents page that lists your chapters in order. That page is how the export is recognised and where chapter order comes from, so an export delivered without it will not be identified; if yours lacks one, tell us and we agree the reading order another way before the sample runs. Add your DTD or specialization and any existing style mapping, and you get DITA topics and a map or bookmap back.

Related guides

Send us 25 pages. The messier, the better.

We'll convert them to DITA free of charge — through the real pipeline, not a demo — and review the output with you. Then we'll discuss pricing one-to-one.

Get your free 25-page sample