The Deja vu experience

CATS comes in different shades, and it is not always easy for a human being to understand the soul and mind of a CAT.
So for the next project I think I will be trying out Déjà vu.
The first thing was to move my Studio TM, 450,000 TU:s to Déjà vu.
Studio can only export TM in TMX, not in Trados txt. And when trying to import the TMX, DVX just froze. So I had to import the TMX to Trados Workbench, then export again as txt, then import to DVX. The import into DVX took 12 hours.
But, otoh, the conversion of my RH-term that I maintain in Excel, and used to import in MultiTerm was very quick. The 20 000 entries 4 language database used to take half an hour to transfer in Trados, but the import into Déjà vu took 1 minute! And the import function was very easy to understand, and worked perfectly! So much easier to work with than MultiTerm.
As to AutoSuggest, the function I liked the most in Studio: Déjà vu has it, and it is actually more powerful.
You are not forced into pretranslate in Déjà vu, and you do not have to use Autopropagate.
The problem with number conversions is not there, as you can opt it out.
The learning effort is less; I have spent this Sunday with the conversions, and it seems to be very easy to get into the way Déjà vu works, although it is of course somewhat different than Workbench/Studio.
But, I would say that if you are to convert from Trados Workbench/TagEditor, it is probably as easy (or even easier) to convert to Déjà Vu.
This is of course only my first enthusiastic reaction to something new, but I have a strong feeling I will change to Déjà vu as my main tool and keep the Trados for conversion purposes.
I have not investigated the duplicate handling in Déjà vu yet, but there is a very good function that is missing in Studio; Déjà vu tells you without having to use Autopropagation, when you hit a repetition, which Studio does not. And this solves my proofreading problem of the mess I got in Studio in my old 40 000 word project. So I will actually run it again in Déjà vu. As the segmenting differs, it will take a day extra, but that will be worth it as I do not have to worry about changing codes and I can easily check the repetitions and eliminate the false duplicates created by Studio.

Addendum: That is what I first thought, but after running DVX a while I realized that DVX also creates false multiple translations. It is easier to detect and remove them in DVX, but it is still an unnecessary manual task. And the multiples should not have been created at all. The prevention against multiple translations in DVX works only if the hits are created within a project, not if you have imported them from another source. And I do have 450,000 TU:s that I am not willing to throw away or edit manually, one by one.