How Envizi workflows are usually organized
Public Envizi documentation highlights:- Hierarchy-based data navigation across groups, locations, and accounts
- Utility bill analytics for cost and consumption
- Meter and virtual-meter concepts for utility data tracking
How your Envizi data maps to Nectar
Recommended onboarding plan
1
Select initial migration scope
Prioritize utility types and sites with the highest reporting impact and cleanest historical datasets.
2
Export hierarchy and utility datasets
Export groups, locations, accounts, meter metadata, and historical utility bill records for mapping.
3
Map hierarchy to Nectar structure
Align groups to companies and locations to sites, then connect accounts and meters.
4
Pilot and reconcile
Validate monthly totals and usage trends between Envizi exports and Nectar for a representative sample.
5
Operational cutover
Use Nectar for intake, QA, and export workflows while preserving your reporting continuity.
What improves in Nectar
- More operational control for utility data intake and correction
- Faster issue triage through dedicated quality workflows
- Smoother handoff between operations teams and downstream reporting users
Features to evaluate in Nectar
Depending on your Envizi implementation, Nectar may add:- Utility connection onboarding and credential collection workflows
- Built-in invitations for client or field-team data collection
- Unified operational workflows across Data Input, Data Inventory, Data Quality, and Data Export
Nectar support during migration
Nectar provides:- Hierarchy and field mapping workshops
- Pilot-side reconciliation with acceptance criteria
- Cutover support and post-go-live tuning