> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nectarclimate.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrate from IBM Envizi

> Map utility bill analytics datasets from IBM Envizi into Nectar for operational data quality and delivery.

If you use IBM Envizi for utility bill analytics and sustainability reporting, Nectar can complement and simplify your day-to-day utility data operations.

## 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

Teams often want a faster operational layer for intake, issue resolution, and recurring exports.

## How your Envizi data maps to Nectar

| Envizi-style source concept        | Nectar destination                                                            | Migration notes                                         |
| ---------------------------------- | ----------------------------------------------------------------------------- | ------------------------------------------------------- |
| Group or business hierarchy        | [Company](/platform/glossary#company)                                         | Mirror major reporting segments as companies.           |
| Location entities                  | [Site](/platform/glossary#site)                                               | Preserve location IDs for cross-system traceability.    |
| Utility accounts                   | [Account](/platform/glossary#account)                                         | Maintain account identifiers as source references.      |
| Physical and virtual meter records | [Meter](/platform/glossary#meter)                                             | Keep meter lineage metadata for aggregated meters.      |
| Utility bill analytics records     | [Bill](/platform/glossary#bill) + [usage data](/platform/glossary#usage-data) | Separate bill totals from usage metrics for cleaner QA. |
| Variance flags and exceptions      | **Data Quality** workflows                                                    | Move from report-only exceptions to actionable queues.  |

## Recommended onboarding plan

<Steps>
  <Step title="Select initial migration scope">
    Prioritize utility types and sites with the highest reporting impact and cleanest historical datasets.
  </Step>

  <Step title="Export hierarchy and utility datasets">
    Export groups, locations, accounts, meter metadata, and historical utility bill records for mapping.
  </Step>

  <Step title="Map hierarchy to Nectar structure">
    Align groups to companies and locations to sites, then connect accounts and meters.
  </Step>

  <Step title="Pilot and reconcile">
    Validate monthly totals and usage trends between Envizi exports and Nectar for a representative sample.
  </Step>

  <Step title="Operational cutover">
    Use Nectar for intake, QA, and export workflows while preserving your reporting continuity.
  </Step>
</Steps>

## 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](/platform/data-input/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

## Ready to migrate from Envizi?

* [Visit the Nectar homepage](https://nectarclimate.com)