What is the standard approach to map Zendesk macro rich text to Genesys Cloud Agent Scripting API v1 during our migration? We are currently hitting a 400 Bad Request on POST /api/v2/scripts when pushing content directly from Zendesk Support Suite 3000. The payload mimics the Zendesk structure, but GC rejects it because the rich text formatting does not translate to the expected JSON schema for script blocks. Our team is in Europe/Paris and dealing with timezone-specific scheduling nuances, yet the core issue remains the data structure mismatch. Zendesk uses a simple HTML-like string for macros, whereas GC expects a nested array of steps with specific types like text or action. We have tried stripping HTML tags, but that loses critical formatting and conditional logic. Is there a recommended transformation layer or SDK helper for converting Zendesk macro content into valid GC script JSON? We need a reliable method to preserve the intent and structure of our existing workflows without manually rewriting thousands of scripts. Any practical migration advice or example payloads for complex macros would be appreciated.