Convert Content from a Previous Version

You can convert content from a previous version of the Developer to the current version. The conversion process imports your content into the Library you are currently using and leaves it intact for use in the previous version as well. This process may take some time depending on the size and complexity of the content you convert.

Note: You can convert content from version 2.5 and above. You do not need to convert content from version 9.1 and above.

During the conversion, various folders and subfolders are created in the Library to store the converted documents such as modules, sections, topics, web pages, packages, glossaries, and so on. You should review the content conversion logic for more information on how content is converted.

Use the Library to display the folders and documents that result from the content conversion.

Before you convert content, you need to know the location of the OnDemand.ini file that contains references to the previous version content that you want to convert.

Warning! Before you convert content from a previous version, all content authors should be logged out of the Developer environment that contains the content to be converted.

The following are general guidelines for converting content from a previous version into a content Library:

• You can convert multiple titles from a previous version into one content Library. You can also convert content from multiple Developer installations into one Library.
• Content in multiple languages can be converted into one content Library.
• You can convert the same content multiple times. If you convert the same title from a previous version multiple times, a number is appended to the "root title" folder name in the Library. For example, if you convert a title called "My Content", a root title folder with the same name is created in the Library. If you convert this title again, a new folder called "My Content_1" is created and the original "My Content" folder is left intact. When you convert content multiple times, you are creating duplicate documents in the Library.
• TPC and Saved Publishing Setting (.xos) files are not converted.
• Published content is not converted. You should republish your content after conversion is complete.
• Unused content such as URLs or keywords that are not assigned to topics is not converted.
• The MRU list in the Topic Editor and Tools, Options settings are not converted.
• Template and publishing style customizations are not converted.

Multi-user Considerations

After you convert content from a previous version, the converted content is stored locally and checked out to you. To make the converted content available to other authors in a multi-user environment, you must make sure you are online in the Developer and then you can check in the converted content. After you have checked the content in, other authors can proceed to check out the content they want to use and edit. To ensure that all converted documents are checked in, it is recommended that you select the main folder and check in the content. However, note that, if the content you converted resulted in the creation of new packages for custom icons, the packages are not checked in unless you explicitly check them in from the System\Icons\Custom folder. You can also use the Check in All command to check in all content in the Library at one time.

If you click the Keep checked out option on the Check In Comment dialog box during check in, the content is checked in and the version number increased but the document remains checked out and unavailable for edit by other users.

See Check In and Check Out Documents in Use the Developer in a Multi-user Environment for more information.