We have on several occasions been asked by customers to develop Guides content in our environment for eventual use in theirs. While the public preview version of the Content Migration Tool is better than nothing, we have encountered obstacles to using it in the real world. It requires simultaneous access to both the source and destination environment by the same person, and customer IT organizations are often unwilling or unable to provide a temporary Guides license for this purpose. It requires admin access to a local PC (which many customers restrict) and requires running a script that is unsupported by virtue of being in public preview against a destination production environment, which has generated anxiety also.

A preferable solution would be to have some sort of standardized export/import format and allow for Guides content to be exported from one instance (if the exporters has appropriate rights), then imported to another. Even the ability to export a guide's structure and text content (without media or objects) would be a significant benefit.