# Q Business → Amazon Quick Suite migration checklist

## Week 0 — decide

- [ ] Confirm whether you are **existing** Q Business (supported) or **net-new** (must use Quick after cutoff)
- [ ] Inventory apps: chat web experience, anonymous access, custom API integrations
- [ ] List connectors and index size (docs / hours)

## Phase 1 — BYOI / attach index

- [ ] Enable Quick Suite in the account / Identity Center org
- [ ] Attach existing Q Business index (Bring Your Own Index) per [migration guidance](https://docs.aws.amazon.com/amazonq/latest/qbusiness-ug/qbusiness-availability-change.html)
- [ ] Validate ACL / identity propagation on 5 representative queries
- [ ] Pilot Quick Research and one Quick Flow on non-prod users

## Phase 2 — expand capabilities

- [ ] Map dashboards: QuickSight → Quick Sight (expect UI rename, not data move)
- [ ] Build 1–2 Quick Flows for recurring ops (ticket, report, approval)
- [ ] Configure Spaces for team-specific context packs
- [ ] Review guardrails / topic controls parity with Q Business

## Phase 3 — cutover

- [ ] Train power users; publish “when to use Quick vs AgentCore vs Q Developer”
- [ ] Decommission duplicate Q Business web experiences only after adoption metrics hold 2 weeks
- [ ] Update procurement language: no new Q Business / Kendra SKUs in RFPs

## Stop conditions

- Anonymous or ISV-embedded Q Business APIs without a Support-approved path
- Requirement for customer-facing high-volume chat — evaluate AgentCore instead of forcing Quick seats