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

> Move from spreadsheet-based utility tracking to a scalable, auditable Nectar workflow.

If your team runs utility operations in spreadsheets, you are not alone.
Many teams start there and eventually hit limits on quality control, collaboration, and scale.

## How spreadsheet workflows are usually organized

Common spreadsheet setups include columns for:

* Utility provider and account number
* Site address or building name
* Billing period start/end
* Usage values (for example kWh, therms, gallons)
* Charges, due dates, and payment status
* Notes for exceptions and follow-up

These files are flexible, but they become hard to govern when multiple people edit them across monthly cycles.

## How your spreadsheet data maps to Nectar

| Spreadsheet column group          | Nectar destination                          | Migration notes                                       |
| --------------------------------- | ------------------------------------------- | ----------------------------------------------------- |
| Client or business-unit column    | [Company](/platform/glossary#company)       | Use a stable company ID during import.                |
| Building or address columns       | [Site](/platform/glossary#site)             | Standardize address formatting before load.           |
| Utility account number            | [Account](/platform/glossary#account)       | Keep original account numbers for reconciliation.     |
| Meter ID or service point columns | [Meter](/platform/glossary#meter)           | Add commodity and units if missing.                   |
| Billing period + charge columns   | [Bill](/platform/glossary#bill)             | Validate date boundaries and currency conventions.    |
| Usage and demand columns          | [Usage data](/platform/glossary#usage-data) | Normalize units before trend analysis.                |
| Exception notes                   | **Data Quality** issues                     | Convert free-text notes into structured QA workflows. |

## Recommended onboarding plan

<Steps>
  <Step title="Audit your source spreadsheets">
    Identify canonical files, remove duplicates, and define the authoritative columns for each utility type.
  </Step>

  <Step title="Standardize format">
    Normalize headers, dates, units, and account IDs. Nectar provides templates to accelerate this step.
  </Step>

  <Step title="Load structure first">
    Import companies, sites, accounts, and meters before loading bills and usage records.
  </Step>

  <Step title="Run historical backfill">
    Import historical billing periods and usage data, then reconcile totals by month and site.
  </Step>

  <Step title="Replace manual collection">
    Shift future intake to [connections](/platform/data-input/connections), [uploads](/platform/data-input/uploads), or [invitations](/platform/data-input/invitations).
  </Step>
</Steps>

## What improves in Nectar

* No more version-control issues across spreadsheet files
* Faster month-end close with structured QA and completeness checks
* Better accountability through role-based workflows and audit trails
* Easier downstream reporting with repeatable exports

## Features to evaluate in Nectar

Compared with spreadsheet operations, Nectar adds:

* Automated utility collection workflows
* Built-in anomaly and missing-data detection
* Unified analytics and export tooling from the same dataset

## Nectar support during migration

Nectar helps you move quickly without losing confidence:

* Spreadsheet-to-platform mapping support
* Pilot validation with side-by-side reconciliation
* Enablement for analysts and reporting teams

## Ready to leave spreadsheets behind?

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