While there is not really any fully vetted "migration paths" to MF connect yet there are a few things that you can do to make sure that you don't get duplicates.
- The first way is to use a "type rule" in MF Connect and in that query you can specify that you only want to synchronize stuff that was created on this day forward, that way you "leave behind" all the old issues and don't even include them that way you do not get duplicates.
- Another way would be to use the "Cross References" feature in MF connect to import your old link definitions. There is not any automated way to do this but you could probably come up with a script to do it. First you would find out what pairs were linked (you could check ALM sync PostgreSQL database). Then export the cross references template in MF Connect, then each record pair that you want to import would be defined with an "add" tag, once you put in all the mapped entity pairs you would then import the cross references. Since it is XML you would have to have the format just right.
- The last way could be a hybrid approach, for instance lets say you don't want to sync any closed tickets anyway so you could have a "type rule" in place that says only to sync the entities that are NOT Closed. Then in the cross references you would only need to import record pairs that are not in the closed state since it is not even going to try to sync records that are closed.
Note: If you decide to use the cross references import keep in mind that the MF tool is always going to be the "source" in this case