Will migrate self-host from v3 to v4 keep all of current run data ? If no, how to mirgate data from my current v3 to v4
#migrate from v3 to v4
gray orbit
stoic citrusBOT
Hi @gray orbit. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
Short answer: no, v4 does not reuse v3’s run engine or data. The docs state that after you upgrade packages and deploy v4, existing (already-started) runs will continue executing on the v3 engine while new runs use v4. There’s no documented path to migrate/port v3 run data into v4’s engine; instead, you run both until v3 runs drain, then everything is on v4 (the period can temporarily double concurrency) (Migrating from v3).
For self-hosting, v4 introduces a new architecture (webapp + supervisor, new compose/Kubernetes setup), and the guidance focuses on fresh v4 deployments with version pinning—not on data migration from v3 stores. The self-hosting docs and upgrade guides do not provide a procedure to migrate historical run data from v3 to v4 storage/queues (Docker compose; Kubernetes version locking).
What to do:
- Upgrade your application packages to v4 and deploy; test in staging first. New runs will be v4, old v3 runs continue until they finish; then v4 is fully in effect (Migrating from v3; Installation).
- If you need to retain historical observability data from v3 inside v4, I’m sorry, but there’s no information about an official migration tool or data import path in the knowledge sources. Consider keeping the v3 instance available read-only until you no longer need that history.