Migrating scripts from older versions of todo4teams to version 4 and higher should generally be quite easy, as the scripts are fully compatible as far as the methods of the helper objects are concerned. However, since todo4teams scripts have almost unlimited options for accessing classes in the Java runtime environment, it is advisable to check the following points:

1. Were classes from the todo4teams packages used directly? This can be recognized by the fact that the package name begins with com.proxemo.todo. The new packages begin with  com.proxemo.todo4.
   • Solution: Rename com.proxemo.todo to com.proxemo.todo4. This is a first approach to a solution that often leads to success. Since the architecture of todo4teams has changed fundamentally in version 4, it is possible that the class in question or the methods used in it no longer exist. In this case, please ask your administrator.

1. Were the classes of the old Swing client accessed directly? This can be recognized by the fact that the package name begins with com.proxemo.todo.client. Since todo4teams has switched from a smart client architecture to a web architecture in this version jump, you have to check individually which new class corresponds to the old Swing class. If in doubt, ask your administrator.