Migration assistant

Replacing scribe_v1?

Ranked replacement candidates, each shown with exactly what changes if you switch. Same-provider matches surface first because switching cost is lower; capability regressions are flagged in red.

EL
Migrating from

scribe_v1

ElevenLabs · Active
Input: —/M Output: —/M Context:
View detail →
🔔
Don't get caught off guard next time.
This is the scramble AI Stack Watch is built to prevent. Put scribe_v1 in a monitored client workspace and we'll tell you — with the source — the moment it's deprecated, repriced, or out-shipped by a candidate, while there's still time to plan the move.
Monitor this in a client workspace →
#1 RECOMMENDED

Eleven v3

ElevenLabs · Audio
same provider
View full detail →
What changes if you switch
Field scribe_v1 Eleven v3 Impact
Input price Not verified for either model
Output price Not verified for either model
Lifecycle Active Active Same status
Other candidates
#2

Claude Fable 5

Anthropic
Available active replacement
Details →
#3

Claude Haiku 3.5

Anthropic
Available active replacement
Details →
#4

Claude Haiku 4.5

Anthropic
Available active replacement
Details →
#5

Claude Opus 4

Anthropic
Available active replacement
Details →
Methodology

How candidates are ranked

Candidates are ranked by how much of the source model's profile each one preserves — weighing switching cost (same provider or model family surface first), capability parity (what you keep versus what you'd lose), context window, and pricing direction. A candidate that is itself deprecated is pushed down the list; one that's already retired is never recommended.

Ranking is purely algorithmic — no editorial weighting, no paid placement. Every value is pulled from each provider's own documentation; click any model name to see the source-linked detail.