Data Explorer
Inspect source-shaped transition evidence, normalized account records, provenance, and account timelines.
| id | customer id | date | source | category | status | outcome | effort score | flag | detail |
|---|---|---|---|---|---|---|---|---|---|
| ACCT-0034 | 2026-01-01 | billing | direct account billing | ready | T5 | 2 | wave-ready | Single billing owner is defined for the read-only source state. | |
| ACCT-0022 | 2026-01-01 | capability | core acceptance | ready | T2 | 2 | wave-ready | Core capability has a tested target-platform equivalent. | |
| ACCT-2007 | 2026-01-01 | integration | unknown surface | watch | T0 | 5 | measurement-gap | Traffic exists but cannot be attributed to a known integration surface. | |
| ACCT-0019 | 2026-01-01 | integration | hosted ui | ready | T4 | 3 | wave-ready | Hosted user journey has a target-platform path and validation checklist. | |
| ACCT-0037 | 2026-01-01 | readiness | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. | |
| ACCT-0015 | 2026-01-01 | readiness | wave 4 integration rework | watch | T4 | 6 | integration-rework | Dual access is useful while integration rework is completed. | |
| ACCT-1019 | 2026-01-02 | account | integrated | watch | T4 | 6 | integration-rework | Account can use both platforms, but embedded integration work remains. | |
| ACCT-1023 | 2026-01-02 | account | low-activity | watch | T0 | 4 | measurement-gap | Low recent activity cannot be interpreted because usage tracking is missing. | |
| ACCT-0039 | 2026-01-02 | account | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | |
| ACCT-0043 | 2026-01-02 | account | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | |
| ACCT-1035 | 2026-01-02 | account | integrated | watch | T4 | 6 | integration-rework | Account can use both platforms, but embedded integration work remains. | |
| ACCT-1039 | 2026-01-02 | account | low-activity | watch | T0 | 4 | measurement-gap | Low recent activity cannot be interpreted because usage tracking is missing. | |
| ACCT-2027 | 2026-01-02 | integration | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | |
| ACCT-0007 | 2026-01-02 | readiness | wave 4 integration rework | watch | T4 | 6 | integration-rework | Dual access is useful while integration rework is completed. | |
| ACCT-0039 | 2026-01-02 | readiness | wave 3 parity dependency | blocked | T2 | 7 | parity-gap | Capability parity blocks transition progression. | |
| ACCT-0035 | 2026-01-03 | readiness | wave 3 parity dependency | blocked | T2 | 7 | parity-gap | Capability parity blocks transition progression. | |
| ACCT-3023 | 2026-01-03 | readiness | wave unknown | watch | T0 | 4 | measurement-gap | Readiness cannot be assigned while usage signals are missing. | |
| ACCT-0007 | 2026-01-04 | account | integrated | watch | T4 | 6 | integration-rework | Account can use both platforms, but embedded integration work remains. | |
| ACCT-1013 | 2026-01-04 | account | capability-heavy | blocked | T2 | 7 | parity-gap | Target processing path exists but required capability parity is incomplete. | |
| ACCT-1527 | 2026-01-04 | capability | core acceptance | ready | T2 | 2 | wave-ready | Core capability has a tested target-platform equivalent. | |
| ACCT-0025 | 2026-01-04 | integration | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | |
| ACCT-3019 | 2026-01-04 | readiness | wave 3 parity dependency | blocked | T2 | 7 | parity-gap | Capability parity blocks transition progression. | |
| ACCT-0017 | 2026-01-05 | account | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | |
| ACCT-0024 | 2026-01-05 | billing | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | |
| ACCT-2517 | 2026-01-05 | billing | direct account billing | ready | T5 | 2 | wave-ready | Single billing owner is defined for the read-only source state. | |
| ACCT-1539 | 2026-01-05 | capability | stored profile data | in-progress | T3 | 5 | parity-gap | Data copy and sync are in progress but not yet verified. | |
| ACCT-2021 | 2026-01-05 | integration | partner connector | watch | T4 | 6 | integration-rework | Connector ownership is known but target-platform support is pending. | |
| ACCT-1025 | 2026-01-06 | account | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | |
| ACCT-0010 | 2026-01-06 | billing | sponsor-paid | watch | T4 | 5 | billing-continuity | A third party pays account fees and must be preserved through cutover. | |
| ACCT-0038 | 2026-01-06 | capability | core acceptance | ready | T2 | 2 | wave-ready | Core capability has a tested target-platform equivalent. | |
| ACCT-1541 | 2026-01-06 | capability | scheduled activity | blocked | T2 | 7 | parity-gap | Scheduled activity has no confirmed target-platform operating model. | |
| ACCT-2011 | 2026-01-06 | integration | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | |
| ACCT-0011 | 2026-01-06 | readiness | wave 4 integration rework | watch | T4 | 6 | integration-rework | Dual access is useful while integration rework is completed. | |
| ACCT-0013 | 2026-01-07 | account | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | |
| ACCT-0041 | 2026-01-07 | account | capability-heavy | blocked | T2 | 7 | parity-gap | Target processing path exists but required capability parity is incomplete. | |
| ACCT-1031 | 2026-01-07 | account | low-activity | watch | T0 | 4 | measurement-gap | Low recent activity cannot be interpreted because usage tracking is missing. | |
| ACCT-1503 | 2026-01-07 | capability | stored profile data | in-progress | T3 | 5 | parity-gap | Data copy and sync are in progress but not yet verified. | |
| ACCT-1507 | 2026-01-07 | capability | self-service tool | watch | T1 | 4 | measurement-gap | Capability is enabled by default but usage tracking is absent. | |
| ACCT-1515 | 2026-01-07 | capability | scheduled activity | blocked | T2 | 7 | parity-gap | Scheduled activity has no confirmed target-platform operating model. | |
| ACCT-1533 | 2026-01-07 | capability | scheduled activity | blocked | T2 | 7 | parity-gap | Scheduled activity has no confirmed target-platform operating model. | |
| ACCT-2509 | 2026-01-08 | billing | direct account billing | ready | T5 | 2 | wave-ready | Single billing owner is defined for the read-only source state. | |
| ACCT-2515 | 2026-01-08 | billing | no current revenue | watch | T0 | 3 | measurement-gap | No current revenue is visible, but account disposition still needs confirmation. | |
| ACCT-2531 | 2026-01-08 | billing | no current revenue | watch | T0 | 3 | measurement-gap | No current revenue is visible, but account disposition still needs confirmation. | |
| ACCT-0018 | 2026-01-08 | capability | core acceptance | ready | T2 | 2 | wave-ready | Core capability has a tested target-platform equivalent. | |
| ACCT-1529 | 2026-01-08 | capability | core acceptance | ready | T2 | 2 | wave-ready | Core capability has a tested target-platform equivalent. | |
| ACCT-0050 | 2026-01-08 | capability | self-service tool | watch | T1 | 4 | measurement-gap | Capability is enabled by default but usage tracking is absent. | |
| ACCT-0026 | 2026-01-08 | capability | core acceptance | ready | T2 | 2 | wave-ready | Core capability has a tested target-platform equivalent. | |
| ACCT-2031 | 2026-01-08 | integration | unknown surface | watch | T0 | 5 | measurement-gap | Traffic exists but cannot be attributed to a known integration surface. | |
| ACCT-0041 | 2026-01-08 | readiness | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. | |
| ACCT-1011 | 2026-01-09 | account | integrated | watch | T4 | 6 | integration-rework | Account can use both platforms, but embedded integration work remains. | |
| ACCT-0011 | 2026-01-09 | account | integrated | watch | T4 | 6 | integration-rework | Account can use both platforms, but embedded integration work remains. | |
| ACCT-1033 | 2026-01-09 | account | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | |
| ACCT-1505 | 2026-01-09 | capability | scheduled activity | blocked | T2 | 7 | parity-gap | Scheduled activity has no confirmed target-platform operating model. | |
| ACCT-1509 | 2026-01-09 | capability | core acceptance | ready | T2 | 2 | wave-ready | Core capability has a tested target-platform equivalent. | |
| ACCT-0040 | 2026-01-09 | capability | scheduled activity | blocked | T2 | 7 | parity-gap | Scheduled activity has no confirmed target-platform operating model. | |
| ACCT-1531 | 2026-01-09 | capability | stored profile data | in-progress | T3 | 5 | parity-gap | Data copy and sync are in progress but not yet verified. | |
| ACCT-0028 | 2026-01-09 | capability | stored profile data | in-progress | T3 | 5 | parity-gap | Data copy and sync are in progress but not yet verified. | |
| ACCT-0017 | 2026-01-09 | integration | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | |
| ACCT-0019 | 2026-01-10 | account | integrated | watch | T4 | 6 | integration-rework | Account can use both platforms, but embedded integration work remains. | |
| ACCT-1511 | 2026-01-10 | capability | core acceptance | ready | T2 | 2 | wave-ready | Core capability has a tested target-platform equivalent. | |
| ACCT-0044 | 2026-01-10 | capability | stored profile data | in-progress | T3 | 5 | parity-gap | Data copy and sync are in progress but not yet verified. | |
| ACCT-0024 | 2026-01-10 | capability | scheduled activity | blocked | T2 | 7 | parity-gap | Scheduled activity has no confirmed target-platform operating model. | |
| ACCT-2023 | 2026-01-10 | integration | unknown surface | watch | T0 | 5 | measurement-gap | Traffic exists but cannot be attributed to a known integration surface. | |
| ACCT-1027 | 2026-01-11 | account | integrated | watch | T4 | 6 | integration-rework | Account can use both platforms, but embedded integration work remains. | |
| ACCT-1037 | 2026-01-11 | account | capability-heavy | blocked | T2 | 7 | parity-gap | Target processing path exists but required capability parity is incomplete. | |
| ACCT-0045 | 2026-01-11 | account | capability-heavy | blocked | T2 | 7 | parity-gap | Target processing path exists but required capability parity is incomplete. | |
| ACCT-0012 | 2026-01-11 | capability | self-service tool | watch | T1 | 4 | measurement-gap | Capability is enabled by default but usage tracking is absent. | |
| ACCT-0014 | 2026-01-11 | capability | stored profile data | in-progress | T3 | 5 | parity-gap | Data copy and sync are in progress but not yet verified. | |
| ACCT-1535 | 2026-01-11 | capability | self-service tool | watch | T1 | 4 | measurement-gap | Capability is enabled by default but usage tracking is absent. | |
| ACCT-2009 | 2026-01-11 | integration | hosted ui | ready | T4 | 3 | wave-ready | Hosted user journey has a target-platform path and validation checklist. | |
| ACCT-0049 | 2026-01-11 | integration | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | |
| ACCT-0001 | 2026-01-11 | integration | partner connector | watch | T4 | 6 | integration-rework | Connector ownership is known but target-platform support is pending. | |
| ACCT-0031 | 2026-01-11 | readiness | wave 3 parity dependency | blocked | T2 | 7 | parity-gap | Capability parity blocks transition progression. | |
| ACCT-0027 | 2026-01-12 | account | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | |
| ACCT-0036 | 2026-01-12 | capability | scheduled activity | blocked | T2 | 7 | parity-gap | Scheduled activity has no confirmed target-platform operating model. | |
| ACCT-3017 | 2026-01-12 | readiness | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. | |
| ACCT-3025 | 2026-01-12 | readiness | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. | |
| ACCT-1009 | 2026-01-13 | account | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | |
| ACCT-0002 | 2026-01-13 | billing | sponsor-paid | watch | T4 | 5 | billing-continuity | A third party pays account fees and must be preserved through cutover. | |
| ACCT-0033 | 2026-01-13 | readiness | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. | |
| ACCT-3021 | 2026-01-13 | readiness | wave 4 integration rework | watch | T4 | 6 | integration-rework | Dual access is useful while integration rework is completed. | |
| ACCT-0009 | 2026-01-14 | account | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | |
| ACCT-2505 | 2026-01-14 | billing | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | |
| ACCT-0042 | 2026-01-14 | capability | core acceptance | ready | T2 | 2 | wave-ready | Core capability has a tested target-platform equivalent. | |
| ACCT-2001 | 2026-01-14 | integration | hosted ui | ready | T4 | 3 | wave-ready | Hosted user journey has a target-platform path and validation checklist. | |
| ACCT-3005 | 2026-01-14 | readiness | wave 4 integration rework | watch | T4 | 6 | integration-rework | Dual access is useful while integration rework is completed. | |
| ACCT-1007 | 2026-01-15 | account | low-activity | watch | T0 | 4 | measurement-gap | Low recent activity cannot be interpreted because usage tracking is missing. | |
| ACCT-0031 | 2026-01-15 | account | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | |
| ACCT-0030 | 2026-01-15 | billing | direct account billing | ready | T5 | 2 | wave-ready | Single billing owner is defined for the read-only source state. | |
| ACCT-0016 | 2026-01-15 | capability | self-service tool | watch | T1 | 4 | measurement-gap | Capability is enabled by default but usage tracking is absent. | |
| ACCT-1519 | 2026-01-15 | capability | core acceptance | ready | T2 | 2 | wave-ready | Core capability has a tested target-platform equivalent. | |
| ACCT-0020 | 2026-01-15 | capability | scheduled activity | blocked | T2 | 7 | parity-gap | Scheduled activity has no confirmed target-platform operating model. | |
| ACCT-2003 | 2026-01-15 | integration | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | |
| ACCT-1001 | 2026-01-16 | account | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | |
| ACCT-0026 | 2026-01-16 | billing | direct account billing | ready | T5 | 2 | wave-ready | Single billing owner is defined for the read-only source state. | |
| ACCT-2525 | 2026-01-16 | billing | direct account billing | ready | T5 | 2 | wave-ready | Single billing owner is defined for the read-only source state. | |
| ACCT-1501 | 2026-01-16 | capability | core acceptance | ready | T2 | 2 | wave-ready | Core capability has a tested target-platform equivalent. | |
| ACCT-1525 | 2026-01-16 | capability | self-service tool | watch | T1 | 4 | measurement-gap | Capability is enabled by default but usage tracking is absent. | |
| ACCT-3001 | 2026-01-16 | readiness | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. | |
| ACCT-2501 | 2026-01-17 | billing | direct account billing | ready | T5 | 2 | wave-ready | Single billing owner is defined for the read-only source state. | |
| ACCT-0028 | 2026-01-17 | billing | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | |
| ACCT-0036 | 2026-01-17 | billing | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | |
| ACCT-0008 | 2026-01-17 | capability | core acceptance | ready | T2 | 2 | wave-ready | Core capability has a tested target-platform equivalent. | |
| ACCT-2019 | 2026-01-17 | integration | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | |
| ACCT-3013 | 2026-01-17 | readiness | wave 4 integration rework | watch | T4 | 6 | integration-rework | Dual access is useful while integration rework is completed. | |
| ACCT-0017 | 2026-01-17 | readiness | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. | |
| ACCT-2503 | 2026-01-18 | billing | sponsor-paid | watch | T4 | 5 | billing-continuity | A third party pays account fees and must be preserved through cutover. | |
| ACCT-2507 | 2026-01-18 | billing | no current revenue | watch | T0 | 3 | measurement-gap | No current revenue is visible, but account disposition still needs confirmation. | |
| ACCT-2519 | 2026-01-18 | billing | sponsor-paid | watch | T4 | 5 | billing-continuity | A third party pays account fees and must be preserved through cutover. | |
| ACCT-0008 | 2026-01-18 | billing | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | |
| ACCT-2529 | 2026-01-18 | billing | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | |
| ACCT-0004 | 2026-01-18 | capability | scheduled activity | blocked | T2 | 7 | parity-gap | Scheduled activity has no confirmed target-platform operating model. | |
| ACCT-3007 | 2026-01-18 | readiness | wave unknown | watch | T0 | 4 | measurement-gap | Readiness cannot be assigned while usage signals are missing. | |
| ACCT-3027 | 2026-01-18 | readiness | wave 3 parity dependency | blocked | T2 | 7 | parity-gap | Capability parity blocks transition progression. | |
| ACCT-2511 | 2026-01-19 | billing | sponsor-paid | watch | T4 | 5 | billing-continuity | A third party pays account fees and must be preserved through cutover. | |
| ACCT-1513 | 2026-01-19 | capability | stored profile data | in-progress | T3 | 5 | parity-gap | Data copy and sync are in progress but not yet verified. | |
| ACCT-1523 | 2026-01-19 | capability | scheduled activity | blocked | T2 | 7 | parity-gap | Scheduled activity has no confirmed target-platform operating model. | |
| ACCT-0043 | 2026-01-19 | integration | partner connector | watch | T4 | 6 | integration-rework | Connector ownership is known but target-platform support is pending. | |
| ACCT-2017 | 2026-01-19 | integration | hosted ui | ready | T4 | 3 | wave-ready | Hosted user journey has a target-platform path and validation checklist. | |
| ACCT-0027 | 2026-01-19 | integration | hosted ui | ready | T4 | 3 | wave-ready | Hosted user journey has a target-platform path and validation checklist. | |
| ACCT-0029 | 2026-01-19 | readiness | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. | |
| ACCT-0021 | 2026-01-20 | integration | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | |
| ACCT-1015 | 2026-01-21 | account | low-activity | watch | T0 | 4 | measurement-gap | Low recent activity cannot be interpreted because usage tracking is missing. | |
| ACCT-2015 | 2026-01-21 | integration | unknown surface | watch | T0 | 5 | measurement-gap | Traffic exists but cannot be attributed to a known integration surface. | |
| ACCT-2025 | 2026-01-21 | integration | hosted ui | ready | T4 | 3 | wave-ready | Hosted user journey has a target-platform path and validation checklist. | |
| ACCT-3003 | 2026-01-21 | readiness | wave 3 parity dependency | blocked | T2 | 7 | parity-gap | Capability parity blocks transition progression. | |
| ACCT-0005 | 2026-01-22 | account | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | |
| ACCT-0033 | 2026-01-22 | account | capability-heavy | blocked | T2 | 7 | parity-gap | Target processing path exists but required capability parity is incomplete. | |
| ACCT-1521 | 2026-01-22 | capability | stored profile data | in-progress | T3 | 5 | parity-gap | Data copy and sync are in progress but not yet verified. | |
| ACCT-0048 | 2026-01-22 | capability | stored profile data | in-progress | T3 | 5 | parity-gap | Data copy and sync are in progress but not yet verified. | |
| ACCT-1537 | 2026-01-22 | capability | core acceptance | ready | T2 | 2 | wave-ready | Core capability has a tested target-platform equivalent. | |
| ACCT-0005 | 2026-01-22 | readiness | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. | |
| ACCT-3011 | 2026-01-22 | readiness | wave 3 parity dependency | blocked | T2 | 7 | parity-gap | Capability parity blocks transition progression. | |
| ACCT-0037 | 2026-01-23 | account | capability-heavy | blocked | T2 | 7 | parity-gap | Target processing path exists but required capability parity is incomplete. | |
| ACCT-0021 | 2026-01-23 | account | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | |
| ACCT-0022 | 2026-01-23 | billing | direct account billing | ready | T5 | 2 | wave-ready | Single billing owner is defined for the read-only source state. | |
| ACCT-0004 | 2026-01-23 | billing | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | |
| ACCT-0046 | 2026-01-23 | capability | self-service tool | watch | T1 | 4 | measurement-gap | Capability is enabled by default but usage tracking is absent. | |
| ACCT-2013 | 2026-01-23 | integration | partner connector | watch | T4 | 6 | integration-rework | Connector ownership is known but target-platform support is pending. | |
| ACCT-0019 | 2026-01-23 | readiness | wave 4 integration rework | watch | T4 | 6 | integration-rework | Dual access is useful while integration rework is completed. | |
| ACCT-1017 | 2026-01-24 | account | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | |
| ACCT-1021 | 2026-01-24 | account | capability-heavy | blocked | T2 | 7 | parity-gap | Target processing path exists but required capability parity is incomplete. | |
| ACCT-0006 | 2026-01-24 | billing | sponsor-paid | watch | T4 | 5 | billing-continuity | A third party pays account fees and must be preserved through cutover. | |
| ACCT-0002 | 2026-01-24 | capability | core acceptance | ready | T2 | 2 | wave-ready | Core capability has a tested target-platform equivalent. | |
| ACCT-0045 | 2026-01-24 | integration | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | |
| ACCT-0047 | 2026-01-24 | integration | partner connector | watch | T4 | 6 | integration-rework | Connector ownership is known but target-platform support is pending. | |
| ACCT-0003 | 2026-01-25 | account | integrated | watch | T4 | 6 | integration-rework | Account can use both platforms, but embedded integration work remains. | |
| ACCT-1005 | 2026-01-25 | account | capability-heavy | blocked | T2 | 7 | parity-gap | Target processing path exists but required capability parity is incomplete. | |
| ACCT-0048 | 2026-01-25 | billing | sponsor-paid | watch | T4 | 5 | billing-continuity | A third party pays account fees and must be preserved through cutover. | |
| ACCT-0050 | 2026-01-25 | billing | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | |
| ACCT-2527 | 2026-01-25 | billing | sponsor-paid | watch | T4 | 5 | billing-continuity | A third party pays account fees and must be preserved through cutover. | |
| ACCT-0012 | 2026-01-25 | billing | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | |
| ACCT-1517 | 2026-01-25 | capability | self-service tool | watch | T1 | 4 | measurement-gap | Capability is enabled by default but usage tracking is absent. | |
| ACCT-2029 | 2026-01-25 | integration | partner connector | watch | T4 | 6 | integration-rework | Connector ownership is known but target-platform support is pending. | |
| ACCT-3015 | 2026-01-25 | readiness | wave unknown | watch | T0 | 4 | measurement-gap | Readiness cannot be assigned while usage signals are missing. | |
| ACCT-3029 | 2026-01-25 | readiness | wave 4 integration rework | watch | T4 | 6 | integration-rework | Dual access is useful while integration rework is completed. | |
| ACCT-0015 | 2026-01-26 | account | integrated | watch | T4 | 6 | integration-rework | Account can use both platforms, but embedded integration work remains. | |
| ACCT-1029 | 2026-01-26 | account | capability-heavy | blocked | T2 | 7 | parity-gap | Target processing path exists but required capability parity is incomplete. | |
| ACCT-0009 | 2026-01-26 | readiness | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. | |
| ACCT-0029 | 2026-01-27 | account | capability-heavy | blocked | T2 | 7 | parity-gap | Target processing path exists but required capability parity is incomplete. | |
| ACCT-2521 | 2026-01-27 | billing | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | |
| ACCT-0015 | 2026-01-27 | integration | hosted ui | ready | T4 | 3 | wave-ready | Hosted user journey has a target-platform path and validation checklist. | |
| ACCT-3009 | 2026-01-27 | readiness | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. | |
| ACCT-0043 | 2026-01-27 | readiness | wave 3 parity dependency | blocked | T2 | 7 | parity-gap | Capability parity blocks transition progression. | |
| ACCT-0032 | 2026-01-28 | billing | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | |
| ACCT-0023 | 2026-01-28 | integration | hosted ui | ready | T4 | 3 | wave-ready | Hosted user journey has a target-platform path and validation checklist. | |
| ACCT-0003 | 2026-01-28 | integration | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | |
| ACCT-0005 | 2026-01-28 | integration | partner connector | watch | T4 | 6 | integration-rework | Connector ownership is known but target-platform support is pending. | |
| ACCT-2523 | 2026-01-29 | billing | no current revenue | watch | T0 | 3 | measurement-gap | No current revenue is visible, but account disposition still needs confirmation. | |
| ACCT-0034 | 2026-01-29 | capability | core acceptance | ready | T2 | 2 | wave-ready | Core capability has a tested target-platform equivalent. | |
| ACCT-0010 | 2026-01-29 | capability | stored profile data | in-progress | T3 | 5 | parity-gap | Data copy and sync are in progress but not yet verified. | |
| ACCT-2005 | 2026-01-29 | integration | partner connector | watch | T4 | 6 | integration-rework | Connector ownership is known but target-platform support is pending. | |
| ACCT-0029 | 2026-01-29 | integration | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | |
| ACCT-3031 | 2026-01-29 | readiness | wave unknown | watch | T0 | 4 | measurement-gap | Readiness cannot be assigned while usage signals are missing. | |
| ACCT-2513 | 2026-01-30 | billing | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | |
| ACCT-0041 | 2026-01-30 | integration | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | |
| ACCT-0001 | 2026-01-31 | account | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | |
| ACCT-1003 | 2026-01-31 | account | integrated | watch | T4 | 6 | integration-rework | Account can use both platforms, but embedded integration work remains. | |
| ACCT-0035 | 2026-01-31 | account | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | |
| ACCT-0013 | 2026-01-31 | readiness | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. |
| account record id | account id | snapshot date | segment | readiness status | transition state | complexity score | risk flag | summary | analyst note |
|---|---|---|---|---|---|---|---|---|---|
| ACCTREC-2026-01-0001 | ACCT-0001 | 2026-01-31 | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | Candidate for an early guided cohort. |
| ACCTREC-2026-01-0002 | ACCT-1001 | 2026-01-16 | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | Candidate for an early guided cohort. |
| ACCTREC-2026-01-0003 | ACCT-0027 | 2026-01-12 | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | Candidate for an early guided cohort. |
| ACCTREC-2026-01-0004 | ACCT-1003 | 2026-01-31 | integrated | watch | T4 | 6 | integration-rework | Account can use both platforms, but embedded integration work remains. | Keep dual access until rework is verified. |
| ACCTREC-2026-01-0005 | ACCT-0003 | 2026-01-25 | integrated | watch | T4 | 6 | integration-rework | Account can use both platforms, but embedded integration work remains. | Keep dual access until rework is verified. |
| ACCTREC-2026-01-0006 | ACCT-1005 | 2026-01-25 | capability-heavy | blocked | T2 | 7 | parity-gap | Target processing path exists but required capability parity is incomplete. | Do not advance until parity gap is closed. |
| ACCTREC-2026-01-0007 | ACCT-0029 | 2026-01-27 | capability-heavy | blocked | T2 | 7 | parity-gap | Target processing path exists but required capability parity is incomplete. | Do not advance until parity gap is closed. |
| ACCTREC-2026-01-0008 | ACCT-1007 | 2026-01-15 | low-activity | watch | T0 | 4 | measurement-gap | Low recent activity cannot be interpreted because usage tracking is missing. | Unknown usage remains unknown, not unused. |
| ACCTREC-2026-01-0009 | ACCT-0005 | 2026-01-22 | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | Candidate for an early guided cohort. |
| ACCTREC-2026-01-0010 | ACCT-1009 | 2026-01-13 | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | Candidate for an early guided cohort. |
| ACCTREC-2026-01-0011 | ACCT-0031 | 2026-01-15 | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | Candidate for an early guided cohort. |
| ACCTREC-2026-01-0012 | ACCT-1011 | 2026-01-09 | integrated | watch | T4 | 6 | integration-rework | Account can use both platforms, but embedded integration work remains. | Keep dual access until rework is verified. |
| ACCTREC-2026-01-0013 | ACCT-0007 | 2026-01-04 | integrated | watch | T4 | 6 | integration-rework | Account can use both platforms, but embedded integration work remains. | Keep dual access until rework is verified. |
| ACCTREC-2026-01-0014 | ACCT-1013 | 2026-01-04 | capability-heavy | blocked | T2 | 7 | parity-gap | Target processing path exists but required capability parity is incomplete. | Do not advance until parity gap is closed. |
| ACCTREC-2026-01-0015 | ACCT-0033 | 2026-01-22 | capability-heavy | blocked | T2 | 7 | parity-gap | Target processing path exists but required capability parity is incomplete. | Do not advance until parity gap is closed. |
| ACCTREC-2026-01-0016 | ACCT-1015 | 2026-01-21 | low-activity | watch | T0 | 4 | measurement-gap | Low recent activity cannot be interpreted because usage tracking is missing. | Unknown usage remains unknown, not unused. |
| ACCTREC-2026-01-0017 | ACCT-0009 | 2026-01-14 | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | Candidate for an early guided cohort. |
| ACCTREC-2026-01-0018 | ACCT-1017 | 2026-01-24 | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | Candidate for an early guided cohort. |
| ACCTREC-2026-01-0019 | ACCT-0035 | 2026-01-31 | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | Candidate for an early guided cohort. |
| ACCTREC-2026-01-0020 | ACCT-1019 | 2026-01-02 | integrated | watch | T4 | 6 | integration-rework | Account can use both platforms, but embedded integration work remains. | Keep dual access until rework is verified. |
| ACCTREC-2026-01-0021 | ACCT-0011 | 2026-01-09 | integrated | watch | T4 | 6 | integration-rework | Account can use both platforms, but embedded integration work remains. | Keep dual access until rework is verified. |
| ACCTREC-2026-01-0022 | ACCT-1021 | 2026-01-24 | capability-heavy | blocked | T2 | 7 | parity-gap | Target processing path exists but required capability parity is incomplete. | Do not advance until parity gap is closed. |
| ACCTREC-2026-01-0023 | ACCT-0037 | 2026-01-23 | capability-heavy | blocked | T2 | 7 | parity-gap | Target processing path exists but required capability parity is incomplete. | Do not advance until parity gap is closed. |
| ACCTREC-2026-01-0024 | ACCT-1023 | 2026-01-02 | low-activity | watch | T0 | 4 | measurement-gap | Low recent activity cannot be interpreted because usage tracking is missing. | Unknown usage remains unknown, not unused. |
| ACCTREC-2026-01-0025 | ACCT-0013 | 2026-01-07 | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | Candidate for an early guided cohort. |
| ACCTREC-2026-01-0026 | ACCT-1025 | 2026-01-06 | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | Candidate for an early guided cohort. |
| ACCTREC-2026-01-0027 | ACCT-0039 | 2026-01-02 | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | Candidate for an early guided cohort. |
| ACCTREC-2026-01-0028 | ACCT-1027 | 2026-01-11 | integrated | watch | T4 | 6 | integration-rework | Account can use both platforms, but embedded integration work remains. | Keep dual access until rework is verified. |
| ACCTREC-2026-01-0029 | ACCT-0015 | 2026-01-26 | integrated | watch | T4 | 6 | integration-rework | Account can use both platforms, but embedded integration work remains. | Keep dual access until rework is verified. |
| ACCTREC-2026-01-0030 | ACCT-1029 | 2026-01-26 | capability-heavy | blocked | T2 | 7 | parity-gap | Target processing path exists but required capability parity is incomplete. | Do not advance until parity gap is closed. |
| ACCTREC-2026-01-0031 | ACCT-0041 | 2026-01-07 | capability-heavy | blocked | T2 | 7 | parity-gap | Target processing path exists but required capability parity is incomplete. | Do not advance until parity gap is closed. |
| ACCTREC-2026-01-0032 | ACCT-1031 | 2026-01-07 | low-activity | watch | T0 | 4 | measurement-gap | Low recent activity cannot be interpreted because usage tracking is missing. | Unknown usage remains unknown, not unused. |
| ACCTREC-2026-01-0033 | ACCT-0017 | 2026-01-05 | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | Candidate for an early guided cohort. |
| ACCTREC-2026-01-0034 | ACCT-1033 | 2026-01-09 | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | Candidate for an early guided cohort. |
| ACCTREC-2026-01-0035 | ACCT-0043 | 2026-01-02 | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | Candidate for an early guided cohort. |
| ACCTREC-2026-01-0036 | ACCT-1035 | 2026-01-02 | integrated | watch | T4 | 6 | integration-rework | Account can use both platforms, but embedded integration work remains. | Keep dual access until rework is verified. |
| ACCTREC-2026-01-0037 | ACCT-0019 | 2026-01-10 | integrated | watch | T4 | 6 | integration-rework | Account can use both platforms, but embedded integration work remains. | Keep dual access until rework is verified. |
| ACCTREC-2026-01-0038 | ACCT-1037 | 2026-01-11 | capability-heavy | blocked | T2 | 7 | parity-gap | Target processing path exists but required capability parity is incomplete. | Do not advance until parity gap is closed. |
| ACCTREC-2026-01-0039 | ACCT-0045 | 2026-01-11 | capability-heavy | blocked | T2 | 7 | parity-gap | Target processing path exists but required capability parity is incomplete. | Do not advance until parity gap is closed. |
| ACCTREC-2026-01-0040 | ACCT-1039 | 2026-01-02 | low-activity | watch | T0 | 4 | measurement-gap | Low recent activity cannot be interpreted because usage tracking is missing. | Unknown usage remains unknown, not unused. |
| ACCTREC-2026-01-0041 | ACCT-0021 | 2026-01-23 | simple-ui | ready | T1 | 2 | wave-ready | Source account has a target shell and no known advanced dependencies. | Candidate for an early guided cohort. |
| capability record id | account id | observed date | capability | parity status | transition state | usage signal | complexity score | gap type | summary |
|---|---|---|---|---|---|---|---|---|---|
| CAP-2026-01-0001 | ACCT-0008 | 2026-01-17 | core acceptance | ready | T2 | observed | 2 | wave-ready | Core capability has a tested target-platform equivalent. |
| CAP-2026-01-0002 | ACCT-1501 | 2026-01-16 | core acceptance | ready | T2 | observed | 2 | wave-ready | Core capability has a tested target-platform equivalent. |
| CAP-2026-01-0003 | ACCT-0034 | 2026-01-29 | core acceptance | ready | T2 | observed | 2 | wave-ready | Core capability has a tested target-platform equivalent. |
| CAP-2026-01-0004 | ACCT-1503 | 2026-01-07 | stored profile data | in-progress | T3 | observed | 5 | parity-gap | Data copy and sync are in progress but not yet verified. |
| CAP-2026-01-0005 | ACCT-0010 | 2026-01-29 | stored profile data | in-progress | T3 | observed | 5 | parity-gap | Data copy and sync are in progress but not yet verified. |
| CAP-2026-01-0006 | ACCT-1505 | 2026-01-09 | scheduled activity | blocked | T2 | observed | 7 | parity-gap | Scheduled activity has no confirmed target-platform operating model. |
| CAP-2026-01-0007 | ACCT-0036 | 2026-01-12 | scheduled activity | blocked | T2 | observed | 7 | parity-gap | Scheduled activity has no confirmed target-platform operating model. |
| CAP-2026-01-0008 | ACCT-1507 | 2026-01-07 | self-service tool | watch | T1 | unknown | 4 | measurement-gap | Capability is enabled by default but usage tracking is absent. |
| CAP-2026-01-0009 | ACCT-0012 | 2026-01-11 | self-service tool | watch | T1 | unknown | 4 | measurement-gap | Capability is enabled by default but usage tracking is absent. |
| CAP-2026-01-0010 | ACCT-1509 | 2026-01-09 | core acceptance | ready | T2 | observed | 2 | wave-ready | Core capability has a tested target-platform equivalent. |
| CAP-2026-01-0011 | ACCT-0038 | 2026-01-06 | core acceptance | ready | T2 | observed | 2 | wave-ready | Core capability has a tested target-platform equivalent. |
| CAP-2026-01-0012 | ACCT-1511 | 2026-01-10 | core acceptance | ready | T2 | observed | 2 | wave-ready | Core capability has a tested target-platform equivalent. |
| CAP-2026-01-0013 | ACCT-0014 | 2026-01-11 | stored profile data | in-progress | T3 | observed | 5 | parity-gap | Data copy and sync are in progress but not yet verified. |
| CAP-2026-01-0014 | ACCT-1513 | 2026-01-19 | stored profile data | in-progress | T3 | observed | 5 | parity-gap | Data copy and sync are in progress but not yet verified. |
| CAP-2026-01-0015 | ACCT-0040 | 2026-01-09 | scheduled activity | blocked | T2 | observed | 7 | parity-gap | Scheduled activity has no confirmed target-platform operating model. |
| CAP-2026-01-0016 | ACCT-1515 | 2026-01-07 | scheduled activity | blocked | T2 | observed | 7 | parity-gap | Scheduled activity has no confirmed target-platform operating model. |
| CAP-2026-01-0017 | ACCT-0016 | 2026-01-15 | self-service tool | watch | T1 | unknown | 4 | measurement-gap | Capability is enabled by default but usage tracking is absent. |
| CAP-2026-01-0018 | ACCT-1517 | 2026-01-25 | self-service tool | watch | T1 | unknown | 4 | measurement-gap | Capability is enabled by default but usage tracking is absent. |
| CAP-2026-01-0019 | ACCT-0042 | 2026-01-14 | core acceptance | ready | T2 | observed | 2 | wave-ready | Core capability has a tested target-platform equivalent. |
| CAP-2026-01-0020 | ACCT-1519 | 2026-01-15 | core acceptance | ready | T2 | observed | 2 | wave-ready | Core capability has a tested target-platform equivalent. |
| CAP-2026-01-0021 | ACCT-0018 | 2026-01-08 | core acceptance | ready | T2 | observed | 2 | wave-ready | Core capability has a tested target-platform equivalent. |
| CAP-2026-01-0022 | ACCT-1521 | 2026-01-22 | stored profile data | in-progress | T3 | observed | 5 | parity-gap | Data copy and sync are in progress but not yet verified. |
| CAP-2026-01-0023 | ACCT-0044 | 2026-01-10 | stored profile data | in-progress | T3 | observed | 5 | parity-gap | Data copy and sync are in progress but not yet verified. |
| CAP-2026-01-0024 | ACCT-1523 | 2026-01-19 | scheduled activity | blocked | T2 | observed | 7 | parity-gap | Scheduled activity has no confirmed target-platform operating model. |
| CAP-2026-01-0025 | ACCT-0020 | 2026-01-15 | scheduled activity | blocked | T2 | observed | 7 | parity-gap | Scheduled activity has no confirmed target-platform operating model. |
| CAP-2026-01-0026 | ACCT-1525 | 2026-01-16 | self-service tool | watch | T1 | unknown | 4 | measurement-gap | Capability is enabled by default but usage tracking is absent. |
| CAP-2026-01-0027 | ACCT-0046 | 2026-01-23 | self-service tool | watch | T1 | unknown | 4 | measurement-gap | Capability is enabled by default but usage tracking is absent. |
| CAP-2026-01-0028 | ACCT-1527 | 2026-01-04 | core acceptance | ready | T2 | observed | 2 | wave-ready | Core capability has a tested target-platform equivalent. |
| CAP-2026-01-0029 | ACCT-0022 | 2026-01-01 | core acceptance | ready | T2 | observed | 2 | wave-ready | Core capability has a tested target-platform equivalent. |
| CAP-2026-01-0030 | ACCT-1529 | 2026-01-08 | core acceptance | ready | T2 | observed | 2 | wave-ready | Core capability has a tested target-platform equivalent. |
| CAP-2026-01-0031 | ACCT-0048 | 2026-01-22 | stored profile data | in-progress | T3 | observed | 5 | parity-gap | Data copy and sync are in progress but not yet verified. |
| CAP-2026-01-0032 | ACCT-1531 | 2026-01-09 | stored profile data | in-progress | T3 | observed | 5 | parity-gap | Data copy and sync are in progress but not yet verified. |
| CAP-2026-01-0033 | ACCT-0024 | 2026-01-10 | scheduled activity | blocked | T2 | observed | 7 | parity-gap | Scheduled activity has no confirmed target-platform operating model. |
| CAP-2026-01-0034 | ACCT-1533 | 2026-01-07 | scheduled activity | blocked | T2 | observed | 7 | parity-gap | Scheduled activity has no confirmed target-platform operating model. |
| CAP-2026-01-0035 | ACCT-0050 | 2026-01-08 | self-service tool | watch | T1 | unknown | 4 | measurement-gap | Capability is enabled by default but usage tracking is absent. |
| CAP-2026-01-0036 | ACCT-1535 | 2026-01-11 | self-service tool | watch | T1 | unknown | 4 | measurement-gap | Capability is enabled by default but usage tracking is absent. |
| CAP-2026-01-0037 | ACCT-0026 | 2026-01-08 | core acceptance | ready | T2 | observed | 2 | wave-ready | Core capability has a tested target-platform equivalent. |
| CAP-2026-01-0038 | ACCT-1537 | 2026-01-22 | core acceptance | ready | T2 | observed | 2 | wave-ready | Core capability has a tested target-platform equivalent. |
| CAP-2026-01-0039 | ACCT-0002 | 2026-01-24 | core acceptance | ready | T2 | observed | 2 | wave-ready | Core capability has a tested target-platform equivalent. |
| CAP-2026-01-0040 | ACCT-1539 | 2026-01-05 | stored profile data | in-progress | T3 | observed | 5 | parity-gap | Data copy and sync are in progress but not yet verified. |
| CAP-2026-01-0041 | ACCT-0028 | 2026-01-09 | stored profile data | in-progress | T3 | observed | 5 | parity-gap | Data copy and sync are in progress but not yet verified. |
| CAP-2026-01-0042 | ACCT-1541 | 2026-01-06 | scheduled activity | blocked | T2 | observed | 7 | parity-gap | Scheduled activity has no confirmed target-platform operating model. |
| CAP-2026-01-0043 | ACCT-0004 | 2026-01-18 | scheduled activity | blocked | T2 | observed | 7 | parity-gap | Scheduled activity has no confirmed target-platform operating model. |
| integration record id | account id | observed date | integration type | readiness status | transition state | complexity score | risk flag | summary | evidence note |
|---|---|---|---|---|---|---|---|---|---|
| INT-2026-01-0001 | ACCT-0015 | 2026-01-27 | hosted ui | ready | T4 | 3 | wave-ready | Hosted user journey has a target-platform path and validation checklist. | Account can proceed with guided verification. |
| INT-2026-01-0002 | ACCT-2001 | 2026-01-14 | hosted ui | ready | T4 | 3 | wave-ready | Hosted user journey has a target-platform path and validation checklist. | Account can proceed with guided verification. |
| INT-2026-01-0003 | ACCT-0041 | 2026-01-30 | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | Requires mapping guide, testing, and deploy coordination. |
| INT-2026-01-0004 | ACCT-2003 | 2026-01-15 | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | Requires mapping guide, testing, and deploy coordination. |
| INT-2026-01-0005 | ACCT-0017 | 2026-01-09 | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | Requires mapping guide, testing, and deploy coordination. |
| INT-2026-01-0006 | ACCT-2005 | 2026-01-29 | partner connector | watch | T4 | 6 | integration-rework | Connector ownership is known but target-platform support is pending. | Partner validation drives the migration date. |
| INT-2026-01-0007 | ACCT-0043 | 2026-01-19 | partner connector | watch | T4 | 6 | integration-rework | Connector ownership is known but target-platform support is pending. | Partner validation drives the migration date. |
| INT-2026-01-0008 | ACCT-2007 | 2026-01-01 | unknown surface | watch | T0 | 5 | measurement-gap | Traffic exists but cannot be attributed to a known integration surface. | Classify before cohort assignment. |
| INT-2026-01-0009 | ACCT-0019 | 2026-01-01 | hosted ui | ready | T4 | 3 | wave-ready | Hosted user journey has a target-platform path and validation checklist. | Account can proceed with guided verification. |
| INT-2026-01-0010 | ACCT-2009 | 2026-01-11 | hosted ui | ready | T4 | 3 | wave-ready | Hosted user journey has a target-platform path and validation checklist. | Account can proceed with guided verification. |
| INT-2026-01-0011 | ACCT-0045 | 2026-01-24 | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | Requires mapping guide, testing, and deploy coordination. |
| INT-2026-01-0012 | ACCT-2011 | 2026-01-06 | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | Requires mapping guide, testing, and deploy coordination. |
| INT-2026-01-0013 | ACCT-0021 | 2026-01-20 | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | Requires mapping guide, testing, and deploy coordination. |
| INT-2026-01-0014 | ACCT-2013 | 2026-01-23 | partner connector | watch | T4 | 6 | integration-rework | Connector ownership is known but target-platform support is pending. | Partner validation drives the migration date. |
| INT-2026-01-0015 | ACCT-0047 | 2026-01-24 | partner connector | watch | T4 | 6 | integration-rework | Connector ownership is known but target-platform support is pending. | Partner validation drives the migration date. |
| INT-2026-01-0016 | ACCT-2015 | 2026-01-21 | unknown surface | watch | T0 | 5 | measurement-gap | Traffic exists but cannot be attributed to a known integration surface. | Classify before cohort assignment. |
| INT-2026-01-0017 | ACCT-0023 | 2026-01-28 | hosted ui | ready | T4 | 3 | wave-ready | Hosted user journey has a target-platform path and validation checklist. | Account can proceed with guided verification. |
| INT-2026-01-0018 | ACCT-2017 | 2026-01-19 | hosted ui | ready | T4 | 3 | wave-ready | Hosted user journey has a target-platform path and validation checklist. | Account can proceed with guided verification. |
| INT-2026-01-0019 | ACCT-0049 | 2026-01-11 | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | Requires mapping guide, testing, and deploy coordination. |
| INT-2026-01-0020 | ACCT-2019 | 2026-01-17 | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | Requires mapping guide, testing, and deploy coordination. |
| INT-2026-01-0021 | ACCT-0025 | 2026-01-04 | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | Requires mapping guide, testing, and deploy coordination. |
| INT-2026-01-0022 | ACCT-2021 | 2026-01-05 | partner connector | watch | T4 | 6 | integration-rework | Connector ownership is known but target-platform support is pending. | Partner validation drives the migration date. |
| INT-2026-01-0023 | ACCT-0001 | 2026-01-11 | partner connector | watch | T4 | 6 | integration-rework | Connector ownership is known but target-platform support is pending. | Partner validation drives the migration date. |
| INT-2026-01-0024 | ACCT-2023 | 2026-01-10 | unknown surface | watch | T0 | 5 | measurement-gap | Traffic exists but cannot be attributed to a known integration surface. | Classify before cohort assignment. |
| INT-2026-01-0025 | ACCT-0027 | 2026-01-19 | hosted ui | ready | T4 | 3 | wave-ready | Hosted user journey has a target-platform path and validation checklist. | Account can proceed with guided verification. |
| INT-2026-01-0026 | ACCT-2025 | 2026-01-21 | hosted ui | ready | T4 | 3 | wave-ready | Hosted user journey has a target-platform path and validation checklist. | Account can proceed with guided verification. |
| INT-2026-01-0027 | ACCT-0003 | 2026-01-28 | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | Requires mapping guide, testing, and deploy coordination. |
| INT-2026-01-0028 | ACCT-2027 | 2026-01-02 | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | Requires mapping guide, testing, and deploy coordination. |
| INT-2026-01-0029 | ACCT-0029 | 2026-01-29 | custom api | blocked | T4 | 7 | integration-rework | Custom code still points to source-platform interfaces. | Requires mapping guide, testing, and deploy coordination. |
| INT-2026-01-0030 | ACCT-2029 | 2026-01-25 | partner connector | watch | T4 | 6 | integration-rework | Connector ownership is known but target-platform support is pending. | Partner validation drives the migration date. |
| INT-2026-01-0031 | ACCT-0005 | 2026-01-28 | partner connector | watch | T4 | 6 | integration-rework | Connector ownership is known but target-platform support is pending. | Partner validation drives the migration date. |
| INT-2026-01-0032 | ACCT-2031 | 2026-01-08 | unknown surface | watch | T0 | 5 | measurement-gap | Traffic exists but cannot be attributed to a known integration surface. | Classify before cohort assignment. |
| billing record id | account id | observed date | billing model | billing status | transition state | complexity score | risk flag | summary | evidence note |
|---|---|---|---|---|---|---|---|---|---|
| BILL-2026-01-0001 | ACCT-0022 | 2026-01-23 | direct account billing | ready | T5 | 2 | wave-ready | Single billing owner is defined for the read-only source state. | Billing can move with account-state approval. |
| BILL-2026-01-0002 | ACCT-2501 | 2026-01-17 | direct account billing | ready | T5 | 2 | wave-ready | Single billing owner is defined for the read-only source state. | Billing can move with account-state approval. |
| BILL-2026-01-0003 | ACCT-0048 | 2026-01-25 | sponsor-paid | watch | T4 | 5 | billing-continuity | A third party pays account fees and must be preserved through cutover. | Do not switch to direct billing silently. |
| BILL-2026-01-0004 | ACCT-2503 | 2026-01-18 | sponsor-paid | watch | T4 | 5 | billing-continuity | A third party pays account fees and must be preserved through cutover. | Do not switch to direct billing silently. |
| BILL-2026-01-0005 | ACCT-0024 | 2026-01-05 | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | State-level billing rule is required. |
| BILL-2026-01-0006 | ACCT-2505 | 2026-01-14 | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | State-level billing rule is required. |
| BILL-2026-01-0007 | ACCT-0050 | 2026-01-25 | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | State-level billing rule is required. |
| BILL-2026-01-0008 | ACCT-2507 | 2026-01-18 | no current revenue | watch | T0 | 3 | measurement-gap | No current revenue is visible, but account disposition still needs confirmation. | Dormant status alone is not a disposition. |
| BILL-2026-01-0009 | ACCT-0026 | 2026-01-16 | direct account billing | ready | T5 | 2 | wave-ready | Single billing owner is defined for the read-only source state. | Billing can move with account-state approval. |
| BILL-2026-01-0010 | ACCT-2509 | 2026-01-08 | direct account billing | ready | T5 | 2 | wave-ready | Single billing owner is defined for the read-only source state. | Billing can move with account-state approval. |
| BILL-2026-01-0011 | ACCT-0002 | 2026-01-13 | sponsor-paid | watch | T4 | 5 | billing-continuity | A third party pays account fees and must be preserved through cutover. | Do not switch to direct billing silently. |
| BILL-2026-01-0012 | ACCT-2511 | 2026-01-19 | sponsor-paid | watch | T4 | 5 | billing-continuity | A third party pays account fees and must be preserved through cutover. | Do not switch to direct billing silently. |
| BILL-2026-01-0013 | ACCT-0028 | 2026-01-17 | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | State-level billing rule is required. |
| BILL-2026-01-0014 | ACCT-2513 | 2026-01-30 | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | State-level billing rule is required. |
| BILL-2026-01-0015 | ACCT-0004 | 2026-01-23 | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | State-level billing rule is required. |
| BILL-2026-01-0016 | ACCT-2515 | 2026-01-08 | no current revenue | watch | T0 | 3 | measurement-gap | No current revenue is visible, but account disposition still needs confirmation. | Dormant status alone is not a disposition. |
| BILL-2026-01-0017 | ACCT-0030 | 2026-01-15 | direct account billing | ready | T5 | 2 | wave-ready | Single billing owner is defined for the read-only source state. | Billing can move with account-state approval. |
| BILL-2026-01-0018 | ACCT-2517 | 2026-01-05 | direct account billing | ready | T5 | 2 | wave-ready | Single billing owner is defined for the read-only source state. | Billing can move with account-state approval. |
| BILL-2026-01-0019 | ACCT-0006 | 2026-01-24 | sponsor-paid | watch | T4 | 5 | billing-continuity | A third party pays account fees and must be preserved through cutover. | Do not switch to direct billing silently. |
| BILL-2026-01-0020 | ACCT-2519 | 2026-01-18 | sponsor-paid | watch | T4 | 5 | billing-continuity | A third party pays account fees and must be preserved through cutover. | Do not switch to direct billing silently. |
| BILL-2026-01-0021 | ACCT-0032 | 2026-01-28 | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | State-level billing rule is required. |
| BILL-2026-01-0022 | ACCT-2521 | 2026-01-27 | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | State-level billing rule is required. |
| BILL-2026-01-0023 | ACCT-0008 | 2026-01-18 | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | State-level billing rule is required. |
| BILL-2026-01-0024 | ACCT-2523 | 2026-01-29 | no current revenue | watch | T0 | 3 | measurement-gap | No current revenue is visible, but account disposition still needs confirmation. | Dormant status alone is not a disposition. |
| BILL-2026-01-0025 | ACCT-0034 | 2026-01-01 | direct account billing | ready | T5 | 2 | wave-ready | Single billing owner is defined for the read-only source state. | Billing can move with account-state approval. |
| BILL-2026-01-0026 | ACCT-2525 | 2026-01-16 | direct account billing | ready | T5 | 2 | wave-ready | Single billing owner is defined for the read-only source state. | Billing can move with account-state approval. |
| BILL-2026-01-0027 | ACCT-0010 | 2026-01-06 | sponsor-paid | watch | T4 | 5 | billing-continuity | A third party pays account fees and must be preserved through cutover. | Do not switch to direct billing silently. |
| BILL-2026-01-0028 | ACCT-2527 | 2026-01-25 | sponsor-paid | watch | T4 | 5 | billing-continuity | A third party pays account fees and must be preserved through cutover. | Do not switch to direct billing silently. |
| BILL-2026-01-0029 | ACCT-0036 | 2026-01-17 | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | State-level billing rule is required. |
| BILL-2026-01-0030 | ACCT-2529 | 2026-01-18 | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | State-level billing rule is required. |
| BILL-2026-01-0031 | ACCT-0012 | 2026-01-25 | dual-active window | blocked | T4 | 6 | billing-continuity | Both platforms may be active, but one billing owner has not been assigned. | State-level billing rule is required. |
| BILL-2026-01-0032 | ACCT-2531 | 2026-01-08 | no current revenue | watch | T0 | 3 | measurement-gap | No current revenue is visible, but account disposition still needs confirmation. | Dormant status alone is not a disposition. |
| readiness record id | account id | review date | wave | readiness status | transition state | complexity score | blocker type | summary | review note |
|---|---|---|---|---|---|---|---|---|---|
| READY-2026-01-0001 | ACCT-0029 | 2026-01-19 | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. | Use as a reference cohort. |
| READY-2026-01-0002 | ACCT-3001 | 2026-01-16 | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. | Use as a reference cohort. |
| READY-2026-01-0003 | ACCT-0005 | 2026-01-22 | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. | Use as a reference cohort. |
| READY-2026-01-0004 | ACCT-3003 | 2026-01-21 | wave 3 parity dependency | blocked | T2 | 7 | parity-gap | Capability parity blocks transition progression. | Resolve target capability before account outreach. |
| READY-2026-01-0005 | ACCT-0031 | 2026-01-11 | wave 3 parity dependency | blocked | T2 | 7 | parity-gap | Capability parity blocks transition progression. | Resolve target capability before account outreach. |
| READY-2026-01-0006 | ACCT-3005 | 2026-01-14 | wave 4 integration rework | watch | T4 | 6 | integration-rework | Dual access is useful while integration rework is completed. | Keep source access until verification succeeds. |
| READY-2026-01-0007 | ACCT-0007 | 2026-01-02 | wave 4 integration rework | watch | T4 | 6 | integration-rework | Dual access is useful while integration rework is completed. | Keep source access until verification succeeds. |
| READY-2026-01-0008 | ACCT-3007 | 2026-01-18 | wave unknown | watch | T0 | 4 | measurement-gap | Readiness cannot be assigned while usage signals are missing. | Collect evidence before sequencing. |
| READY-2026-01-0009 | ACCT-0033 | 2026-01-13 | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. | Use as a reference cohort. |
| READY-2026-01-0010 | ACCT-3009 | 2026-01-27 | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. | Use as a reference cohort. |
| READY-2026-01-0011 | ACCT-0009 | 2026-01-26 | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. | Use as a reference cohort. |
| READY-2026-01-0012 | ACCT-3011 | 2026-01-22 | wave 3 parity dependency | blocked | T2 | 7 | parity-gap | Capability parity blocks transition progression. | Resolve target capability before account outreach. |
| READY-2026-01-0013 | ACCT-0035 | 2026-01-03 | wave 3 parity dependency | blocked | T2 | 7 | parity-gap | Capability parity blocks transition progression. | Resolve target capability before account outreach. |
| READY-2026-01-0014 | ACCT-3013 | 2026-01-17 | wave 4 integration rework | watch | T4 | 6 | integration-rework | Dual access is useful while integration rework is completed. | Keep source access until verification succeeds. |
| READY-2026-01-0015 | ACCT-0011 | 2026-01-06 | wave 4 integration rework | watch | T4 | 6 | integration-rework | Dual access is useful while integration rework is completed. | Keep source access until verification succeeds. |
| READY-2026-01-0016 | ACCT-3015 | 2026-01-25 | wave unknown | watch | T0 | 4 | measurement-gap | Readiness cannot be assigned while usage signals are missing. | Collect evidence before sequencing. |
| READY-2026-01-0017 | ACCT-0037 | 2026-01-01 | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. | Use as a reference cohort. |
| READY-2026-01-0018 | ACCT-3017 | 2026-01-12 | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. | Use as a reference cohort. |
| READY-2026-01-0019 | ACCT-0013 | 2026-01-31 | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. | Use as a reference cohort. |
| READY-2026-01-0020 | ACCT-3019 | 2026-01-04 | wave 3 parity dependency | blocked | T2 | 7 | parity-gap | Capability parity blocks transition progression. | Resolve target capability before account outreach. |
| READY-2026-01-0021 | ACCT-0039 | 2026-01-02 | wave 3 parity dependency | blocked | T2 | 7 | parity-gap | Capability parity blocks transition progression. | Resolve target capability before account outreach. |
| READY-2026-01-0022 | ACCT-3021 | 2026-01-13 | wave 4 integration rework | watch | T4 | 6 | integration-rework | Dual access is useful while integration rework is completed. | Keep source access until verification succeeds. |
| READY-2026-01-0023 | ACCT-0015 | 2026-01-01 | wave 4 integration rework | watch | T4 | 6 | integration-rework | Dual access is useful while integration rework is completed. | Keep source access until verification succeeds. |
| READY-2026-01-0024 | ACCT-3023 | 2026-01-03 | wave unknown | watch | T0 | 4 | measurement-gap | Readiness cannot be assigned while usage signals are missing. | Collect evidence before sequencing. |
| READY-2026-01-0025 | ACCT-0041 | 2026-01-08 | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. | Use as a reference cohort. |
| READY-2026-01-0026 | ACCT-3025 | 2026-01-12 | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. | Use as a reference cohort. |
| READY-2026-01-0027 | ACCT-0017 | 2026-01-17 | wave 1 simple path | ready | T5 | 2 | wave-ready | Account has a simple operating path and can enter source read-only after notice. | Use as a reference cohort. |
| READY-2026-01-0028 | ACCT-3027 | 2026-01-18 | wave 3 parity dependency | blocked | T2 | 7 | parity-gap | Capability parity blocks transition progression. | Resolve target capability before account outreach. |
| READY-2026-01-0029 | ACCT-0043 | 2026-01-27 | wave 3 parity dependency | blocked | T2 | 7 | parity-gap | Capability parity blocks transition progression. | Resolve target capability before account outreach. |
| READY-2026-01-0030 | ACCT-3029 | 2026-01-25 | wave 4 integration rework | watch | T4 | 6 | integration-rework | Dual access is useful while integration rework is completed. | Keep source access until verification succeeds. |
| READY-2026-01-0031 | ACCT-0019 | 2026-01-23 | wave 4 integration rework | watch | T4 | 6 | integration-rework | Dual access is useful while integration rework is completed. | Keep source access until verification succeeds. |
| READY-2026-01-0032 | ACCT-3031 | 2026-01-29 | wave unknown | watch | T0 | 4 | measurement-gap | Readiness cannot be assigned while usage signals are missing. | Collect evidence before sequencing. |