Transfer of term relationships from asset (column) of one DB host system to an asset (column) of another DB host system

===============
Problem Scenario
===============

An organization has recently migrated one of their databases (let's say, they shifted from SQL to PostgreSQL). As a result there have been changes to the host name of the DB, DB name, Schema name etc.
Now, they need to transfer all of their glossary information that's pointed to the assets of old database (SQL) to the assets on new database (PostgreSQL).

For this above scenario, we currently have the option to export the existing (old) common metadata using istool export command and then import (istool import) the same common metadata with the help of a mapping file (The mapping file helps to change your existing hostname, DB name, Schema name etc. to relevant new names). We can also transfer all the terms assigned to the old assets to the new assets, thanks to the mapping file. BUT, the problem is when you have a huge glossary size, we either end up with n number of duplicate identity errors or some invalid link point errors and there seems to be not a way to work around these errors. So eventually, we have to go through the manual work of removing the term relationships on the old host and add them onto the new host. Imagine what the time spent looks like when we have hundreds and thousands of term relations to deal with!

Would it be possible to introduce a feature or a command line tool to transfer these term relationships (without hassles) which helps in case of any major database migrations?