Capability parity and target-platform readiness backlog.
List every unknown usage surface and start logging or manual confirmation before wave planning.
No current revenue is visible, but account disposition still needs confirmation.
Capability is enabled by default but usage tracking is absent.
Capability is enabled by default but usage tracking is absent.
Resolve target-platform capability gaps before accounts are invited into dual access.
Target processing path exists but required capability parity is incomplete.
Target processing path exists but required capability parity is incomplete.
Data copy and sync are in progress but not yet verified.
Use one billing owner per account state so dual-active periods do not create double billing or missed billing.
A third party pays account fees and must be preserved through cutover.
Both platforms may be active, but one billing owner has not been assigned.
Both platforms may be active, but one billing owner has not been assigned.
Give integrators a separate wave with test credentials, mapping guides, and verification gates.
Connector ownership is known but target-platform support is pending.
Account can use both platforms, but embedded integration work remains.
Custom code still points to source-platform interfaces.
Target-platform parity gaps appear before accounts can advance to later transition states.
Target processing path exists but required capability parity is incomplete.
Target processing path exists but required capability parity is incomplete.
Data copy and sync are in progress but not yet verified.