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

> Move utility expense and sustainability data from ENGIE workflows into Nectar with a structured onboarding plan.

If you currently run utility data operations through ENGIE Impact, you can migrate to Nectar in a controlled, low-risk sequence.
This guide helps you map your current structure, validate data quickly, and cut over with confidence.

## How ENGIE workflows are usually organized

Based on public ENGIE materials, most ENGIE programs combine:

* Utility expense and invoice datasets across electricity, gas, water, and waste
* Account and meter-level records tied to large site portfolios
* Sustainability and performance analytics layers for finance and ESG teams

In practice, you often have multiple exports and report layers, not one operational workspace for day-to-day data QA.

## How your ENGIE data maps to Nectar

| ENGIE-style source concept                | Nectar destination                                                            | Migration notes                                               |
| ----------------------------------------- | ----------------------------------------------------------------------------- | ------------------------------------------------------------- |
| Client / portfolio hierarchy              | [Company](/platform/glossary#company) + [site](/platform/glossary#site)       | Keep existing portfolio segmentation.                         |
| Utility account identifiers               | [Account](/platform/glossary#account)                                         | Preserve account numbers as source-of-truth IDs.              |
| Meter-level records                       | [Meter](/platform/glossary#meter)                                             | Map one meter per commodity where possible.                   |
| Invoice / bill line items                 | [Bill](/platform/glossary#bill) + [usage data](/platform/glossary#usage-data) | Split financial and usage fields for better QA and exports.   |
| Monthly or interval consumption metrics   | Usage data records                                                            | Normalize units before bulk import.                           |
| Exception and variance reporting extracts | **Data Quality** issue workflows                                              | Use Nectar issue queues to replace manual exception tracking. |

## Recommended onboarding plan

<Steps>
  <Step title="Export and profile your ENGIE datasets">
    Export representative account, meter, and billing history for 6 to 24 months. Nectar helps you profile null rates, duplicate IDs, and unit mismatches before import.
  </Step>

  <Step title="Set up your base structure in Nectar">
    Create companies and sites first, then attach accounts and meters. This preserves reporting continuity after cutover.
  </Step>

  <Step title="Run a pilot import">
    Migrate a subset of sites and reconcile totals by month, account, and utility type. Resolve mapping gaps early.
  </Step>

  <Step title="Enable ongoing collection flows">
    Add automated [connections](/platform/data-input/connections), [uploads](/platform/data-input/uploads), or [invitations](/platform/data-input/invitations) for future data flow.
  </Step>

  <Step title="Parallel validate and cut over">
    Compare one to two billing cycles between systems, sign off on parity, then move reporting workflows to Nectar.
  </Step>
</Steps>

## What you gain in Nectar

* **Data Input:** Faster onboarding for new utilities through connection, upload, and invitation pathways.
* **Data Inventory:** One place to review bills, accounts, meters, and usage records with editable context.
* **Data Quality:** Native issue tracking for anomalies, missing months, and completeness.
* **Data Export:** Repeatable exports and partner integrations without rebuilding monthly reports.
* **Analytics:** Portfolio trends by commodity, site, and time without spreadsheet rollups.

## Features you may not have today

Depending on your ENGIE engagement model, Nectar may add capabilities you do not currently use, including:

* Self-serve utility connection onboarding for ops teams
* Built-in client-facing invitations for credential collection
* Unified operational QA flows across ingestion, validation, and export

## Nectar support during migration

Nectar supports you through a full onboarding motion:

* Data model workshop and mapping sign-off
* Pilot validation and reconciliation reporting
* Weekly implementation checkpoints until cutover
* Post-launch support to tune quality and exports

## Ready to migrate from ENGIE?

Learn more about Nectar and book your migration conversation:

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