Translation is one of many areas where a little redundancy can be better than the most concise representation.

It helps to know a little about how translations works.  Anything in trans/blocktrans/gettext gets collected and displayed to human translators at https://www.commcarehq.org/rosetta/.  *Unless the dev specifically passes a static "context" to each call, every instance of any given simple string gets translated the same throughout the application.* For blocktrans, any parameters are displayed verbatim to the translator, which helps provide context.

In addition, we should consider the following possibilities for the languages that we are translating stuff into:
- "to" can be translated in many different ways depending on the context
- "X to Y" sounds incorrect or very bad compared to "from X to Y"
- "to Y from X" is the only way you can correctly say it

Given that, I think it's obvious what one or two good solutions here would be, and it's the only thing from this comment I'm not going to rewrite after I ran out of battery and hibernation on linux failed to work.

Another thing is whether it's even necessary to include this, or to include it here.  I think two design principles apply, one of which I've read and one of which I'm making up (guess):
- use structure instead of prose to convey information because it's easier to process (say, some sort of item: value bullet list)
- try to avoid including dynamic information in navigation text -- it's less noisy to have more minimal, static navigation text