Importing Tasker xml Tasks/Profiles?

[Wibbly]

Seems fairly straight forward to me.

If you recognise Automagic as better than Tasker, that will drive you to embrase AM methodology and go through the one-time pain of recreating the functionality you want in AM. Doing that will also surely get you a lot of AM understanding and experience.

If you don't want to do that, obviously you don't think AM is that much better and are prepered to live with Tasker as something you understand.

Only you can make that trade-off.

I went from Llama to AM. But Tasker is highly functional and popular and seems to be what folk think of first for automation apps. I found it too much of steep learning curve so never invested in it. It seems Tasker does some things that AM does not and vice-versa. I like AM's UI and have never regretted choosing it over Tasker.

[hmast]

If you recognize Automagic as better than Tasker, that will drive you to embrace AM methodology and go through the one-time pain of recreating the functionality you want in AM.

It would take maybe two weeks to set manually everything up that I have in Tasker. And possibly some bug testing some time after. It's too much time/work in comparison to rewards. I figured I can do what I see value in Automagic outside of Tasker, and then translate to whatever language seems most appropriate.

[Desmanto]

@hmast : I agreed it is very time consuming. If we reverse the case, Let's say somehow I found out that now tasker is better than Automagic (in my alternate universe), I will still reluctant to move all my 200+ flows. Some flows take weeks to build and test.

But no way other way, Automagic and tasker are completely different and use different concept. No other shortcut except to rebuild it from scratch. It should be faster than first build, as you already know the profiles/tasks. Maybe you can start to migrate from the smaller ones first. One day one task/flow.