Migrating GroupShare termbases

I might be missing something obvious but until I figure it out, can someone tell me how to migrate termbases from GroupShare 2015 to GroupShare 2017?

The only way I've found to do this is

  • Open the (GroupShare 2015) server-based termbase in MultiTerm Desktop
  • Export the termbase - only option is XML (why not SDLTB?)
  • Create a new file-based termbase
  • Create a new (GroupShare 2017) server-based termbase
    • using the newly-created file-based termbase as the definition
  • Import into the new termbase using the XML file

This seems tedious and time-consuming - we have a few hundred termbases to migrate.

Please tell me that there's an easier migration method.

Parents
  • Hi Andrew,

    No need to go the route you describe. At the end of the installation process will pop up called the "Termbase migration wizard" which will allow you to place TBs in Organizations. If it didn't pop up automatically for whatever reason, you can launch it manually: C:\Program Files (x86)\SDL\SDL Server\SDL Multiterm\Multiterm14\MigrationWizard.exe

    Note: We strongly recommend to use our Professional Services to perform the upgrade to increase the likelihood of everything working correctly and ensuring ongoing support.

    Thanks,
    Luis

    Best regards,
    Luis Lopes | Principal Product Manager | RWS | (twitter) @Luis___Lopes |

  • Hi Luis,

    The Migration Wizard didn't run at the end of the installation. Nor does it run when I double-click it or try running it from a command prompt. Nothing happens, the computer just stares back at me.

    We're in the process of arranging for SDL personnel to upgrade our test/development GroupShare installation but in the meantime - so that we could get started with some integration work and testing - this was a clean install on a new VM and a clean DB.
  • Hi Andrew,

    Right, that was the info I was missing. If it's a clean install it won't pop up as there are not termbases to migrate.

    The process would then be:
    - Export to XML
    - Save Termbase definition (xdt)
    - Create a server-based termbase using xdt file
    - Import XML

    No need to go through a file-based termbase.

    There are ways to copy the Termbases on SQL level but I wouldn't recommend this.

    Thanks,
    Luis

    Best regards,
    Luis Lopes | Principal Product Manager | RWS | (twitter) @Luis___Lopes |

Reply
  • Hi Andrew,

    Right, that was the info I was missing. If it's a clean install it won't pop up as there are not termbases to migrate.

    The process would then be:
    - Export to XML
    - Save Termbase definition (xdt)
    - Create a server-based termbase using xdt file
    - Import XML

    No need to go through a file-based termbase.

    There are ways to copy the Termbases on SQL level but I wouldn't recommend this.

    Thanks,
    Luis

    Best regards,
    Luis Lopes | Principal Product Manager | RWS | (twitter) @Luis___Lopes |

Children
No Data