I am currently developing a migration tool to convert PowerDocs templates from OpenText Content Manager to OpenText Core Communications (Communications CA).
As part of this effort, I have been reverse engineering Core Communications export packages to understand how templates and components are represented in their source files. The goal is to accurately generate equivalent structures during the conversion process.
While working with the export packages, I found that interpreting the JSON files is manageable to some extent. However, understanding the .bin files located in thecontent folder has proven to be significantly more challenging. In many cases, the associated JSON field names do not clearly indicate what the corresponding binary data represents or how it should be constructed.
This makes it difficult to reliably map and generate the correct fields during migration.
Is there any official or internal documentation available that explains the structure of Core Communications export packages, including detailed descriptions of fields and their purposes across all component source files (especially the .bin content)? Any guidance or references would be greatly appreciated.
