Skip to main content

About Importing and Exporting

Paligo lets you import existing content in several formats, including HTML, DocBook, DITA, Microsoft Word, Paligo Export Format (XML), Atlassian Confluence, MadCap Flare, Zendesk Guide (help center) and more. Some can be imported directly, but in other cases, you will need first to convert the content into a different format and then import that.

There are always some limitations regarding what can be imported from one format to another; some import formats will work better than others. Generally, the more structured the legacy format, the more complete the import will be.

When an import is too big, Paligo recommends dividing the import into smaller packages. Variable sets that have been included in previous imports, will get duplicated, unless a variable set ID is entered in "Match with existing variable set", see Use the Import Wizard and Find a Variable Set ID.

However, you can only match one variable set, so if there are multiple in the import, the others will still be duplicated. Therefore it might be a good idea before exporting the content, to either:

  • Merge the variable sets into one

  • To use one variable set per import package



An import is not the same as a migration, but a tool that speeds up the process of migration significantly. But every import must always be checked manually to make sure no content is missing or incorrect in any way.


When importing content, Paligo will not automatically create a snapshot of the imported content. Paligo recommends you to always create a Create Snapshot in Resource View of the imported content, to have an archived version to compare with the changes you make.