We need to migrate a large number of documents from another collaborative platform to Clearspace. I've been pulling together a rough import tool using the CS webservices API, seems pretty straighforward. Some of the files are word, PDF, etc -- those I can upload as straight binary documents. Others are HTML and text documents, and I'd prefer to recreate those as Clearspace text documents. But I've not been able to figure out the right format of the "body" parameter for the createDocument method for HTML documents. When I pass the straight source markup, the tags gets escaped (e.g. show up in the rendered document view). I tried wrapping the content in a "<div class='jive-rendered-content'>" element, which is how document bodies are returned when an existing Clearspace document is queried, but that doesn't seem to have any effect.

Is there some particular way to tell Clearspace to accept HTML markup without escaping it, as if the user had used the Clearspace editor directly? I'm aware that there may be some loss of fidelity from this process, e.g. if the source document used lots of custom formatting, illegal tags, etc., these may not be supported in the resulting Clearspace document, but we can clean these up manually once the documents have been loaded.

Peter