> ## 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 Arcadia / Urjanet

> Migrate normalized utility account and bill datasets from Arcadia/Urjanet into Nectar.

If you currently use Arcadia or Urjanet-based utility data feeds, Nectar can map your normalized records into an operations-first workspace for ongoing intake, QA, and export.

## How Arcadia / Urjanet workflows are usually organized

Public Arcadia and Urjanet materials describe a model centered on:

* Utility account enrollment with credentialed data access
* Normalized utility bill and account records across many providers
* API-driven delivery for downstream reporting and analytics

This model is strong for data acquisition. Teams often add additional operational layers elsewhere for exception handling and day-to-day QA.

## How your Arcadia / Urjanet data maps to Nectar

| Arcadia / Urjanet-style concept               | Nectar destination                                                              | Migration notes                                               |
| --------------------------------------------- | ------------------------------------------------------------------------------- | ------------------------------------------------------------- |
| Provider account ID and account metadata      | [Account](/platform/glossary#account)                                           | Keep source identifiers for traceability.                     |
| Service address and utility provider metadata | [Site](/platform/glossary#site) + account attributes                            | Preserve address normalization and provider names.            |
| Meter-level usage payloads                    | [Meter](/platform/glossary#meter) + [usage data](/platform/glossary#usage-data) | Map interval and billing-period values by commodity.          |
| Bill headers and bill charges                 | [Bill](/platform/glossary#bill)                                                 | Import service period start/end, totals, and charges.         |
| Enrollment or account statuses                | Connection and QA workflows                                                     | Use status-driven dashboards for onboarding and issue triage. |

## Recommended onboarding plan

<Steps>
  <Step title="Export account and bill history">
    Pull representative account metadata, bill records, and usage payloads. Include status fields used for operational tracking.
  </Step>

  <Step title="Map IDs and hierarchy">
    Map provider account IDs to Nectar accounts, then align addresses to sites and company ownership.
  </Step>

  <Step title="Load a pilot portfolio">
    Import a subset of accounts and reconcile bill totals and usage for two to three billing periods.
  </Step>

  <Step title="Set up ongoing intake">
    Choose your production intake path: direct [connections](/platform/data-input/connections), scheduled uploads, or hybrid workflow.
  </Step>

  <Step title="Operationalize in Nectar">
    Move issue management into **Data Quality** and downstream delivery into **Data Export**.
  </Step>
</Steps>

## What improves in Nectar

* More complete operations loop from ingestion to QA to export in one place
* Easier collaboration between implementation, operations, and reporting teams
* Better handling of portfolio-level exception workflows

## Features to evaluate in Nectar

Depending on your current Arcadia/Urjanet stack, Nectar may add:

* Built-in UI workflows for data operations teams, not only API delivery
* Invitation-based onboarding for faster credential and source collection
* Unified record editing and quality triage across bills, accounts, and meters

## Nectar support during migration

Nectar provides:

* Source-to-target mapping workshops
* Pilot import QA and reconciliation support
* Cutover planning with post-launch monitoring

## Ready to migrate from Arcadia / Urjanet?

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