Migration guides

Practical guidance for teams moving to Ironmark from an existing authoring tool or content repository. Each guide covers what stays the same, what changes, and what the actual import path looks like.

From an existing authoring tool

From PTC Arbortext

Structured XML travels straight across. What changes when the review/publish/deliver flow moves into the same tool.

Read →

From Adobe FrameMaker (XML)

XML content preserved; layout-specific formatting maps to publish stylesheets.

Read →

From desktop XML editors generally

Oxygen, XMLSpy, MadCap, others. What you keep, what you lose, what shows up.

Read →

From SGML sources

Convert SGML to conformant XML on ingest. What the auto-conversion handles vs what needs a hand.

Read →

From an existing repository

From an IADS archive

Import a Team-IADS package as a fresh project. Preserves TOC, DMs, graphics, and DTD folder for round-trip parity.

Read →

From an existing CSDB

Bulk import DMs, graphics, and BREX from a Common Source Database. Applicability filters translate to Ironmark's model.

Read →

← Back to home