Upgrade considerations
Upgrade planning needs to account for licensing, alerting setup, site naming, dashboards, and LiveAssist. The following items highlight the main operational impacts to review before or during rollout.
- Customers using traditional offline licenses must plan for license replacement as part of, or immediately after, the upgrade.
- Cloud license migrations may require re-entering license credentials in some environments.
- Teams adopting NRM Alerting should plan an initial setup phase for rules and notification policies.
- Organizations using site renaming should communicate that historical reporting may retain the old site name.
- Teams adopting Dynamic Dashboards may benefit from basic governance around dashboard ownership, naming, and JSON portability.
- LiveAssist users may need onboarding to understand Projects and message-level search behavior.
Current limitations
Some features currently have limits that affect deployment planning and operational readiness. Review the following constraints before enabling the related capability in production.
- Licensing: Traditional license files are unsupported, so upgrade planning is mandatory for legacy offline license users.
- NRM Alerts: Email is the only supported notification channel currently, so teams relying on other delivery methods need interim workarounds.
- NRM additional tabs: Visibility depends on supported devices and successful polling, so not all devices expose all new tabs or values.
- Site Suggestions: Suggestions are recommendation-only and cannot create new sites, so admins still validate and apply assignments manually.
- Dynamic Dashboard: JSON is the only export format, and some widget areas are still maturing, so this is better suited to a guided rollout than unrestricted broad use on day one.
- Site Renaming: Historical ClickHouse flow data keeps the old site name, so cross-period reporting may show mixed naming.