Use a tool that understands the semantics of JSON, e.g. http://www.jsondiff.com/
JSON is a human-readable format, but is not plain text.
On the contrary,
- Exporting to Excel would be dramatically limiting. Excel's strict row/column model, by definition, cannot fit nested data. If each row is a tag, where do you put properties that can have multiple values, such as alarms?
- Modern Excel versions can directly read JSON files, although you'll still ultimately have the same problem of shoving multi-dimensional nested data into a strict R/C format: Power Query JSON connector - Power Query | Microsoft Learn
Using a simple, but structured format, allows for a huge variety of tooling; JSON is a 'de-facto' standard for interchange between APIs and has an ecosystem to match. For instance, there's an incredibly powerful tool call jq
that can make very complex operations absolutely trivial; see this post for an example: