Qontak One Team Migration
Migration of existing team structures from Qontak Chat (Divisions) and Qontak CRM (Teams) into a unified Qontak One Launchpad USMAN system. Introduces mandatory team assignments for new user invitations, adds DB identifiers to track team origins (source_identifier and reference_id), and provides an idempotent script to safely migrate and prefix legacy teams.
As amended on 2026-07-20, every CID's General team also contains all existing users through an
idempotent backfill and automatically receives every future user. Launchpad owns the migration
trigger and calls private Chat/CRM endpoints. These additions are unestimated; the existing
12.5/15.5 md (81%) remains a historical baseline, not the expanded-scope percentage. See
status 2026-07-20.
Initiatives
prds/prd-qontak-one-team-anchor.md— ANCHOR: initiative master index and Phase Indexprds/prd-qontak-one-team-migration.md— Phase 1: Legacy Team Migration (Bifrost lead)
QA Lane
Lane B — keeps a human QA gate. Security/isolation: migrates team-assignment and access data, and a one-time migration is largely out of automation reach and hard to reverse. No E2E test specs exist for this initiative yet, so the Lane-A entry bar (100% E2E, spec-mapped coverage) is unmet regardless. Classified by Yoddi, Izzul (QA), 2026-06-26.