Review the CRCPLAN parent feature for additional context, including the feature overview, goals, user stories and use cases, acceptance criteria, designs, dependencies, risks, assumptions, pending questions and documentation callouts.

Summary and goal

Description of what we're building, the end goal and how we'll go about it.

The goal of this epic is to fully harden the migration and dual write code, and to migrate production. It will address bugs found with migration or dual writes functionality from testing in stage or prod, and migration procedures to ensure a safe production migration.

Acceptance Criteria 

These conditions must be met for the epic to be considered complete. This provides a detailed definition of scope and the expected outcomes, written from a user's point of view.

1. RBAC has migrated data for all tenants to relations
2. RBAC has dual write on for all tenants
3. Migration timelines/impacts are communicated to teams and customers (where relevant)
4. Reliability and performance of RBAC is not significantly affected

Non-goals:

• If replication latency is too high, this is a problem, but it can be addressed in a follow-up epic.

Open Questions

Capture any open questions and resolutions related to the epic goal or acceptance criteria. Add any additional details, questions or decisions that need to be made or addressed.