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

> Migrate utility invoice and cost-allocation datasets from Cass workflows into Nectar.

If you rely on Cass for utility invoice processing and payment-adjacent services, Nectar can become your operational system for utility data quality, structure, and downstream analytics.

## How Cass workflows are usually organized

Public Cass materials commonly emphasize:

* High-volume invoice intake and processing
* Payment and disbursement management
* Cost allocation and ERP-ready reporting outputs

This setup is effective for payable operations. Teams often need an additional layer for utility data normalization, meter-level context, and sustainability analytics.

## How your Cass data maps to Nectar

| Cass-style source concept              | Nectar destination                                                      | Migration notes                                                 |
| -------------------------------------- | ----------------------------------------------------------------------- | --------------------------------------------------------------- |
| Business unit or cost-center hierarchy | [Company](/platform/glossary#company) + [site](/platform/glossary#site) | Keep allocation hierarchy and reporting tags.                   |
| Vendor and utility account references  | [Account](/platform/glossary#account)                                   | Preserve account IDs and utility metadata.                      |
| Facility-level utility service points  | [Meter](/platform/glossary#meter)                                       | Add commodity and units for analytics consistency.              |
| Invoice headers and line-item charges  | [Bill](/platform/glossary#bill)                                         | Retain invoice numbers, service periods, and charge categories. |
| Consumption and demand details         | [Usage data](/platform/glossary#usage-data)                             | Normalize units and fill missing metadata before cutover.       |
| Cost allocation outputs                | Data Export views                                                       | Rebuild allocation-ready exports for finance consumers.         |

## Recommended onboarding plan

<Steps>
  <Step title="Capture current reporting requirements">
    Document allocation dimensions, required fields, and month-end reconciliation expectations.
  </Step>

  <Step title="Extract historical invoice and usage data">
    Pull account, invoice, and consumption datasets for a representative historical window.
  </Step>

  <Step title="Map to Nectar operational model">
    Align costs and usage to companies, sites, accounts, and meters, then validate source IDs.
  </Step>

  <Step title="Pilot and reconcile outputs">
    Validate pilot results against existing Cass outputs for totals, periods, and allocation tags.
  </Step>

  <Step title="Scale and cut over">
    Expand to full portfolio, then transition recurring reporting and QA into Nectar.
  </Step>
</Steps>

## What improves in Nectar

* More utility-context detail for each invoice and usage record
* Better issue detection and correction before downstream reporting
* Stronger bridge between payable data and sustainability analytics

## Features to evaluate in Nectar

Depending on your current Cass operating model, Nectar may add:

* Utility-specific onboarding workflows for ongoing source collection
* Built-in [Data Quality](/platform/data-quality/overview) monitoring for anomalies and missing periods
* Richer analytics across commodity, site, and historical trends

## Nectar support during migration

Nectar provides:

* Mapping design sessions with finance and operations stakeholders
* Pilot-side reconciliation and sign-off checkpoints
* Cutover support and post-launch optimization

## Ready to migrate from Cass?

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