A Dragon word-list export does not transfer custom commands. If specialized terms appear in a new profile but your reusable text commands are missing, inspect the command export process rather than importing the vocabulary file repeatedly.
This guide covers a small, authorized transfer using Dragon desktop command management. Commands can contain actions as well as text, so only import material from a trusted owner whose purpose you understand. Do not use downloaded command packs as a shortcut to restoring a known setup.
Inventory what needs to move
Make three separate lists: vocabulary entries, custom voice commands and general profile configuration. A command that inserts a paragraph is not simply a long vocabulary word. Likewise, a command that acts on a window may rely on an application that is absent on the destination computer.
Nuance's custom command management guidance documents exporting selected commands through the Command Browser. The documented procedure produces a command file, distinct from the TXT or XML used for vocabulary lists.
Select only the intended commands
Review the command names and groups before exporting. A broad selection can include obsolete actions or material intended for a different department. Create a small initial transfer containing one harmless Auto-Text command so that the recipient can validate the process before a larger migration.
Review stored content
Do not include passwords, private records or confidential details in custom commands. Inspect reusable text and any application actions with the command owner. Having permission to use Dragon does not automatically authorize sharing every command from another person's profile.
Export through the supported command interface
Open the source profile and Command Browser, then select the approved commands and use its export function. Record the filename and the actual destination folder. Avoid overwriting an older migration file without confirming whether it is still needed for rollback or audit purposes.
The official Command Browser reference explains its management functions and notes that managed commands may be controlled by an administrator. If commands are disabled centrally, a local transfer is not a route around that decision.
| Asset | Transfer question |
|---|---|
| Custom vocabulary | Which word-list format and properties are required? |
| Auto-Text command | Does the recipient need this exact reusable content? |
| Action or scripting command | Are its dependencies understood and authorized? |
| Managed command set | Does the administrator distribute it centrally? |
Import selectively on the destination
Open the intended destination profile before using the documented command import operation. Inspect the offered selection rather than accepting every command automatically. Keep an inventory of what was imported so you can distinguish existing commands from the new additions.
Treat name collisions deliberately
A matching spoken name may already trigger a different action in the destination. Stop and compare the definitions before accepting a replacement or combining files. A successful import that silently changes familiar behavior can be more disruptive than a command that remains visibly missing.
Check application dependencies
For a text insertion command, verify the target editor and formatting. For an action command, inspect the application and window context it expects. Do not execute an unfamiliar script merely to see what it does, particularly in a session containing real customer documents or open administrative tools.
Validate a harmless example first
Open a blank sample document and invoke the approved test command. Confirm the inserted wording and any formatting, then save and reopen the sample if formatting matters. Only proceed to a broader import after the command owner has confirmed the expected behavior.
This is a functional migration check, not evidence that every command will work across all Dragon editions or application versions. Record differences and consult the help matching the actual source and destination products when necessary.
The PowerMic comparison addresses equipment separately. A missing command definition is not fixed by changing the audio input device when Dragon already recognizes the spoken phrase.
Have the recipient repeat the harmless command without assistance. This confirms that the handoff includes a usable invocation, not just a file copied successfully.
Keep the original export and source profile available through the approved retention process until migration is accepted. The handoff is complete when vocabulary and commands have each been transferred by their own supported route, the selected commands behave as intended, and their scope and ownership are clear to the receiving user.
