Capability parity and target-platform readiness backlog.
List every unknown usage surface and start logging or manual confirmation before wave planning.
Traffic exists but cannot be attributed to a known integration surface.
Low recent activity cannot be interpreted because usage tracking is missing.
Capability is enabled by default but usage tracking is absent.
Resolve target-platform capability gaps before accounts are invited into dual access.
Capability parity blocks transition progression.
Capability parity blocks transition progression.
Target processing path exists but required capability parity is incomplete.
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.
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.
Give integrators a separate wave with test credentials, mapping guides, and verification gates.
Custom code still points to source-platform interfaces.
Account can use both platforms, but embedded integration work remains.
Account can use both platforms, but embedded integration work remains.
Target-platform parity gaps appear before accounts can advance to later transition states.
Capability parity blocks transition progression.
Capability parity blocks transition progression.
Target processing path exists but required capability parity is incomplete.