Customer-story reference · December 2016
Moving the source is only part of multilingual migration.
Bluestream’s original post pointed to a WhP article about Margaret Devere’s work migrating Micro Motion’s Model 5700 transmitter manual to XDocs. The credited excerpt is retained below.
Figures reported in the original WhP excerpt
From WhP: a multilingual migration
Excerpt credited to WhP, as published in December 2016.
from WhP, http://www.whp.net/en/6-tips-migrate-multilingual-content/ In 2016, Margaret Devere, Information Architect at Micro Motion, a business unit of Emerson Automation Solutions, set off on a challenging task: migrate the manual for the Model 5700 transmitter from a SharePoint-based CCMS to the XDocs CCMS from Bluestream. The 350-page manual had been written in English, and translations existed for the 600+ DITA topics, but, due to system issues, the translations had not been published. Read more…
Editorial context · October 2026
What the original excerpt tells us
WhP’s excerpt names Margaret Devere as Information Architect at Micro Motion, a business unit of Emerson Automation Solutions. It describes a content migration from a SharePoint-based CCMS to XDocs. Although translations already existed, system issues had prevented publication.
Plan a multilingual migration around relationships
For a project like this, first map each source topic to its translations. Then record the publications, supporting assets, and review status for that content. A file count alone cannot show whether a language edition is ready to build and check. The questions below help test that inventory.
| Inventory item | Question to answer |
|---|---|
| Source and target topics | Which translated topic corresponds to each source topic, and which source revision does it represent? |
| Publication structure | Which maps or other assembly instructions define the intended publication for each language? |
| References and assets | Are linked topics, images, and other required resources available in the target environment? |
| Readiness | Which language editions can be built and reviewed, and which have unresolved gaps? |
Prove an output before declaring the move complete
Start with one small publication and one target language. Next, follow the content through import, assembly, and review. Check the output’s references, images, navigation, and terminology. Resolve or record any gaps before extending the migration. Together, these checks show whether the destination supports the content’s intended use, beyond simply receiving its files.
Archive source: Part of the solution, 5 December 2016.