Something went amiss when migrating content v7 to v10. With the exception of media loosing its connections (a post for later) I've only had content for a single document type that has failed. Is there a way I can get to the bottom of this? It's a bog standard JSON error:

Unexpected character encountered while parsing value: E. Path '', line 0, position 0.

full stack trace: https://pastebin.com/qy8ZEUZt I thought it was related to media pickers. I've since changed them to the latest versions, but it makes no difference. I'd just add the content again, but I can't actually delete the existing content as it errors the moment I click it within the back office. Any ideas to help with debugging and getting to the bottom of this?

If you can figure out which property is the one with the bad data (looks like it'll be one that expects the data to be json, so it could be any of the content/media pickers or blocklists), you could then temporarily change that property into a `textstring`/`textbox`, which should stop it from erroring out as it will simply dump the raw string data into the textbox.

@Owain Jones - thanks, I'll give that a go. just find it a bit weird how I can render it with the normal APIs, just not view it in the back office. Hopefully, I can write a script that will read all the broken ones, and use them to create working versions.