You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As a TU classic user, I would like to migrate old data from TU classic to TU app.
Describe the solution you'd like
It would be good to have the migration path described somewhere. TU app seems to ignore ZIP with XMLs containing exported data from TU classic. Maybe some more sophisticated mechanisms are required.
Additional context
Some die hard TU classic users would prefer not to manually migrate thousands of tasks between apps :).
The text was updated successfully, but these errors were encountered:
This is on my todo list since a very long time and honestly I'm not sure I will do it one day.
The data are quite different, a lot of things changes in the data model and would require quite some work.
The current workaround would be to use a Toodledo account to sync and retrieve the data between the old and the new TaskUnifier.
It's some workaround, but not for people preferring to keep their tasks offline :).
I propose to keep this task open - maybe I'm just the only one who would prefer to migrate data instead of starting it over. There is also a chance, there will be some desperate "script guru" to write some unofficial migration tool in Perl or Awk to convert all those XMLs to JSONs and cover the differences you mentioned ;).
Is your feature request related to a problem? Please describe.
As a TU classic user, I would like to migrate old data from TU classic to TU app.
Describe the solution you'd like
It would be good to have the migration path described somewhere. TU app seems to ignore ZIP with XMLs containing exported data from TU classic. Maybe some more sophisticated mechanisms are required.
Additional context
Some die hard TU classic users would prefer not to manually migrate thousands of tasks between apps :).
The text was updated successfully, but these errors were encountered: