With the exceptions listed below, all objects created and used by FileNet applications will be supported by the CS Export functionality.
NOTE When your CS system has documents filed in multiple folders (eg; multiple references of the same Document ID), it is recommended you first export all of your folders, but choose to not select any document classes. Then select the documents to be exported by using the docclass filter in the Doc Classes to export dialog and perform a second migration.
IMPORTANT Content Services Custom Properties that have a default value set at the property level (or at the class level) in CS will have that default value set during the export process. The Required Flag will not get migrated to the Content Engine. Also, after the migration is completed, the default can be set manually. It should be noted that a default should not be set to a value that is not in a Controlled Vocabulary List (CVL) assigned to this property.
NOTE This is to eliminate the possibility of errors where a custom property has a default value set to a value that is not in the Controlled Vocabulary List (CVL) assigned to the property.
CAUTION When running CS Export and exporting a CS document using a Doc class that has an integer custom property with a CVL assigned and the property is blank (null) on the document, CS Export generates an error saying "Error Setting custom property" and the detail message states "FileNet P8 Content Engine DMA Core Library - The value specified for property 'SVCPIntegerItem01' is not one of the permitted values." You can view the errors in the CS Export log files.
Exporting the following Content Services objects are not supported:
Stored searches are exported but are not functional.
NOTE When CVL's are imported from Content Services to Content Engine, a Date CVL is converted into a string. There is no option to add Date CVL's so importing a Date CVL is not possible.