Skip to main content
Product packaging can vary by contract. Nectar validates your exact data model with you during onboarding.
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.

From ENGIE Impact

Map utility expense and sustainability datasets from ENGIE workflows into Nectar.

From Schneider Electric

Move Resource Advisor-style utility billing and meter data into Nectar.

From energy services companies

Standardize fragmented ESCO workflows and client data into one Nectar operating model.

From Arcadia / Urjanet

Translate normalized account and bill datasets from Arcadia/Urjanet into Nectar.

From spreadsheets

Import sites and connections from spreadsheets, then collect bills in Nectar.

From IBM Envizi

Port utility bill analytics datasets and hierarchy-aligned records into Nectar.

From EnergyCAP

Move account, meter, and utility accounting workflows from EnergyCAP to Nectar.

From Constellation

Migrate utility bill management and reporting workflows from Constellation Navigator.

From Conservice

Map property utility expense and resident-billing-adjacent data into Nectar.

From Cass

Bring utility invoice and cost-allocation records from Cass into Nectar.

​
Your migration path in Nectar

1

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, and add connections.
2

Start with a few sites

Import a small set of sites, connect or upload bills, then check Completeness and Issues before expanding.
3

Parallel run and reconciliation

Compare Nectar against your current process for one to two billing cycles using Completeness, Issues, and exports. Close gaps with your onboarding contact.
4

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.

​
What typically improves after migration

​
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 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. API onboarding for developers is a separate services conversation — see For developers. You keep control of timing and priorities, and we help you reduce risk at each phase.

​
Start your migration plan

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