After upgrading, it converted 1/3 (approx) of the messages before it stopped at "0 - Error decoding JSON data: Syntax error".

I solved the issue for this record. Seems like your migration routines lacks som escaping. Please pass this info on to the developers.

In an old message body was

"nårr. tror jeg går iseng. sees =). natte nat. =}"

changed to

"nårr. tror jeg går iseng. sees =). natte nat. ="

Conversion is running again.

I am sorry if I seems like a smart-ass - but I could not wait days for resolution with 800 impatient users :)

How did you locate the specific message? How did you edit it? Having the same issue here, trying to fathom it out =)

I don't have the SQL statements at hand, but I searched the the date in old table > than the last converted in new table - there is also a "converted" attribute on the old table you can omit all that is not null on the table.

For me it was } character in a few messages and one had only {{}}{}{{}} with some numbers (smileys I suppose). I change the } to ) - the last one I just wrote "Message could not be converted" in.

Thanks! I actually got Dimas to fix my problem. They will put the fix into the release of the next version. I'm just looking through the backend now to check the conversion progress. I must have hit the cron job about 400 times or so. I really didn't think we had that many messages , so I'm curious :)