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

# How to migrate from another provider

> Move from your current utility data workflow to Nectar with guided onboarding, site and connection import, and bill collection.

<Note>
  Product packaging can vary by contract. Nectar validates your exact data model with you during onboarding.
</Note>

If you are moving from another energy or utility data workflow, you do not need to rebuild your process from scratch. Self-serve import covers **sites**, **connections**, and optional **custom variable values**. Accounts, meters, and bills are created when you collect or upload data. Nectar’s onboarding team can map historical extracts when that is in your contract.

## Choose your current service

Use these guides when you talk with Nectar about your source system. They are not in-app importers for accounts, meters, or bills.

<CardGroup cols={2}>
  <Card title="From ENGIE Impact" icon="arrow-right-left" href="/docs/platform/onboarding/engie">
    Map utility expense and sustainability datasets from ENGIE workflows into Nectar.
  </Card>

  <Card title="From Schneider Electric" icon="arrow-right-left" href="/docs/platform/onboarding/schneider-electric">
    Move Resource Advisor-style utility billing and meter data into Nectar.
  </Card>

  <Card title="From energy services companies" icon="arrow-right-left" href="/docs/platform/onboarding/energy-services-companies">
    Standardize fragmented ESCO workflows and client data into one Nectar operating model.
  </Card>

  <Card title="From Arcadia / Urjanet" icon="arrow-right-left" href="/docs/platform/onboarding/arcadia-urjanet">
    Translate normalized account and bill datasets from Arcadia/Urjanet into Nectar.
  </Card>

  <Card title="From spreadsheets" icon="arrow-right-left" href="/docs/platform/onboarding/spreadsheets">
    Import sites and connections from spreadsheets, then collect bills in Nectar.
  </Card>

  <Card title="From IBM Envizi" icon="arrow-right-left" href="/docs/platform/onboarding/envizi">
    Port utility bill analytics datasets and hierarchy-aligned records into Nectar.
  </Card>

  <Card title="From EnergyCAP" icon="arrow-right-left" href="/docs/platform/onboarding/energycap">
    Move account, meter, and utility accounting workflows from EnergyCAP to Nectar.
  </Card>

  <Card title="From Constellation" icon="arrow-right-left" href="/docs/platform/onboarding/constellation">
    Migrate utility bill management and reporting workflows from Constellation Navigator.
  </Card>

  <Card title="From Conservice" icon="arrow-right-left" href="/docs/platform/onboarding/conservice">
    Map property utility expense and resident-billing-adjacent data into Nectar.
  </Card>

  <Card title="From Cass" icon="arrow-right-left" href="/docs/platform/onboarding/cass">
    Bring utility invoice and cost-allocation records from Cass into Nectar.
  </Card>
</CardGroup>

## Your migration path in Nectar

<Steps>
  <Step title="Discovery with Nectar onboarding">
    Nectar’s onboarding team reviews your source exports, portals, and reporting outputs and maps them to companies, sites, accounts, meters, and usage. In product, you create the company, [bulk-import sites](/docs/platform/onboarding/spreadsheets), and add [connections](/docs/platform/data-input/connections).
  </Step>

  <Step title="Start with a few sites">
    Import a small set of sites, connect or upload bills, then check [Completeness](/docs/platform/data-quality/overview) and [Issues](/docs/platform/data-quality/issues) before expanding.
  </Step>

  <Step title="Parallel run and reconciliation">
    Compare Nectar against your current process for one to two billing cycles using Completeness, Issues, and [exports](/docs/platform/data-export/overview). Close gaps with your onboarding contact.
  </Step>

  <Step title="Scale across the portfolio">
    Repeat site import and connections across the rest of your portfolio. Nectar can help migrate history when that is part of your engagement.
  </Step>
</Steps>

## What typically improves after migration

| Area           | Typical pre-migration pain                            | Nectar outcome                                                                                                                                |
| -------------- | ----------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| Data Input     | Manual bill retrieval, mixed sources, delayed updates | Automated [connections](/docs/platform/glossary#connection), uploads, email, and [invitations](/docs/platform/glossary#invitation)                      |
| Data Inventory | Fragmented account and meter records                  | Unified [bills](/docs/platform/data-inventory/bills), [accounts](/docs/platform/data-inventory/accounts), and [meters](/docs/platform/data-inventory/meters) |
| Data Quality   | Hidden anomalies and missing months                   | Built-in issue and completeness workflows in **Data Quality**                                                                                 |
| Data Export    | Custom ad hoc reports each month                      | Repeatable exports and downstream integrations in **Data Export**                                                                             |
| Analytics      | Spreadsheet-heavy trend analysis                      | Portfolio consumption analytics by site, utility type, and time period                                                                        |

## Nectar support during onboarding

Nectar’s onboarding team supports technical mapping, QA, and rollout as a **services process** (not in-app tools):

* Discovery workshops and data dictionary alignment with your team
* Help validating site and connection import files; historical bill files go through [uploads](/docs/platform/data-input/uploads) or Nectar-assisted migration
* Regular implementation checkpoints and issue resolution
* Go-live checklist and post-cutover support

Site and connection CSV validation happens in the browser during [bulk import](/docs/platform/glossary#bulk-import). API onboarding for developers is a separate services conversation — see [For developers](/docs/platform/for-developers).

You keep control of timing and priorities, and we help you reduce risk at each phase.

## Related pages

* [Migrate from spreadsheets](/docs/platform/onboarding/spreadsheets) — self-serve site and connection import
* [Getting started](/docs/platform/getting-started) — platform overview and first-time onboarding steps
* [Data Input](/docs/platform/data-input/overview) — connections, uploads, invitations, and manual entry
* [Data Quality](/docs/platform/data-quality/overview) — Completeness and Issues
* [Data Inventory](/docs/platform/data-inventory/overview) — bills, accounts, and meters
* [Glossary](/docs/platform/glossary) — definitions for terms used in migration guides

## Start your migration plan

Read the guide that matches your current system, then contact Nectar to scope your rollout:

* [Visit the Nectar homepage](https://nectarclimate.com)
* [Contact support@nectarclimate.com](mailto:support@nectarclimate.com)