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

> Move utility bill management datasets from Constellation workflows into Nectar.

If you currently use Constellation utility bill management workflows, Nectar can preserve your reporting continuity while improving day-to-day data operations.

## How Constellation workflows are usually organized

Public Constellation Navigator utility bill management materials typically describe:

* Consolidation of utility bills across multiple locations and providers
* Reporting by line item, meter, and location
* Bill audit and payment-adjacent workflows

Teams often want a more integrated operating layer for ongoing data intake, issue triage, and downstream integrations.

## How your Constellation data maps to Nectar

| Constellation-style source concept | Nectar destination                                                      | Migration notes                                               |
| ---------------------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------- |
| Portfolio and location groups      | [Company](/platform/glossary#company) + [site](/platform/glossary#site) | Preserve your regional or business-unit structure.            |
| Utility account records            | [Account](/platform/glossary#account)                                   | Keep account IDs for reconciliation and audit.                |
| Meter-level reporting entities     | [Meter](/platform/glossary#meter)                                       | Map utility types and measurement units directly.             |
| Utility bill records               | [Bill](/platform/glossary#bill)                                         | Import period boundaries, totals, and key charge fields.      |
| Consumption metrics                | [Usage data](/platform/glossary#usage-data)                             | Normalize unit conventions before migration.                  |
| Audit exception logs               | **Data Quality** issue queues                                           | Move exception handling into structured, trackable workflows. |

## Recommended onboarding plan

<Steps>
  <Step title="Prioritize the first migration wave">
    Choose high-impact sites and utility types for the pilot. Keep scope tight to accelerate validation.
  </Step>

  <Step title="Extract account, meter, and bill history">
    Export representative historical records and define source-of-truth fields used in monthly reporting.
  </Step>

  <Step title="Map and validate in Nectar">
    Build field mappings, import pilot data, and reconcile by billing period and site totals.
  </Step>

  <Step title="Enable future-state intake">
    Configure automated [connections](/platform/data-input/connections) and fallback upload flows to reduce manual handling.
  </Step>

  <Step title="Cut over QA and exports">
    Move daily review to **Data Inventory** and **Data Quality**, then move recurring outputs to **Data Export**.
  </Step>
</Steps>

## What improves in Nectar

* Faster onboarding and scaling for new utility sources
* Better cross-team collaboration for issue management
* Cleaner end-to-end path from intake to analytics and export

## Features to evaluate in Nectar

Depending on your current package and process, Nectar may add:

* Client-facing [invitations](/platform/data-input/invitations) for streamlined source collection
* Unified record-level edits across bills, accounts, meters, and usage
* Purpose-built data quality and completeness workflows

## Nectar support during migration

Nectar provides:

* Mapping workshops and migration checklists
* Pilot reconciliation and acceptance sign-off
* Structured go-live and post-cutover support

## Ready to migrate from Constellation?

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