No. The intended workflow is to first import .tbulic18 bundles into the Passolo 2018 project, then upgrade the project from 2018 to 2022 and then export new 2022 bundles.

This means importing the tbulic18 bundles into the Passolo 2018 project requires Passolo 2018, Passolo 2022 would open the LPU either in read-only (no import possible due to read-only) or upgrade it an open it (no import possible because the tbulic18 bundles cannot be imported). Right?

I just did a few tests and it looks like we can successfully import tbulic18 bundles into a Passolo 2022 lpu using the Project > Import Button. Can you please confirm this is a valid approach and okay to use? Otherwise we can upgrade to Passolo 2022 only when we have no uncompleted projects (a rare case ;-)) if we don't want to run 2022 and 2018 in parallel for a while.

Thanks a lot and best regards

I talked to product management and development. 

Officially we recommend to use 2018 and 2022 in parallel and not import .tbulic18 into 22 – so avoid mixing and matching versions like this.

Semi-officially, such a feature wasn't tested. But if it works for you, then make sure to test it thoroughly before deploying in production, and you would use this at your own risk.

If it isn't possible to open Passolo 2018 files in Passolo 2022, why doesn't Passolo 2018 work with Studio 2014 and Multiterm 2024?

I have done the installLocation trick in the Passolo 2018 settings.xml file fpr Studio 2024. Not working.

Can't do the .pai file trick for Multiterm.
Software from the same company and I have to spend valuable time on solving problems that shouldn't exist.

Is there a solution for this problem?

(It's not a new problem, but you know that)