CARTESIA MODEL MIGRATION WORKSHEET Checked October 18, 2026 Companion: https://burki.dev/blog/cartesia-sonic-retirement-model-migration Original planning resource. No calls, synthesis requests or configuration changes were made for this worksheet. It is free; provider and production usage are not included. Use only authorized configurations and evidence. 1. IDENTIFY THE DEPENDENCY Business route / assistant reference: ________________________________________ Environment: ________________________________________________________________ Saved configuration and evidence location: ___________________________________ Actual model ID: _____________________________________________________________ Voice ID and language: _______________________________________________________ Runtime / integration version: _______________________________________________ Output format / sample rate / receiver: _______________________________________ Configuration owner and review date: _________________________________________ Record the precise saved ID, not just the provider name or a model nickname. A default in source is not proof that a particular production route uses it. Do not copy credentials into this inventory. 2. CHECK THE LIFECYCLE Provider status checked on: __________________________________________________ Official status page: ________________________________________________________ Relevant deadline and any stated timezone: ___________________________________ The current provider schedule sunsets sonic-3-2025-10-27 on October 20, 2026, and stops sonic-2 / sonic-turbo and their snapshots after that date. Source: https://docs.cartesia.ai/build-with-cartesia/tts-models/older-models No cutoff timezone is established by this worksheet. Affected / unaffected / unresolved, and why: _________________________________ Other routes using the same dependency: ______________________________________ 3. PLAN A SUPPORTED REPLACEMENT Intended replacement ID: _____________________________________________________ Stable alias / dated snapshot / preview: _____________________________________ Source proving its current status: ___________________________________________ Supported configuration route in your application: ___________________________ Account / voice / language compatibility checked: ____________________________ Required software or configuration changes, if any: ___________________________ Separate authorization and funding for any test: _____________________________ Named decision owner: ________________________________________________________ Do not type a model ID into a custom voice ID field. A provider's replacement recommendation does not establish a native selector in every application. 4. FIX THE BASELINE AND THE SCRIPT Authorized baseline evidence, or explicitly none: ____________________________ Model / voice / language / output route held fixed except intended change: _____________________________________________________________________________ Other changed variables, recorded separately: ________________________________ Original fictional Cedar Arts script: "Welcome to Cedar Arts. The workshop entrance is beside the courtyard. Your enquiry reference is C, D, four, zero. A staff member still needs to confirm room access." Caller interruption: "Did you say the courtyard entrance or the street entrance?" Review criteria: complete understandable instruction, correct reference, an appropriate answer to the clarification and no obsolete audio after interruption. Room access remains unconfirmed. These are criteria, not generated results. 5. RETAIN ALL RESULTS, INCLUDING FAILURES Case | Model requested | Result/evidence | Listener review | Accepted? ____ | _______________ | _______________ | _______________ | _________ ____ | _______________ | _______________ | _______________ | _________ ____ | _______________ | _______________ | _______________ | _________ Provider accepted request? Evidence or unknown: _______________________________ Complete audio received? Evidence or unknown: ________________________________ Actual playback path: ________________________________________________________ Entrance/reference repeated accurately by reviewer? __________________________ Interruption/stale audio outcome: ____________________________________________ Error, partial result or uncertainty: _________________________________________ Changed word/voice/timing issue requiring investigation: ______________________ 6. DECIDE THE OPERATING ROUTE Replacement accepted / rejected / unresolved: ________________________________ Evidence supporting that decision: ___________________________________________ Saved configuration after permitted update: __________________________________ Actual route verification and limits: ________________________________________ Approved alternative if replacement is unavailable: __________________________ Who owns the alternative and when is it used? ________________________________ Do not assume reverting to a retiring provider dependency remains viable after its deadline. Record any temporary operating route as a separate decision. 7. COST AND HANDOFF Current account plan / rate / date: ___________________________________________ Assumed test quantity / unit / authorized maximum: ___________________________ Actual usage evidence, or not run: ___________________________________________ Other recognition / reasoning / platform / carrier charges: __________________ Next owner, due date and unresolved item: _____________________________________ Final state: planned / configured / generated / reviewed / accepted / unresolved Keep these states separate. Do not close the migration from an editor change alone.