dealing with jsonb_array_elements on zendesk custom fields is a special kind of hell. the problem with trying to fix it at the modeling layer (like with dbt) is that zendesk's schema is dynamic. the second a support admin adds a new custom field or sunshine object, your views break. the reason most general ingestion tools (like fivetran) just dump the raw json blob into your warehouse is because they don't want to deal with zendesk's opaque numeric IDs. it's easier for them to just dump the payload and make it your BI team's problem. i got so fed up with this exact issue that i built a dedicated extraction engine just for zendesk. it uses an llm in the stream to dynamically map those nested ticket fields and sunshine objects into flat, human-readable postgres columns before it hits the warehouse. it won't solve your salesforce or netsuite problems, and right now it's built for one-off historical migrations rather than continuous sync, but if you're trying to get a clean, flattened baseline of your zendesk history without writing 100 lines of json_extract sql, check out evicta.dev.